I've been using Sails 1.0 in production for the past year and haven't had any problems. Excited to see this fully released!
My experience has been that Sails dramatically improves productivity and efficiency for me and my team. As for the ORM (Waterline), we primarily make CRUD apps and haven't had a single problem with it. But, in cases where you might want more fine-grained control of your query, you can always drop out of Waterline and write native queries.
Sails isn't perfect, but it provides native access to any of the components it uses, so if you ever want to drop out and work with Express and your datastore directly you can do that.
Sails is a convention-over-configuration framework, meaning if we all agree on certain conventions then we don't all have to reconfigure every time we make any app. I think that's very difficult for people that are new to the framework, because they haven't learned the conventions yet, and they are used to doing things a certain way. But if you're willing to embrace Sails' conventions there is a huge upside in productivity.
I don't usually do this, but I find both idealboy's and luislobo's comments to be somewhat suspicious. I can't for the life of me imagine that they were paid to post positively about a crappy node framework, but one of them has few previous comments, and the other's history is... odd to say the least (including a previous similar accusation).
My sincere apologies if I'm wrong about this, but my experience with Sails (and its 'culture') has been sufficiently negative that I wouldn't put it beyond its leader(s) to pay some semi-real accounts to post in favor of it. The alternative is lack of dev experience though, so maybe that's it.
I find your comments suspicious. Perhaps you’re part of a Russian campaign to sow discord in the open-source community? My sincere apologies if I'm wrong about this, but from your comment history it sure seems like it.
Either way, I prefer to encourage the fine people that contribute to our ecosystem instead of degrading their contributions. But to each their own I guess.
Yeah, I kind of expected that response. I'd say my comment history doesn't indicate anything like that. So your point is is not a very good one.
I'm happy to hear you actually like the framework. I just was truly suspicious and felt it was worth saying.
Also, I also prefer to encourage fine people who contribute, which is exactly why I raised this suspicion. If you're a contributor, I wish you'd contribute to something better, but I commend you for doing so anyways.
My experience has been that Sails dramatically improves productivity and efficiency for me and my team. As for the ORM (Waterline), we primarily make CRUD apps and haven't had a single problem with it. But, in cases where you might want more fine-grained control of your query, you can always drop out of Waterline and write native queries.
Sails isn't perfect, but it provides native access to any of the components it uses, so if you ever want to drop out and work with Express and your datastore directly you can do that.
Sails is a convention-over-configuration framework, meaning if we all agree on certain conventions then we don't all have to reconfigure every time we make any app. I think that's very difficult for people that are new to the framework, because they haven't learned the conventions yet, and they are used to doing things a certain way. But if you're willing to embrace Sails' conventions there is a huge upside in productivity.