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!
> Travis is the _only_ former Sails contributor (i.e. someone with actual write access to our repos)
Again, we seem to define these terms differently. I think if you told the hundreds of Sails contributors that they aren't actually contributors because you haven't given them write access, they would feel rather insulted by that.
> But please realize that this fork is not about technical issues
It's true that I think you're a lying scumbag, but I need a software stack that I can build my business on for the next 2-5 years. Sails.js is obsolete, and these issues stemming from your poor technical competence and community management are thoroughly documented on the internet.
We've been in contact with the owner of tent, and are responding appropriately. Our logo unfortunately does bear a strong resemblance to theirs, which our designers are working to resolve.
I'd hitherto not heard of tent nor seen their logo, and neither had anyone else on our team. Saying that we "stole" it is fine for sloppy internet-talk, but it imbues your statement with a level of accusatory malice that we should try to avoid.
re stock market: A common (and expensive) fallacy of beginners who think they can beat the market with clever technical tricks is analyzing all of the publicly-traded companies' history and divining patterns in trading and such. This ignores, of course, the countless companies that have gone out of business completely or have otherwise been de-listed from the exchanges.
In analyzing these trends, you're biased by looking only at the companies that have done well enough to be on the current list. In this way it's particularly insidious, because you're omitting the very data that might save you from betting on a company that might be delisted.
It will be awhile before it's fully production-ready of course, but we'll begin using it internally for developing new projects after our 1.0-beta release in February.
One note: we're using Hapi by default, but koa and express4 will be supported as well. This is part of our modularity difference.
Hopefully. We've actually seen some (mostly superficial) activity in Sails recently, which is surprising and encouraging.
Trails is actually much more modular than Sails. The goal is the same -- to make your life easier -- and the conventions are rails-like (indeed, compatible wiyh Sails) but the technical design is completely different and actually quite a bit more "node-like".
Keep in mind that Trails is not a fork, but a Sails-compatible re-write. So there's no upstream code-level reconciliation that can happen, but I'm sure both projects can coexist and compete in the framework market on their merits.
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!
He owned some of the assets, still, including the github org. Even though we negotiated an agreement, and were operating the company under the assumptions of that agreement, McNeil refused to sign it at the last minute and spent the past two months clawing everything back that he could. We still own the Balderdash LinkedIn page and npm account, for example.
He refuses to speak with me directly, so there's no resolution to this yet. Nor do we really understand why he decided on this course of action at all. I hope to bring things back to some equilibrium, but one permanent change is that we are no longer supporting Sails, and are directing all our efforts toward developing Trails.
The maintained-ness of Sails is really a separate issue from the ceo-schism drama. There are plenty of other literature which discuss the technical deficits of Sails, and the incredible amount of work it needs merely to be viable as an enterprise framework. That it relies on EOL'd dependencies, and has no plans to upgrade them, is an example.
Your assessment is perfectly logical based on the information you have available, and also mostly wrong.
First, I'm not 22, and our COO ran the largest jQuery cobsulting firm (appendTo) for 5 years. Second, McNeil did not hire us, we purchased the company; McNeil has no ownership in the "new" Balderdash. Your educated guesses about hitting metrics and so forth don't apply to anything here.
Mike McNeil needs control of Sails.js because he promised it to his VC investors behind treeline. We did not know this when we entered into the acquisition of Balderdash, and that's not what we signed up for. Since we were lied to for nearly a year, we are pivoting the company and our open-source efforts toward other things. Trails is one of those things.
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!