Status of Sails.js

Re:Status of Sails.js by dvt on Thursday December 31, 2015 @10:08PM (#10820965)

I've used sails.js for many (many) projects including gameref.io, hackjob.io, and on several internal projects at my current job. I find it ideal for prototyping and small-to-medium-sized projects. I really hope it doesn't die as I love the pipelined approach it takes.

@SignMeTheHELLUp is complaining about Waterline ORM, but I'd argue that Hibernate is worse (and it's an "industry standard"). It's just a fact of life that ANY ORM will suck because it tries to build an isomorphic API over several database abstractions.

Also, come on, entire world-class companies are based on a Node.js architecture (Uber comes to mind)[1]. If you can't write solid code in Node, you're probably just a shitty programmer.

[1] https://www.quora.com/What-is-the-technology-stack-behind-Ub...

[ Parent | on HN ]

Re:Status of Sails.js by SignMeTheHELLUp on Thursday December 31, 2015 @10:32PM (#10821018)

> SignMeTheHELLUp is complaining about Waterline ORM, but I'd argue that Hibernate is worse

Are you serious. Hibernate and all it's language-specific variants are actual feature-complete ORMs. Waterline falls flat as soon as you get past eager-fetching a child property. It's a toy.

I wasn't just complaining about Waterline either. Every time I had issues with Sails I had to dip into the Sails source and patch bugs out, eventually I replaced parts of Sails with libraries that actually worked. By the end of the project the only "Sails" left was the routing component...

Edit: Of the two sites you linked to, one is a splash page and the other is an aggregator that loads slowly. Neither are real-world LOB applications with complex logic underneath them.

I can write solid code on Node the same way I can on any PHP framework, but I'm experienced enough to know to look elsewhere when my requirements are complex.

[ Parent | on HN ]

Re:Status of Sails.js by rargulati on Friday January 01, 2016 @12:17AM (#10821161)

> Every time I had issues with Sails I had to dip into the Sails source and patch bugs out, eventually I replaced parts of Sails with libraries that actually worked. By the end of the project the only "Sails" left was the routing component...

Would love to hear more about this - if time permits, would be a great write-up.

[ Parent | on HN ]

Re:Status of Sails.js by dvt on Friday January 01, 2016 @07:18PM (#10824291)

I have a feeling it's just nonsense. There's not much to re-write to begin with. Sails.js is a thin-ish layer on top of express that uses grunt to tie everything together. Waterline is the biggest component, but it's not even technically part of Sails.js proper.

[ Parent | on HN ]

Re:Status of Sails.js by dvt on Friday January 01, 2016 @07:13PM (#10824275)

I linked to toy projects, I never claimed otherwise. Some people, however, use Sails.js for real business solutions.

> I wasn't just complaining about Waterline either. Every time I had issues with Sails I had to dip into the Sails source and patch bugs out, eventually I replaced parts of Sails with libraries that actually worked.

I don't even know what this means. Sails is basically just a router on top of express with grunt tying everything together. What part of sails did you have to "replace"? The i18n? Let's not be dramatic here.

But then again, your post about staying away from Node just showed how unhinged you are. I'm no language zealot, but that's just ignorant to say when world-class companies are using Node on incredible scales.

[ Parent | on HN ]