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 instea

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 :)