4 ms·
Comparing JavaScript (or Node) to Rails doesn't seem right, since, like you said, one is a programming language, the other is a framework. But the reality is t
by shafyy 5y ago
Comparing JavaScript (or Node) to Rails doesn't seem right, since, like you said, one is a programming language, the other is a framework.
But the reality is that this comparisoin is what you end up with in real life decisions. Even if you pick a Node framework like Express, it will only give you a handful of tools, not really a batteries-included framework like Rails.
I haven't come across a Rails-like framework for Node. I wonder why? Didn't people try to make it? Is it because of the language specific features and Node ecosystem that it's hard to come up with a coherent, opinionated, all-inclusive framework?
- suction 5y agoI've sometimes read that Sails.js is the "Rails" of the JS world, but when "I did my own research" about it there were enough red flags experienced by real world devs that I never considered it for a project. For instance, all benchmarks I read showed a very poor performance compared to other frameworks, also very poor real world adoption so it doesn't look good on the resume. I chose to go the Rails API with a Vue.js frontend route (actually, Quasar), and I'm very happy with it.