I reviewed Trails and found that it's direction was different than that of Sails. At some point, we will likely need to identify those differences in detail. For now, I would say that Sails values the productivity of ActionPack (ActionController, ActionView, use of Prototype), leaving the complexity of persistence alone for now, where Trails seems to think that ActiveRecord and the ActionPack's Scaffolding stuff is what makes Rails. Actually, after having used Hibernate 3.0 and Tapestry 3.0 extensively myself, I think Trails could be useful to some folks. But not to me. We have some great ideas for Sails that go beyond my original vision...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just FYI - if you have missed it :)
https://trails.dev.java.net/
Best regards
Thanks for the heads up.
I reviewed Trails and found that it's direction was different than that of Sails. At some point, we will likely need to identify those differences in detail. For now, I would say that Sails values the productivity of ActionPack (ActionController, ActionView, use of Prototype), leaving the complexity of persistence alone for now, where Trails seems to think that ActiveRecord and the ActionPack's Scaffolding stuff is what makes Rails. Actually, after having used Hibernate 3.0 and Tapestry 3.0 extensively myself, I think Trails could be useful to some folks. But not to me. We have some great ideas for Sails that go beyond my original vision...