3 ms·

I tried Elixir back during the period that the Phoenix framework (the real draw - for me personally - to Elixir) was transitioning between v1.2 and v1.3. Tryin

I tried Elixir back during the period that the Phoenix framework (the real draw - for me personally - to Elixir) was transitioning between v1.2 and v1.3. Trying to figure it out while things were changing - the documentation hadn't even been updated fully yet - with old walkthrough's referencing concepts that were now being considered bad practice was overwhelming as a fairly junior dev. I gave up and went back to what I knew. With Chris McCord announcing[1] Phoenix Liveview beta and demoing it over Christmas holiday season, I decided to give the language another try (as a less junior dev than I was two years ago). All I can say is wow! What a delightful language. Pattern matching is such a joy to work with it makes me a bit frustrated it's not common in more languages. The documentation for the language and 90% of packages I've poked my nose into in the past week is concise and neatly organized (mostly due to with Jose Valim's decision to treat documentation as a first-class citizen in the language). For anyone who has been curious and heard mentions of the language, with the advent of LiveView, along with the maturation of the Nerves Project, I don't think there could be a better time than now to give the language a try. [1]: https://twitter.com/chris_mccord/status/1106291353670045696 https://twitter.com/chris_mccord/status/1106291353670045696 edit: Great video even for non-elixir/erlang devs.

QuinnWilton 8y ago
The transition from 1.2 to 1.3 was rough for a lot of people. It represented a shift from the Rails-y "Phoenix is your application" school of thought, to instead pushing people toward separating all of their business logic and persistence concerns into a different layer than the web framework. This was of course always possible in frameworks like Rails, but it wasn't necessarily encouraged by the framework, and required a lot of effort to truly achieve in practice. This change left a lot of people feeling unsure of how to structure and architect their apps, and with a lot of libraries in flux as best practises were still being fleshed out. Overall it's been a positive progression in my opinion, and I think that as the ecosystem continues to embrace lessons from domain-driven design and patterns like utilizing Phoenix PubSub as a message queue, we're going to be seeing a lot of really high quality and extensible libraries showing up. It's an exciting time to be a professional Elixir developer :)

QuinnWilton 8y ago

The transition from 1.2 to 1.3 was rough for a lot of people. It represented a shift from the Rails-y "Phoenix is your application" school of thought, to instead pushing people toward separating all of their business logic and persistence concerns into a different layer than the web framework. This was of course always possible in frameworks like Rails, but it wasn't necessarily encouraged by the framework, and required a lot of effort to truly achieve in practice. This change left a lot of people feeling unsure of how to structure and architect their apps, and with a lot of libraries in flux as best practises were still being fleshed out. Overall it's been a positive progression in my opinion, and I think that as the ecosystem continues to embrace lessons from domain-driven design and patterns like utilizing Phoenix PubSub as a message queue, we're going to be seeing a lot of really high quality and extensible libraries showing up. It's an exciting time to be a professional Elixir developer :)