On Wednesday, 20 June 2012 22:17:02 UTC+5:30, Dominik Dorn wrote:
From looking at active web, I don't see what should be better there
than in play.
Well, if you look closer on the docs, you'll find that it's closer to RoR with ActiveRecords, default routes, coding standards and naming conventions--feel free to correct me if I'm wrong. If you look Rocket Framework's doc
http://www.scooterframework.com/docs/lovely_features.html , some of these may be possible through Japid and Rhythm--but none of these are available in Play! by default. By merely looking at the docs, both ActiveWeb and Rocket Framework seem to lack Auth and ACL; but they seem to have more features--especially closer to RoR.
as for you posting _always_ about other frameworks, it makes me wonder
if you have
ever really created a project in play or are just here to do bashing.
Hmm... while it's good to post such defamatory remarks--to gain ingroup acceptance, it won't help you really. I know bunch of CakePHP aficionados and bullies who now hide their PHP skills and claiming to be Rails and Python experts. FWIW, I came to Play! only because of Scala (at that time, I didn't like Java) and JVM. While trying Play! Scala, I came across weird compiler errors. So, I switched to Play! Java and found it much better as there's no claimed benefits of LOC reduction nor productivity increase in Play! Scala. We used Japid, Deadbolt, SecureSocial and jqvalidate; and happy with the result. Since, the buzz was that RoR is dead due to clientapp evolution, I looked at Node.js and Backbone.js and quite happy with its result. While planning to try Meteor and Vertx.io, accidentally came across ActiveWeb and Rocket Framework. If you have any good comparisons, please share.