Is anyone doing any significant work with the play framework?
dabeeeenster: We're building an app that will be going into production in the next few weeks. It's not a huge application, probably around 300 hours of work.Coming from a framework stack of WebWork/Struts2, Spring and Hibernate, it's a total breath of fresh air. Everything is there that you ask for, even nice little helper methods like encrypting strings, resizing images or serving byte arrays as documents.We keep expecting to find some big shortcoming that brings about loads of painful refactoring, but it hasn't happened yet!The templating engine is simple, clean and gets out of your way. The hot reloading really does work. The fact that there is NO XML configuration in our app is blissful and a real wake up call to how absurd Spring and Hibernate configuration used to be. The error messages are almost always enough to show you straight away where the problem is.The only downside is that it completely shuns the entire Servlet API (although I appreciate that this is where a lot of the simplicity comes from). As a result you cant leverage any servlet-based components. But maybe that's a good thing.I'm seriously impressed. I thought my company was going to have to make a jump to python or ruby to get such a clean, simple well thought through full-stack framework, but we dont.