Hacker News Reader

Comment by hit8run | Hacker News Reader

Did anyone use both Rails and Sails and could elaborate a bit about the development process compared to Ruby On Rails? I had a brief look at the boilerplate project sails generates supporting login and payments but I found it not as clear as Rails. But I use Rails for about 9 years now and therefore I am used to it.

View on HN

I used Rails 3.2 and Sails 0.12 in the past.

The lifecycle callback methods are almost identical to Rails. Waterline is an absolutely awful ORM for database management: You have almost no granular control over joins on MySQL tables. Additionally, the third-party libraries available for Node.js are much more sparse than the Rails' ecosystem.

Having said all of this, I am still very excited to upgrade my Sails API to 1.0 and take advantage of all of the new ES6 features.

I used rails about 3 years with multiple versions, and recently started to work on Node.js. Typically pure express-based websites tend to become quite messy, at least the projects I worked on. Started a new site with Sails.js 1.0 (beta) recently. It's definitely not as solid as rails. But overall I am pleased so far, except some shortcoming, ex. the lack of out-of-the-box migration system.

I agree. The documentation feels lacking as well, though maybe it's gotten better for 1.0. There's no equivalent to the Rails Guide which was something I've taken for granted. One of the sails devs came out with a detailed book but it uses Angular 1.x as part of the examples.

That said, this is probably still the best nodejs framework. It's one of the few that support relational databases.

Reply on news.ycombinator.com