JS has multiple full stack frameworks similar to Rails. There is even a framework called Sails...
The problems people solve with JS are different from the ones solved with Rails. Which is why the frameworks look different.
JS has multiple full stack frameworks similar to Rails. There is even a framework called Sails...
The problems people solve with JS are different from the ones solved with Rails. Which is why the frameworks look different.
> JS has multiple full stack frameworks similar to Rails. There is even a framework called Sails...
But it doesn’t. Rails is not just a full-stack framework. It’s the entire ecosystem of gems that magically just work together. What JS has is like the Temu version of Rails.
I don't know to what extent that's true compared to the npm ecosystem, but the js ecosystem largely rejects the monolith framework approach. It's focused heavily on frontend / browser, and the most popular JS frameworks are really just backends for frontend. Its most common to have a separate backend, perhaps in a different language, and it's an approach I prefer.
And I think rejecting the monolith is a massive mistake for the average CRUD app.
And it’s not like I’m not familiar with JS/Node, it’s the ecosystem I’ve spent the most time over the last 15 years. I’ve just seen so much wasted engineering effort in that time. Not sure what the exact multiplier is, but gut feeling says you’d typically need at least 2x the amount of engineers when using Node over Rails.
Haha that comparison made me chuckle out loud. It's true though.