3 ms·

There are many points in your comment that is a matter of preference... And with many of them I desagree... I used Django in the past and the "auto-migraton su

by yokaro 4y ago

There are many points in your comment that is a matter of preference... And with many of them I desagree... I used Django in the past and the "auto-migraton support" feature you are talking about is great but not perfect. It is even mentioned in the official documentation. I have been myself in situations where it created unwanted behavior. So I can understand the Elixir core team not wanting to bet on a feature that is neither perfect nor essential. > But having the unnecessary views there adds another level of abstraction making everything more complex for no reason. Hell no! Imagine how much more succinct and clear templates can be just because you moved some verbose logic into helpers defined in your views? I find that Phoenix encourages people, especially beginners, to adopt nice ways to organize their code. The generators you like them or not but you are not forced to use them. Personally I find that they boost productivity and are a very good learning tool. Finally I would say that Django did not become what it is in a day. Elixir/Phoenix is perhaps slowly but surely moving towards a future that I am impatiently awaiting.

spapas82 4y ago
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!

by yokaro 4y ago

spapas82 4y ago

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!