[icedchai]

The "search for something better" is what drew me to Elixir and Phoenix. I started learning it in my spare time a few months ago. I've been doing web development, in some form, since the 90's (starting with Perl CGI scripts.) I've grown totally tired of the traditional approaches to web app development, especially over the past 10 years as JS frameworks took over, and wanted something different. The runtime (BEAM, Erlang, actors/message passing, distribution/clustering) is obviously a strong plus. Anything that gets Javascript out of the way is preferable.

[john_the_writer]

What you'll find though is that FE teams don't care what you're running the api through. And they won't know how to capitalise on the BEAM. They will send you larger and larger requests, and as nice as BEAM works, the bottle neck will aways be the database.

I've seen 8 years of Elixir, and still get asked to return the world when FE wants data. No they won't ask for bits.. They want the user info and the company info for the user, and the client list for the user, and the company details from the client list for the user.. and they want it all in one response. BEAM becomes a useful tool you'll never reach for.

[icedchai]

I hear ya. I'm mainly looking at it for smaller projects (micro-SaaS, 2-to-3 people sorta stuff), not anything with a large team.

[HerrBertling]

Since I’m coming from the FE side - that’s exactly what is bothering me. I feel like Remix is a good step into the right direction, baking a backend-ish part of the stack into the FE. And crossing the networking gap in an elegant way. I see the same in Phoenix. Well, I guess I’ll fiddle with it for a bit and see if I can even handle the stack at all.