Home/ Questions/Q 7619109
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T03:34:30+00:00

Up to now I’ve always used PHP with or without a framework but a

  • 0

Up to now I’ve always used PHP with or without a framework but a month ago I decided to start something new: Ruby and Rails, I found them quite easy and similar to PHP and some PHP frameworks in how they works but using a simpler syntax and many other advantages.

Some days ago I started reading about Node.js, Node.js vs Rails, “why node.js is better”…

I’m a bit confused but my objective is to learn something modern that will not become obsolete in a few months so:

What are the main differences between Rails/Ruby and Node.js and a framework based on it like Express.js (except that one is written in JS and the other in Ruby)?

What are the main advantages/disadvantages of using Node.js and framework based on it instead of a Ruby based solution like Rails?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There aren’t enough differences between Node.js and Rails for it to practically matter.

    A lot of what Node.js can do can be pulled off in Rails with things like EventMachine and Pusher. So unless you are really familiar with Rails’ limitations, and know you’ll be pushing the boundaries, you’d be hard pressed to make something a seasoned Rails developer couldn’t do.

    Having built apps in Node and Express I can say that they alone aren’t enough to make a sexy application. They can seem just as old and stale if you don’t have an outstanding frontend UI to facilitate the backend possibilities. Instead of comparing backend servers, I think the real future of doing amazing things is in front-end JavaScript frameworks like Backbone.js that use Express/Rails/Node.js on the backend.

    I have chosen to go in the direction of Backbone.js with Rails as my backend API server. Because it’s so easy to rapidly create a very nice RESTful backend server in Rails. Rails also makes working with CoffeeScript and precompiling/organizing Backbone code a breeze. There are already decent Backbone.js gems out there for Rails.

    The Rails core is also able to acknowledge and embrace the fact that frontend JS MVCs are logically a good next step, and they have been working to strengthen the bond between the two. For those same reasons they have also worked to make Rails an even better API server so that it can work with frontend JS easier. Node.js and Express aren’t putting as much effort to coordinate with frontend JavaScript MVCs as the Rails community is.

    Being good with a JavaScript frontend MVC and Rails as a backend makes you also great for both worlds in terms of getting a job. You will easily be able to hop onto a Node.js project and add value to that team with your superior frontend experience, and you can also roll with the punches on a Ruby on Rails team and add value to them as well.

    • 0