There comes a point in a developer's career where the framework/language doesn't really matter. Node, PHP, Rails, Django, etc all have their strengths and weaknesses.<p>If you are wondering which framework/language to use for a given project, the above questions won't really help you. Instead consider the following:<p>1. How much community support does the framework have?
For example, a novice NodeJS developer is probably better off using Express than, say, Koa-- which is much less widely used and documented (unless that developer likes struggling through problems). Tackling less supported frameworks can be very educational but is also risky. If you are building a startup based on something that is unstable and/or unsupported, you may accumulate some serious technical debt that could hurt you later.<p>2. Try out all your options and decide: which one's easier/more fun (for you)?
If you are trying to build a product, why bog yourself down with a framework that you find more difficult to use, just because some other developers say that it is "not as good"? Many people love ruby and python-- I'm personally not a fan of either. Does that make rails, django, or flask bad frameworks? Not at all! I just personally don't like them. At the end of the day, you are trying to make software that /does something/. I highly recommend simply picking the easiest/"funnest" route. You might even consider using parse to skip backend development altogether (it just makes you more efficient as a developer).<p>3. Are you collaborating with others?
If you don't have a strong opinion on which framework to use, why not let those who do pick their favorite for you?<p>4. Are there any special libraries/tools that you would like to use?
Not all ecosystems are created equal. Most languages have frameworks that allow you to easily make HTTP endpoints and packages to help you access databases-- which is all you need for a basic web application. However, sometimes languages will have niche libraries that make them especially ideal for a given use-case. NodeJS and Ruby have very rich ecosystems, however, there have been times where I have been forced to use python or java for this very reason. It depends completely on what you are building.<p>I typically advise people who are just beginning to learn NodeJS, so that, as a web developer, they get more comfortable with JavaScript (I see you already use express, so this may not apply to you). If you are just asking this question for the thrill of trying a new framework, and not from the perspective of using it to build anything in particular, why not try Rust Iron? I've been meaning to check that out, although I'm not sure if it is production ready yet.