LiveView is a relatively new extension to Phoenix. However, it is 2021 many other web app ecosystems have caught up or surpassed its vermillion tracks. You could make reasonable and often convincing business cases for developing Rails. Ruby on Rails was a tremendous productivity booster during a good chunk of it’s early life. Plain old Phoenix isn’t enough for me to radically adjust how I think about creating new web apps or change how I staff up engineering teams. The thing about Phoenix however, is that it’s just an opinionated MVC web framework. Ecto itself is, you guessed it quirky, learning curve, etc. The Ecto ORM and Postgres integration quite well done. You can scale vertically, horizontally with a load balancer or with any fancy cluster management solution. Elixir’s template language, Eex, essentially compiles down elixir code. If you are coming from an environment where everything is explicit, the magic and convention steepens the learning curve a bit, but that’s part of the productivity tradeoff. Like Elixir itself, it is quirky & has a learning curve & elegant & you can be quite productive with it. Just like Elixir was strongly influenced by Ruby, Phoenix’s ancestral roots point to Ruby on Rails. It’s an opinionated web framework, with a bit of magic and convention in it. The Phoenix web framework is (as far as I can tell) the crown jewel of the aforementioned broader Elixir ecosytem. My overall impressions of the language, tooling and broader ecosystem are quite positive. The above is a succinct summary of my experience using Elixir. The endgame is high developer efficiency.Taking the time to climb that curve can result in elegant solutions.This is part two of a short series titled “The Sublime Developer Efficiency of Elixir, Phoenix and LiveView”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |