Yeah, some programming experience with: Java, C, C++, python, javascript, ruby and php. I have build some simple android and desktop apps. Nothing production quality.
------------------------------
CHOOSING A FRAMEWORK:
These are some things I have been considering (the list falls short):
-Does it attract good developers? is the community large enough?
-Fast prototyping.
-How will it handle scaling issues? new features?
-Are companies moving away from it? why?
------------------------
JOB:
Anything that uses the framework I pick. I was thinking RoR/React but it's just a thought.
Picking a framework to get started isn't a lifelong commitment. So trying to optimise for these 5 factors (the 4 you listed, plus being able to get a job) at the same time is overkill, and unlikely to result in a better decision.
Just pick one. You will not regret starting with Rails or Django, providing you put in sustained effort to learn best practices.
Re: 'fast prototyping', the RoR+React combo won't give you that. De-coupling the front-end and back-end of your code has many advantages, but fast prototyping is not one of them. Particularly as you'll be learning as you go, with two different languages (Ruby and JS) and two frameworks, you'll spend twice as much time stuck.
Yeah, some programming experience with: Java, C, C++, python, javascript, ruby and php. I have build some simple android and desktop apps. Nothing production quality.
------------------------------
CHOOSING A FRAMEWORK:
These are some things I have been considering (the list falls short):
-Does it attract good developers? is the community large enough?
-Fast prototyping.
-How will it handle scaling issues? new features?
-Are companies moving away from it? why?
------------------------
JOB:
Anything that uses the framework I pick. I was thinking RoR/React but it's just a thought.