Re:Trails – Modern MVC Web Framework for Node.js
by jon-wood on Saturday January 02, 2016 @07:34AM
(#10826007)
> 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.
The same could have been said of Rails and Merb back in the day, but they eventually combined efforts, and rolled the concepts that people liked from Merb back into Rails. It wasn't a case of just copying the code over, but it still allowed proving the ideas in the real world.
[dead]
[dead]
Re:Trails – Modern MVC Web Framework for Node.js
by mikermcneil on Monday January 04, 2016 @02:28PM
(#10837866)
Certainly you're not alleging that I created that account to write that comment? Not only do I not have time for that kind of dishonesty, Sails was created while I was running one of those "kind of consulting shops".
Please leave me and my team alone.
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.