# Phoenix LiveView

58 Hacker News commenters recommended Phoenix LiveView and 10 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months. It meets the Hacker Approved badge rule.

**Verdict:** Recommended for interactive pages without a separate JavaScript frontend. Critics note server-held state limits concurrent sessions, and complex features still need JavaScript hooks.

## Why people recommend it

- Enjoyable, productive programming model (6 comments): "Elixir + Phoenix LiveView is the only "new" thing that has excited me in the past decade" ([source](https://news.ycombinator.com/item?id=46453828)) "the more I learned, the more I was impressed by the efficiency and the programming model" ([source](https://news.ycombinator.com/item?id=49276992)) "Unit test runs are fast, and testing LiveView is overall more pleasant and effective" ([source](https://news.ycombinator.com/item?id=48409358))
- Real-time interactivity for internal tools (5 comments): "LiveView particularly shines for internal tools like this where you want the interactivity" ([source](https://news.ycombinator.com/item?id=46885983)) "the out-of-the-box live UI with Phoenix/LiveView that was really appealing" ([source](https://news.ycombinator.com/item?id=49023977)) "killer tool for the sorts of apps or tools I'm likely to build" ([source](https://news.ycombinator.com/item?id=48161592))
- Fast, sends less data (4 comments): "We've improved throughput on new features by about 2x and sentry errors are down." ([source](https://news.ycombinator.com/item?id=48527140)) "LiveView can send less data than a JSON API, and the client has less work to do." ([source](https://news.ycombinator.com/item?id=49285728)) "Its architecture is explained in the documentation, that's why it's so fast!" ([source](https://news.ycombinator.com/item?id=46444292))
- Skips separate frontend framework (3 comments): "Phoenix with LiveView bypassing the need for a separate frontend framework is also a huge win" ([source](https://news.ycombinator.com/item?id=49849827)) "migrate off of the Next.js and other JS SSR rats nets to Elixir and Phoenix LiveView" ([source](https://news.ycombinator.com/item?id=47143880)) "you’re able to completely forgo the need for a frontend framework" ([source](https://news.ycombinator.com/item?id=50315289))

## What people warn about

- Server state limits concurrency (2 comments): "since the liveview state is on the server side it means that one server can't support a large number of concurrent sessions" ([source](https://news.ycombinator.com/item?id=48162832)) "its much much easier to account for this with regular HTTP handlers in other stacks though" ([source](https://news.ycombinator.com/item?id=48393720))
- Client and server state get messy (2 comments): "have you actually tried mutating state on both client and server? I have with Phoenix and it sucks." ([source](https://news.ycombinator.com/item?id=46240850)) "yes it is convenient, but on the other it could become a huge mess" ([source](https://news.ycombinator.com/item?id=48525223))
- Websocket spam and security gaps (2 comments): "how easily you can hijack the websocket and just spam random commands to your server" ([source](https://news.ycombinator.com/item?id=48388679)) "with liveview there are almost no resources on how to build a view securely" ([source](https://news.ycombinator.com/item?id=48389434))

## Alternatives hackers recommend

- [Ruby on Rails](https://hackerapproved.com/p/ruby-on-rails.md): 337 recommend
- [Django](https://hackerapproved.com/p/django.md): 277 recommend
- [Next.js](https://hackerapproved.com/p/next-js.md): 127 recommend
- [Phoenix Framework](https://hackerapproved.com/p/phoenix.md): 85 recommend
- [Laravel](https://hackerapproved.com/p/laravel.md): 71 recommend

## Cite as

Hacker Approved, "Phoenix LiveView", https://hackerapproved.com/p/phoenix-liveview/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).