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!
I'm interested in the Miami one. Any information?
Trails – Modern MVC Web Framework for Node.js
21–30 of 84 posts
Re: Trails – Modern MVC Web Framework for Node.js
#22Can someone define "modern" in this context for me?
Re: Trails – Modern MVC Web Framework for Node.js
#23Re: Trails – Modern MVC Web Framework for Node.js
#24Can someone define "modern" in this context for me?
Re: Trails – Modern MVC Web Framework for Node.js
#25Re: Trails – Modern MVC Web Framework for Node.js
#26Re: Trails – Modern MVC Web Framework for Node.js
#27Then I saw a point where they were using hapijs in their module: https://github.com/hapijs/hapi
That is giving me a small motivation to try some of my future weekend projects with Trails.
Re: Trails – Modern MVC Web Framework for Node.js
#28Earlier quoted context omitted.
> Hopefully this turns out like the node / io.js split and is, in the end, positive for the ecosystem in some way. I agree. I commented earlier that the Node community seems to prefer small modules over Rails-like frameworks, but I think a solid web framework would be good for Node adoption by people who prefer them and beginners.
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…
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.
Re: Trails – Modern MVC Web Framework for Node.js
#29All -- 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!
[0]: https://courses.platzi.com/courses/develop-apps-sails-js/
Re: Trails – Modern MVC Web Framework for Node.js
#30Weird situation with this and Sails right now. Sails.js development has basically stagnated in the past year, and many people in the community believe Balderdash, the company behind it, aren't giving it the attention it deserves (they have a few new projects they're working on). Travis Webb and his team behind Trails were kicked out of Balderdash (not clear if fired from the company or just removed from GitHub group)…
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.