# Phoenix Framework

85 Hacker News commenters recommended Phoenix Framework and 11 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months; owners who said how long report a median of 8 years (7 owners). It meets the Hacker Approved badge rule.

**Verdict:** Developers recommend Phoenix for fast, low-overhead web apps with real-time features and little client-side JavaScript. Caveats: a steep learning curve and friction during upgrades.

## Why people recommend it

- Helpful for LLM-assisted coding (3 comments): "It's token efficient (because of code generator), has great static analysis, and terse (because functional)." ([source](https://news.ycombinator.com/item?id=48526079)) "Just so quick and easy, and the LLM seems to get things right quite often." ([source](https://news.ycombinator.com/item?id=48482515)) "LLMs seem to have an easy time with Elixir and Phoenix in my testing." ([source](https://news.ycombinator.com/item?id=48303725))
- Little or no client-side JavaScript (3 comments): "With Phoenix you can write actually 0 code that runs on the client, just the backend and html templating." ([source](https://news.ycombinator.com/item?id=48294510)) "I also switched to Phoenix using Js only when absolutely necessary." ([source](https://news.ycombinator.com/item?id=46032749)) "It's extremely nice! Coming from the React and Next.js world there is very little that I miss." ([source](https://news.ycombinator.com/item?id=46241083))
- Fast responses and low memory use (3 comments): "we were measuring responses in microseconds on local dev machines, and under 5 ms in production with zero optimization" ([source](https://news.ycombinator.com/item?id=46450756)) "delightfully fast and not having to deal with two entirely different application stacks" ([source](https://news.ycombinator.com/item?id=48289510)) "it's hard to argue with a 10x reduction in memory usage and latency" ([source](https://news.ycombinator.com/item?id=50181051))
- Real-time features via websockets (2 comments): "with elixir/phoenix you just push all that complexity to the backend and trust in websockets and the BEAM" ([source](https://news.ycombinator.com/item?id=47030444)) "I already knew Phoenix well, LiveView fits my use case, and websockets setup with Phoenix is very clear" ([source](https://news.ycombinator.com/item?id=48103676))

## What people warn about

- Hard for newcomers to follow (2 comments): "the differences in Phoenix 1.7 are enough to break the tutorials enough to confuse a newbie" ([source](https://news.ycombinator.com/item?id=48391274)) "I didn't understand how a Phoenix app booted, didn't know where to edit my config." ([source](https://news.ycombinator.com/item?id=48388860))
- Heavy middleware adds overhead (2 comments): "It really takes surprisingly little volume to cripple a return-hello-world Phoenix app that indirects the "hello world" behind way too much middleware and message passing" ([source](https://news.ycombinator.com/item?id=48387316)) "Elixir with Phoenix and Liveview is super bloated" ([source](https://news.ycombinator.com/item?id=47071599))

## 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
- [Laravel](https://hackerapproved.com/p/laravel.md): 71 recommend
- [SvelteKit](https://hackerapproved.com/p/sveltekit.md): 67 recommend

## Cite as

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