Hacker News new | ask | show | jobs
by NatW 3430 days ago
Ruby on Rails or Node.js for the backend (API) and React for the front end. Rails is excellent for database migrations. Postgresql / MongoDb / Firebase for the database, depending on requirements.
1 comments

I'm saying this as a Node.js user myself so I'm not putting down Node but... Node.js is not a "Framework"

Sails.js is a framework. You could argue that Express is. But Node itself if not.

2nd this... Node.js for the 1 billionth time is not a "Framework". It is a JavaScript runtime.

Sails.js, Meteor.js, and etc... are frameworks that use/run on Node.js.

Also, Sails.js is the worst framework I've ever worked with. Never, ever use it.
I started backend development with Nodejs because I was familiar with JavaScript. I dropped sails after a month because of the lack of documentation and help available when something went wrong.

A few months later I happened to try Rails and realized that that was what Sails was trying to be for JavaScript. At some point Sails will become awesome, but until then I'll stick with Rails.