I downvoted you because there is no "right" stack. All popular languages have good web frameworks. The right one to launch with is the one your team knows the best.
I'm not sure that's the case with Javascript - there's plenty of microframeworks (express, hapi) and even a couple with bigger ambitions - like Sails.js
Last time I looked, none were comparable to Rails/Django/SpringBoot/Laravel
> I downvoted you because there is no "right" stack. All popular languages have good web frameworks. The right one to launch with is the one your team knows the best.
Surely there are more appropriate stacks for specific problem domains? Like how using R outside of data analysis is probably weird, or writing your microcontroller code in nodejs is probably a bad idea.
The law of the hammer exists, and if your tasks requires a screwdriver and all you have is a hammer it will be more challenging than need be.
You're correct but I was talking about language selection in the context of web development. There are, of course, specific domains that have language requirements.
You are setting yourself up for a much harder employee market if you're choosing something fresh and hip, though. Finding skilled js people that have experience with your framework choice will typically be harder than finding a developer that knows php and Laravel. Imho if you have no specific reason to choose one stack over another, choose a very common one (for projects where you expect to need other people to join).
Last time I looked, none were comparable to Rails/Django/SpringBoot/Laravel