EOF was one of the key components of making NeXT such a powerful OS, and why it was so heavily used on Wall Street. When they created WebObjects, they, of course, put EOF behind it, and yes, it is by far the most impressive ORM I have ever used. Thankfully, a well known WO developer, Andrus Adamchik, has developed Cayanne using the same principals behind EOF: http://cayenne.apache.org/
It does a lot of magic and doesn't follow normal Java patterns, but you can look under the covers and the different programming style it uses is easy to grok.
If you are a Java dev that is sick of the architect-itus that Java developers typically suffer from, Play will feel great to you.
If you are coming from Spring MVC, JSF, Struts2 and any other large-scale framework with a lot of configuration and complex concepts, you will appreciate Play quite a bit more.
You can tell the creators are Java devs that played in the Rails arena for a while and brought a lot of that back to the Java world.
The mailing list is also quite active and releases are very methodical.
Play also works on Google App Engine, (obviously) AWS Elastic Beanstalk, Zenexity's own Playapps cloud hosting and now Heroku... nice to see innovation!
Play! is great. I have used it on my own projects and easily running on Heroku is a nice bonus.
I am not an entrepreneur, instead spending most of my work time consulting (and writing) and I generally go with what customers want but I have been disappointed a few times when I could not convince customers to use a PAAS like Heroku or AppEngine in cases where it probably made the most sense to outsource platform, admin, etc.
(code at https://github.com/lstoll/heroku-playframework-scala , basically a simple hello world app)
Many thanks for confirming.
Can anyone explain what this means in practical terms? Particularly the "meant to be deployed, not packaged and distributed" part.
It even has its own module: http://www.playframework.org/modules/dotcloud
Play and Akka are my new favorite toys when I do Java.
My buddy is looking into the framework and has run into some odd perm gen constraints because so much of the framework uses static members, etc.
I haven't talked to him about the details, and I wonder if those go away in production (since you're not reloading).
Basically, I guess I'm asking if you've seen it deployed in a largish installation?
I've been running a fairly busy application for a couple of years with Play and have yet to encounter any of the standard JVM nightmares you get with Tomcat, e.g. Permgen space etc.
As a side note, I implemented a similar (but basic) routing for Rack apps in Ruby: