Rails, without a doubt. Don’t waste your time on Django and all the Node stuff is just a mountain of distractions.
(I’ve been doing this for over a decade. At one point I was a Django zealot and avoided Rails like the plague. Boy was I wrong)
(I’ve been doing this for over a decade. At one point I was a Django zealot and avoided Rails like the plague. Boy was I wrong)
The difference between Django and rails is pretty small from my oberservation. They have similar ease of use and performance characteristics.
Django is a good framework. Ultimately why people choose it or something else is about your own taste. The reason I didn't choose it is that Django give users more freedom i.e. configuration over convention which for me leads to https://en.wikipedia.org/wiki/The_Paradox_of_Choice (Maybe things have changed?) It's strange because Python is the opposite in terms of philosophy. Rails goes the other direction and is very opinionated which is also strange considering Ruby's philosophy is the opposite i.e. 10 million ways to do the same thing.
The next issue is community consensus. Python doesn't seem to have it. (Again things may have changed.) You can see this with packaging and the 2x vs 3x war. Not sure if Python has finally standardized packaging yet but it's hard not having a good package system everyone uses once you get exposed to ruby gems, npm modules, and even maven.
For the record, I'm not saying Python is bad. Just giving reasons for why I personally do not use it unless I'm forced.
Currently I know Python and am using Django.
I am too lazy to learn Ruby. Is it worth it to learn Ruby just to use Rails?