I'm in love with the simple explicit composability of everything in the Elixir ecosystem. In Phoenix everything is a pipeline from the connection leading down t

I'm in love with the simple explicit composability of everything in the Elixir ecosystem. In Phoenix everything is a pipeline from the connection leading down through the routes, controller, etc. Phoenix is just a plug in a Mix application and it doesn't impose itself in everything I do. I'm not a Phoenix developer, I'm an Elixir developer who happens to be using Phoenix to manage web traffic. I think this is where Rails and Phoenix diverge in philosophy, Phoenix prioritizes explicitness and minimal assumptions with how and what you're going to do with their tool, whereas Rails is famously opinionated providing a 'Rails way' of doing most things. What Rails does, it is very good at, but when you move outside of its expertise, you'll may find yourself in hot-water fast. Phoenix can be what you need it to be, and when you need to do something outside of Phoenix's domain everything is composable, so pick and chose what you need.