Phoenix LiveView 1.2 Released

Phoenix LiveView 1.2 just dropped, and on paper the big news is simple: developers can now keep their page styling right next to the page code, instead of scattering it elsewhere. The update is meant to make building apps feel tidier and faster, with the framework doing some behind-the-scenes magic so those styles stay in their lane and don’t spill across the whole site. Sounds neat, right? The comments, however, turned this release into a full-on culture war.

The loudest cheerleader was cpursley, who didn’t just praise LiveView — he used it to dunk on modern web development as a whole, blasting “vibe coded NextJS rats nests” and painting Phoenix as the clean, sane antidote to bloated, slow apps glued together with paid add-ons. That instantly set the tone: this wasn’t just a version bump, it was a values battle. Team Phoenix says this approach is fast, simple, and refreshingly old-school in a good way. One commenter even bragged about building a similar “mostly backend” app style because it feels “blazing fast” and easier to reason about.

But not everyone was ready to crown it king. One skeptic warned that mixing style and code could become a debugging nightmare, comparing it to old Rails-era messes where front-end behavior was “littered throughout your code base.” Another commenter swerved the whole debate into 2026 by asking the only truly cursed question left: if coding is now mostly “steering an LLM,” can the bots handle Phoenix too? So yes, the update is real — but the real show is the comment section split between “finally, sanity” and “here we go again.”