Comparing to Rails/Ruby is not really fair because Ruby’s popularity exploded due to Rails, especially in web context. As such both the primitive and the framew

Comparing to Rails/Ruby is not really fair because Ruby’s popularity exploded due to Rails, especially in web context. As such both the primitive and the framework are closely tied (in web dev context). Whereas JavaScript is a primitive, and frameworks have gone and come based on the needs of the time. Depending on your web stack, you probably have a very different view of JavaScript. And actually I’d rather view it as that; JavaScript in the context of a web stack is just an extension of the serving framework. If you say the backend is just a simple REST API, then you fall into the SSR or not camp. If you’re not in SSR, I guess it doesn’t matter. But these days, things aren’t trending towards SSR. So your question actually boils down to, which set of JavaScript libraries will be maintained for a given stack. So the answer is: the most popular JS framework for any established full stack web framework. If not SSR though, I’d say react. Because it’s cheap and ubiquitous.