Status of Sails.js
I found SailsJs unfit for any projects that had even a moderately sized set of business rules. Partly due to Node&#x27;s lack of threading and partly because SailsJs feature set was a weak or incomplete copy of &#x27;real&#x27; frameworks which failed to meet needs once they had to offer anything more than an extremely light CRUD wrapper.<p>I agree with fideloper that it&#x27;s better not to use NodeJs or any of that mess of an ecosystem for projects more complex than &#x27;plumbing code&#x27;.<p>Saw this comment and it reminded me how Waterline ORM became a running joke at my office. Save yourself a headache and avoid these JS backend frameworks:<p>&gt; I can chime in on Waterline since everyone keeps mentioning deep populate! The PR for the polyfill is pretty much ready to go, it&#x27;s a recursive query runner that will run queries until the results are completed. This will increase the query count in sql adapters until the adapters understand how to interpret and build these join queries (nosql adapters don&#x27;t have joins so those will work).<p>Who needs N+1 select issues when we can have recursive queries baked right into the ORM! smh