Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js
by Supermancho on Thursday October 16, 2025 @04:00PM
(#45610013)
Almost 20 years after I bought my first Erlang books, I would never recommend Erlang OR Elixir to anyone but a senior dev who likes coding on their own and want to try something different. This pool is almost 0 people, since I was someone who wanted to play with it. I found the juice not worth the squeeze, in time investment vs capability. The build system alone is enough to throw most people off.
[ Parent
| on HN ]
Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js
by cmoski on Thursday October 16, 2025 @04:44PM
(#45610452)
How is the build system a problem? It's a piece of cake to create a deployment and everything is controlled through the one cli, mix.
Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js
by Supermancho on Thursday October 16, 2025 @10:43PM
(#45612859)
> It's a piece of cake to create a deployment and everything is controlled through the one cli, mix.
* It is not, despite your own familiarity. Erlang is in worse shape, using rebar3 ofc
* There is no central package management. I want to know what library to include that will do X (or a selection of choices), if it's not in https://github.com/h4cc/awesome-elixir, I basically have to crawl github. (Lua has the same problem).
Past some toy projects, most people abandon these languages for more mature ecosystems.
Re:Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js
by Supermancho on Friday October 17, 2025 @10:05AM
(#45616964)
It's not like I don't ask about this and talk with other developers. 15 years later, the problems are largely the same as they were. It feels like these languages are stuck in echo chambers. shrug