trails

> Worth noting that the previous devs even started over with a psuedo-fork of Sails called Trails: https://github.com/trailsjs/trails Correct. A core Sails team member (Travis Webb) left Sails and started a new project to try and fix the issues they saw with the project. > Nope, none of the Sails core team are affiliated with that. It's true that no one currently on the Sails core team is affiliated with Trails (as far as I'm aware), but that's not what was being claimed.

Worth noting that the previous devs even started over with a psuedo-fork of Sails called Trails: https://github.com/trailsjs/trails

Version 2 of Trails was released a few days ago: https://github.com/trailsjs/trails/releases/tag/2.0 We continue to build on the success of Trails v1, and continue our bi-annual release cycle to coincide with the Node.js release cycle. v3 will be released in April 2017 with a number of further improvements, including first-class support for GraphQL. Thanks everyone who has contributed to making Trails a success!

For anyone who's interested, the github repo: https://github.com/trailsjs/trails

Interesting. This was also announced yesterday: https://github.com/trailsjs/trails

Hi bnb, it hurts to see the word "stole" and judgement passed so hastily, so I thought I'd take a quick second to reply. It was only just this morning with the attention from Hacker News that we learned about the similarities between the two logos/brandmarks, and we're actively coming up with something new and different. We'll keep the community posted on the status of the new designs here: https://github.com/trailsjs/trails/issues/47 Being open, compassionate, and transparent is a huge part of what we're hoping to do with Trails, so chatting with us directly is always an option. We hope to see you on gitter! All best :)

All -- Keep in mind that Trails.js is pre-release. We're releasing 1.0-alpha on January 8, which isn't too far away. For more info on our development schedule, see our roadmap: https://github.com/trailsjs/trails/blob/master/ROADMAP.md We'll be giving some talks on Trails the week of Jan 11th; we'll be visiting local Javascript groups in Detroit, Miami, and Los Angeles that week. If you're in the area, come hang out!

Interestingly, even though the node.js community is growing quickly and has a lot of great tools, I think your options are mainly Sails.js and Meteor. Meteor, imho, focuses much more efforts around building shiny things to convincing new developers to try it out. It has gained a reputation of being a great framework for writing hello world in 60 seconds, but not for building real business applications. Sails is a great tool, but unfortunately is dying, as evidenced by the attitude of the creators (who have moved on to work on other things), and the multiple articles on hackernews and elsewhere discussing whether it is dying. That answer, obviously, is yes. It is for these reasons that we (several of the core Sails.js maintainers) decided to invest in building a new framework, where we could offer a Sails-like development experience using

Compare the new Trails JS: https://github.com/trailsjs/trails The Trails project is developing thanks to Travis Webb and team, and his reasons are described in the pull request. The Trails README includes this intro: "Trails is built and maintained by former members of the Sails.js core team, and offers an upgrade path from existing Sails applications, but it utilizes exactly zero lines of code from the original Sails project."

FYI, Sails is being replaced with Trails: https://github.com/trailsjs/trails

I wrote the comment that OP linked to. IMHO, Sails is dying, which is why many of the project maintainers have started building a successor: https://github.com/trailsjs/trails. Yes it rhymes, no it's not a fork. It's a modern re-write with modern tools and ES6, built around similar conventions.