Hacker News Reader

Comment by dev_l1x_be | Hacker News Reader

These "why I chose articles" can be summed up adding: because I like it more and I cherry picked some facts for justification.

View on HN

Exactly, this is all blogspam at this point. Ignores all the features available in Rails so he can pick Elixir/Phoenix the “winner”.

that’s fair, though the intention wasn’t to dismiss rails or crown a winner. it was more about sharing a personal experience with elixir and phoenix for a specific use case, not a comparison to discredit other frameworks. i haven’t discredited rails, but features like fault tolerance and the beam make phoenix especially robust. i also mentioned that rails is a beautiful framework, i just chose what felt best for my project.

> Rails Hotwire really caught my attention, especially because of how fast you can build an MVP with Rails. But I still needed background jobs, real-time updates, and two-way communication that just works. Those things are possible in Rails and Laravel, but they take a bit more effort to set up.

All of this is built into Rails tho.

That’s why I didn’t like this article, feel free to pick whatever you want and explain the benefits, but if you do comparisions at least try to come accross as well informed. But it sounds like you haven’t started a Rails project in years

That’s fair, Rails + Hotwire is excellent for building fast MVPs. What really set Phoenix apart for me was the built-in real-time layer (via channels), the BEAM’s fault tolerance and concurrency, and how effortlessly it scales with background jobs, PubSub, and LiveView without needing extra services. Rails can absolutely do all that, but Phoenix gives you those capabilities natively with far less setup and overhead. I appreciate your feedback, I’ll definitely try to add more details in the next one. Also, I’m not implying Phoenix is better than Rails or Laravel.

Reply on news.ycombinator.com