> JS programmers don't see their framework-du-jour culture ... > The high turnover rate of JS frameworks ... > this fly-by-night aspect of the Javascript com

> JS programmers don't see their framework-du-jour culture ... > The high turnover rate of JS frameworks ... > this fly-by-night aspect of the Javascript community .. All those things are your interpretation. But please hesitate when generalising like that and stating your opinions as fact, and think about what is actually going on here. The JS community is larger than any other, and very good at promoting its stuff (great landing pages/demos/docs, lots of conferences, podcasts and bloggers). This can give the appearance we're switching tools all the time, but actually in the few jobs I've worked, that simply wasn't the case. And on Express.js specificially, that is not a great example of your point at all. Express is still the defacto winner by my understanding. I wouldn't pick Koa, because it's a niche thing to use a framework built around generators. The fact that original Express people went on to work on it is irrelevant (though I see it could be a confusing signal to the community). And again I want to reiterate on the jobs thing, that (in my opinion, granted) you are not painting yourself into a corner picking any one framework because recruiters shouldn't be looking for any specific framework, and if you find in your interactions with them that they are, then it's up to you to set them straight.