The Quiet Revival of Alternatives to React and Next.js
Phoenix LiveView 1.2 dropped and the thread was unusually enthusiastic, with multiple comments explicitly framing it as a relief from what one person called 'vibe coded NextJS rats nests that need specialized hosting, are dog slow and require a ton of proprietary paid services.' That is a pointed description of the Vercel dependency chain, and it landed without much pushback.
LiveView 1.2 adds CSS integration and collocated JS, which prompted some concern about it becoming messy, but the overall sentiment was that Elixir's server-side model with WebSocket-driven updates is genuinely competitive for most web apps. The comparison to ASP.Net Blazor came up, suggesting people are actively shopping for the exit from the React ecosystem.
The pattern here is not new but it is getting louder: developers who have shipped real products in Next.js are frustrated with the complexity and hosting lock-in, and alternatives that trade some flexibility for simplicity are finding an audience. This is a founder-relevant signal because it affects hiring, tooling choices, and infrastructure costs.
So what?
If you are starting a new web product and your team is open to it, seriously evaluate whether you need React at all. The specialized hosting requirement and complexity of modern Next.js setups are real costs that show up in engineer time and AWS bills. LiveView and similar server-side approaches are not toys anymore.