What Did Node.js Provide that Rails Didn't?by@niel_malhotra
6,618 reads

What Did Node.js Provide that Rails Didn't?

tldt arrow
Read on Terminal Reader
Read this story w/o Javascript

Too Long; Didn't Read

When I graduated with a Computer Science degree at the end of 2012, Ruby on Ruby on Rails was at its peak popularity with the startup crowd. Developing a web application on Rails always felt easier and faster than with Node.js. With hosting providers like Heroku, you can deploy your application for the world to see in minutes. The default package system (npm) causes all sorts of issues with upgrading packages in Node applications. Node feels like it was made for real-time applications. The code you save by using the same language on the client and server is minor at best.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - What Did Node.js Provide that Rails Didn't?
Niel Malhotra HackerNoon profile picture

@niel_malhotra

Niel Malhotra

Programmer/Writer/Founder at Growista


Receive Stories from @niel_malhotra

react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!