I think most people simply don't get or dismiss how exceptionally awesome working on the BEAM is, including many that "just build phoenix apps" already. So many

I think most people simply don't get or dismiss how exceptionally awesome working on the BEAM is, including many that "just build phoenix apps" already. So many people never actually are in the position to deal with the kind of problems the BEAM solves so nicely, and also keep themselves in the JS hamsterwheel of neverending relearning cycles without actual progress being made. The point is that working in the elixir ecosystem gives any sohpisticated engineer _multiple_ superpowers. - for architecture/system engineers, its the BEAM/OTP - for frontend/fullstack devs LiveView is the best thing in our industry for like 95% of all use cases out there - for data engineers/... having Livebook is like Jupyter on steroids, even better when linked to the production systems and Ecto is just outstanding as an ORM take, especially when comparing to much weaker options in the JS ecosystem, and don't get me started on orchestration or data pipelines with broadway - for AI enthusiasts all the machine learning stuff is at your fingertips already, with bindings to the native libs also used by python but more ergonomic and a lot of QoL over python because of the strictly better BEAM capabilities + toolings - ... There are a few areas I can highlight above where the tech absolutely excels so its the best or one of the best options in general. The magic then is that Elixir is also like 80-90% in nearly everything else with the only 2 shortcomings being raw computation speed (native libs can help as usual, easy with rust) and deployment being more complex than Ruby/Python since you should link the server nodes (no-brainer with hosters like fly)