I agree about some things being a matter of prefernece and also depending on the kind of stuff you are making. About the migrations; creating automigrations li

I agree about some things being a matter of prefernece and also depending on the kind of stuff you are making. About the migrations; creating automigrations like django is a ton of work. It handles all trivial and most non-trivial cases perfectly. If you have some really complex stuff you can edit the migration file (it.s normal python). I don't like organiziging stuff into per-controller views, I usually need to re-use things and create helper views, or other modules having that functionality etc. So their usefulness is diminishing. About generators, I agree about the learning stuff (I actually mentioned that in my comment). About productivity... hm it depends on how useful they would be. As for your final comment? I definitely agree; Django is a behemoth framework with more than 15 years of development time and a really huge community of contributors. Phoenix is much smaller both in age and in community so it will definitely be less mature. But I agree that it moves towards the correct goal, especially if you focus on its excellent real-time features where it really shines!