> "maturity" maturity is many-dimensional here. * userland packages - yes, sure. erlang/elixir ecostystem is not mature as of yet. It works, it nice, but you

> "maturity" maturity is many-dimensional here. * userland packages - yes, sure. erlang/elixir ecostystem is not mature as of yet. It works, it nice, but you can't find everything you need (including e.g. blog posts and SO answers for every possible question). * On other hand, erlang base brings stability, instruments to solve every possible _production_ issue out there. * Phoenix itself is has same mixed aptitude - it's pretty new and, at same time, written by core rails dev and therefore has many design issues fixed from start. > "it's magic and that's bad" IMO it's not the magic that hurts but overtwisted internal logic where you can't figure out how it works exactly (and yes, Rails became pretty complicated software). Keeping things simple (at least "mental model" of things) is damn hard :( Phoenix is basically == "rewrite from scratch to reduce complexity and fix things that can't be fixed without starting from scratch" > convention-over-configuration i like that! Also, both Rails and Phoenix doing it right. 90+% other frameworks failing miserably :(