5 ms·

I don't understand why the Node community doesn't have an analogous to Rails. I love the Ruby language, but given that much of my work is on the front-end, I'd

I don't understand why the Node community doesn't have an analogous to Rails. I love the Ruby language, but given that much of my work is on the front-end, I'd love to avoid context-switching between two languages for my stack. Also, with some requirements like server-side rendering, being able to natively do that in my web server is nice. I haven't used Rails since the early 2010s.

petre 7y ago
They do have Sails but it's nowhere as good as as RoR. At least prefer something fast like Fastify or Koa if using Node.js.
- cutler 7y ago
  Doesn't this kinda prove the point that Node.js is only more performant when used with micro-frameworks like Express? That Sails failed to match Rails should tell you something. A fair comparison with Express would be something like Grape or Rhoda. Node.js itself should be compared with Rack which is pretty fast.
  - JMTQp8lwXL 7y ago
    The fact that Sails never caught on to match or exceed Rails usage doesn't mean the main problem was primarily performance. Rails, for one, has a huge incumbency advantage (2004). Second, Rails is just easier than throwing together a pile of NPM modules. Imagine if you had 0 knowledge of the NPM ecosystem. It'd be quite a lot of decision making to evaluate a basket of modules that could emulate all of what rails provides.
    - petre 7y ago
      Thworing together a pile of third party NPM modules is a bad decision anyway. This is precisely why we picked Mojolicious to use as a Perl web framework: minimal dependencies, minimal breakage, reimplements some functionality. It turned out to be a good decision as it's also actively maintained compared to the others.
  - winrid 7y ago
    Sails was not in a good way when I used it...
mpfundstein 7y ago
Because Rails is a huge mega framework that tries to do everything in a very opinionated way. We need guys love to compose bigger things out of small things. :-)
Can_Not 7y ago
So on one hand, adonisjs, feathers, etc., but a lot of nodejs users consider express+npm to be their "rails".

petre 7y ago

They do have Sails but it's nowhere as good as as RoR. At least prefer something fast like Fastify or Koa if using Node.js.

cutler 7y ago
Doesn't this kinda prove the point that Node.js is only more performant when used with micro-frameworks like Express? That Sails failed to match Rails should tell you something. A fair comparison with Express would be something like Grape or Rhoda. Node.js itself should be compared with Rack which is pretty fast.
- JMTQp8lwXL 7y ago
  The fact that Sails never caught on to match or exceed Rails usage doesn't mean the main problem was primarily performance. Rails, for one, has a huge incumbency advantage (2004). Second, Rails is just easier than throwing together a pile of NPM modules. Imagine if you had 0 knowledge of the NPM ecosystem. It'd be quite a lot of decision making to evaluate a basket of modules that could emulate all of what rails provides.
  - petre 7y ago
    Thworing together a pile of third party NPM modules is a bad decision anyway. This is precisely why we picked Mojolicious to use as a Perl web framework: minimal dependencies, minimal breakage, reimplements some functionality. It turned out to be a good decision as it's also actively maintained compared to the others.
- winrid 7y ago
  Sails was not in a good way when I used it...

mpfundstein 7y ago

Because Rails is a huge mega framework that tries to do everything in a very opinionated way. We need guys love to compose bigger things out of small things. :-)

Can_Not 7y ago

So on one hand, adonisjs, feathers, etc., but a lot of nodejs users consider express+npm to be their "rails".