Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js

Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js by Jnr on Thursday October 16, 2025 @10:53AM (#45606122)

All good, but did you know that Next.js is a full stack framework? You can have backend and frontend in the same code base. You don't need Laravel if you use Next.

[ Parent | on HN ]

Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js by rvitorper on Thursday October 16, 2025 @11:38AM (#45606716)

Next.js is still missing lots of backend stuff. Background jobs, cron jobs, queues, etc.

[ Parent | on HN ]

Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js by FredPret on Thursday October 16, 2025 @11:32AM (#45606645)

BEAM / Erlang / OTP / Elixir feels different:

- no JS (well a tiny bit ships with Phoenix but I never have to look at it), no NPM, nothing that breaks every week

- the whole system lends itself to executing on multiple cores

- GenServers BEAM processes in general are amazing

[ Parent | on HN ]

Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js by pier25 on Thursday October 16, 2025 @10:56AM (#45606183)

> You don't need Laravel if you use Next

But you do need to solve a lot of stuff that Laravel already solves for you.

[ Parent | on HN ]

Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js by akarshc on Thursday October 16, 2025 @09:34PM (#45612529)

that’s true, next.js does a great job offering a full stack experience. the difference with phoenix is that it’s built on the beam, which gives you concurrency, fault tolerance, and real-time capabilities out of the box. liveview also lets you build interactive frontends without managing separate api layers or client frameworks, keeping everything unified and fast.

[ Parent | on HN ]