4 ms·
Did you try version 0.9.x? 0.10.x has been a lot better, the docs have also gotten a complete revamp. I'm building my SAAS product in it and haven't found any d
by mithras 12y ago
Did you try version 0.9.x? 0.10.x has been a lot better, the docs have also gotten a complete revamp. I'm building my SAAS product in it and haven't found any dealbreakers. Still quite some gotcha's, I'll give you that.
- smt88 12y agoI gave up for reasons above, but the reason I've never looked back is that Node wasn't the right tool and the Sails developers didn't have a philosophy I could agree with. My problem with Node is that it's really hard to learn a code base and really hard to debug. In other languages, I can CTRL+click to get to definitions of classes and methods. I never realized how important that was to me until I was trying to read the Sails code. It was like following a maze. I now use Node as a very simple API layer when performance is absolutely a necessity, but I don't start with it. There's a reason there's a new [x language]-to-JavaScript transpiler announced on HN every day. As for the developers, I was just disappointed that they would ship something so broken. It would be better not to publish it at all, or to keep it on the dev branch, than to publish it in that state. I also like to use libraries with lots of third-party activity, and it seemed like only 2 people were committing to the Sails code base.