H12
Astro 3.0 dropped a few days ago and there seems to be a decent amount of hype in the broader webdev community around many of its new features.
This video provides a pretty extensive breakdown (and a lot of said hype).
Looking through the release, there seems to be some genuinely awesome stuff – support for the new View Transitions API and their story for Image Optimization via easy CDN integration seem particularly compelling.
As someone who loves Elixir/LiveView, but hasn’t had the chance to work extensively with either in a professional environment (yet), I’m curious to hear some thoughts from the more experienced members of the community…
How does LiveView today compare with Astro 3.0 (and perhaps the server-side JS world more broadly) in your eyes? Are there any features Astro now offers that you wish could be added to LiveView, or even features compelling enough to get you to switch? Is there any reason LiveView couldn’t (or shouldn’t) do everything Astro now does?
Personally, I’d almost certainly choose LiveView when I have complex needs on the back-end and want tight integration with the BEAM, but then (reluctantly) reach for something like Astro when I have a simpler back-end and care more about building a flashy front-end for my content.
Curious how y’all feel!
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Chat & Discussions>Discussions
Latest on Elixir Forum
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex











First 10 of 21 Posts
scoop
I’m using Astro to generate the company and marketing website for a LiveView app
Terrific experience and the combo for the different purposes fits great so for.
kwando
Biggest drawback is that I would have to use JS/TS and all the other “fun” stuff that comes with that

H12
Nice! It’s cool to hear that both tools can be used side-by-side successfully.
So is Astro simple enough to use that context switching between it & LiveView isn’t much of a problem? Or do you have separate teams working on each?
H12
Oh I completely agree – tho I have to admit… Some of the transitions on their demo app just might be slick enough for me to take on a little bit of JS/TS pain
scoop
Well, the company and marketing site is so basic and simple, that thus far we’re talking about a mobile menu show/hide and a contact form validation.
Not having to do the whole React thing was so nice. The Astro components can be kept so simple. It’s more than enough for such a project. Getting started was easy peasy
Coming from that angle, I myself wouldn’t have considered Astro over LiveView for anything else than a very simple use case. Others I guess would be more happy to do something more ambitious.
scoop
View transitions
cschmatzler
Astro is explicitly not targeting the same group of projects as LiveView:
kwando
Would it be feasible to use view transitions with live view? (I know next to nothing about how it works).
LostKobrakai
In theory nothing would prevent that. But afaik chris stance is that he won’t use features in LV, which are not available cross browser or are otherwise in draft status. But LV could provide callbacks to allow for manually adding view transitions.
sodapopcan