3 ms·
Phoenix, for a lot of the same reasons I used to have for Rails including: * Fast development cycle * Conventional * Great community * Good ecosystem of lib
by bwilliams 10y ago
Phoenix, for a lot of the same reasons I used to have for Rails including:
* Fast development cycle
* Conventional
* Great community
* Good ecosystem of libs to take advantage of
* "Magic" (although Phoenix's magic is much different)
And some of it's own like
* Great concurrency (which feels like a free win over Rails)
* Functional programming
* How Ecto, the ORM works
* How simple it is, even with the "magic" included.
* How assets are handled, via a thin layer to Brunch, Webpack, or other JavaScript asset bundler
There's a few more, but I think those are a lot of the major talking points.
- jetti 10y agoI'm starting a project in Phoenix in the next week or so and am excited. I have done little web work and what I have done was using ASP.NET MVC so it is different than what I'm used to.