[HN Gopher] Unpacking Elixir: Phoenix
___________________________________________________________________
Unpacking Elixir: Phoenix
Author : lawik
Score : 23 points
Date : 2024-03-08 20:28 UTC (2 hours ago)
(HTM) web link (underjord.io)
(TXT) w3m dump (underjord.io)
| atonse wrote:
| I have been such a huge fan of Ecto in general, because they have
| conceptually broken down the idea of Schemas, Changesets, and
| Repos in a way that you can use it in so many additional use
| cases.
|
| For example, you can use Ecto Schemas and Changesets to validate
| the shapes of your API requests (down to the valid values, etc)
| and provide good quality error messages. And changesets are easy
| to extend too.
|
| Ecto is probably my favorite part of the overall Elixir
| ecosystem. Phoenix and LiveView have been nice to work with (But
| still don't quite feel right, especially event handling and
| bubbling up of events up components, I wish was smoother).
|
| Overall we still really like working with this stack and the
| community is great too, in the general quality of libraries
| available.
| sabzetro wrote:
| I pivoted from C# to Elixir after a former manager (and now
| friend and co-founder) put me onto it as part of a project we
| were doing for a high volume eCommerce solution. I did another C#
| job after and then when the opportunity struck, I dove head first
| into full time Elixir development. I have no regrets. It feels
| like any problem I have can be solved with a bit of elbow grease
| and some proper thinking. Phoenix is a bit too opinionated for my
| liking, but I can't deny just how much more productive it is for
| me vs C#/.NET. All 'round, my career is the better for working
| with Erlang/Elixir.
| hinkley wrote:
| I feel like I missed the window when I could get paid to learn
| elixir on the job. Felt like that was during Covid and shortly
| after.
___________________________________________________________________
(page generated 2024-03-08 23:02 UTC)