sails

I was just talking about this topic of whether we really has any Rails-influenced JS frameworks out there in the wild. And I struggled to come up with anything off the top of my head other than Sails.js [1]. RedwoodJS looks interesting, what about it in particular do you find exciting? [1] https://github.com/balderdashy/sails

I've never tried Sails, but I'll note that it has a very bad reputation in the node community for many years, with particular scorn heaped on its poor documentation, many bugs, slow development pace, and (especially) its truly bad ORM. Representative criticism: https://kev.inburke.com/kevin/dont-use-sails-or-waterline/ Or see the comments here: https://github.com/balderdashy/sails/issues/3429 Now admittedly that was three years ago, much may have changed, and this release may be amazing, but I'd suggest doing some due diligence. I've run across 6+ different projects regretting their use of Sails; I've yet to run across someone celebrating their decision. The project is troubled and probably on no one's list of "top 3 node js frameworks".

I think this thread [1] along with unstable modules were convincing enough for people not to trust their production applications with an open source project that has a shaky future. Most people who were interested in the approach moved their efforts to TrailsJS [2] [1] - https://github.com/balderdashy/sails/issues/3429 [2] - https://trailsjs.io

Perhaps, but I can assure you that Express 3 and Express 4 are completely safe. The interface set up by Express is depended on by far too many companies and other frameworks for that to not be the case -- for instance, even though Express 3 is officially unmaintained by Strongloop, the Sails core team has committed to taking over critical patches. As for the future of Express: I've only had the opportunity to get together with Doug in person once, but we've talked about this a few times in the past. I can guarantee you the last thing he wants is drama, so I'll leave the ball completely in his court there. I will say this though: keep an eye on Doug's federated projects (jshttp and Pillar). Whether or not the various pieces are released as Express 5 or not, the _code base_ is still improving and becoming increasingly standardized, rega

I'm sorry that this debacle has negatively impacted your opinion of the framework. Other open-source maintainers had warned me in the past that this kind of thing is par for the course as any project grows, but it doesn't make it any easier to deal with when it happens to you. In the mean time, it has certainly made my family's holidays unpleasant, and disrupted the lives of the rest of our team. I posted a few important clarifications here in the original issue: https://github.com/balderdashy/sails/issues/3429#issuecommen...

Travis did not play a meaningful role in the development of Sails. He was a contributor for less than a year and made a total of 37 commits: https://github.com/balderdashy/sails/commits?author=tjwebb That said, I wish Trails the best-- I just think it's important to point out information that is being misrepresented. If you have any technical issues with Sails, I would appreciate hearing about those on GitHub.

Context -https://github.com/balderdashy/sails/issues/3429

Mike wrote in here, sounds like they are just busy working on Treeline. My read: doesn't help having an ex-employee / collaborator telling everyone Sails isn't supported any more. That just seems like trolling. https://github.com/balderdashy/sails/issues/3429 > Hey Cody, thanks for sharing your concern. Apologies for the lack of transparency from our end- it's coming from a place of limited resources, not deliberate opacity. Like you said, we're a small team spread across a few large projects right now; and it's part of why we've been in more of maintenance/stability mode with Sails and Waterline over the past 9 months. > Another thing has happened too: we've become more attuned to the full lifecycle of development with a Sails app. The work we do outside of open-source has always been a huge influence on Sails-- I mean, I firmly belie

@neya yessir, or as production ready as Node.js + express + socket.io is. Here's our roadmap: https://github.com/balderdashy/sails/wiki/roadmap

@sideproject Actually you can use Sails (https://github.com/balderdashy/sails) with whichever front-end framework you like. It's architected to serve a nice clean RESTful API and leave the front-end up to you.

Great question! I'm really pumped about more folks getting involved. First off, you can manage pubsub as you like using Socket.io. The most important thing to realize about Sails is that we're not trying to be Meteor. This is for real, production projects, with a straightforward fallback to trusted technologies. How you manage publish and subscribe is completely up to you-- but if you're using the API blueprint, here's how it works from a pubsub perspective: GET /user => the socket who issued this request is subscribed to the class room, and the instance rooms for all models returned (until the socket closes) POST /user => the model created is "introduced" to the class room, subscribing all sockets connected to the class room, to IT. Then, all of the class room subscribers are notified that the new model has been created. PUT /user/n