3 ms·

Thank you for your commentary, allover. You do bring up a good point, I think. It does address a slightly different issue than I wanted to bring up though. C

Thank you for your commentary, allover. You do bring up a good point, I think. It does address a slightly different issue than I wanted to bring up though. Consider this: I can still use Delphi to make Windows apps too, but where am I going to find a job? Being able to use an old tool isn't my point. My point is that while you may still be using Express.js where you work, there are many other Javascript companies who aren't using it anymore. They've moved on. Even the Express.js developers have moved on to something else (Koa), so by mastering Express.js, you sort of paint yourself into a corner in your career. You most likely won't show up on recruiting radars, since you don't have the latest JS buzzwords on your résumé, and if you try to go get another Express.js job on your own, you'll have a more difficult time of it. The high turnover rate of JS frameworks works to your detriment, I would think, because it is more difficult to keep up with all the moving targets. If JS programmers don't see their framework-du-jour culture as a problem, then by all means, keep doing it. I just think you'd be better off, and attract more developers, if you congregated around the best framework or two out there, and worked to make them the best they can be, instead of re-inventing the wheel every other day. I'm simply bringing it up as a point to consider for making the JS community more stable and cohesive, and worthy of personal investment. I know this fly-by-night aspect of the Javascript community is one of the reasons I don't bother with server-side JS. I know a lot of other developers in my area who feel the same way. Just something to consider...

allover 10y ago
> 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.

allover 10y ago

> 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.