BIRT 3.7
Written by: Michael Williams
Featured Refcardz: Top Refcardz:
  1. HTML5 Canvas
  2. Ruby
  3. iPhone/iPad
  4. Spring Web Flow
  5. REST
  1. jQuery Selectors
  2. Spring Config.
  3. Java
  4. Ajax
  5. Java Concurrency

Link Details

Link 380177 thumbnail
User 358746 avatar

By pepite_nl
via lunatech-research.com
Published: Mar 15 2010 / 16:31

erhaps the most striking thing about about the Play! framework is that its biggest advantage over other Java web application development frameworks does not fit into a neat feature list, and is only apparent after you have used it to build something. That advantage is usability. Note that usability is separate from functionality. In what follows, I am not suggesting that you cannot do this in some other framework: I merely claim that it is easier and more pleasant in Play! I need to emphasise this because geeks often have a total blind spot for usability because they enjoying figuring out difficult things, and under-appreciate the value of things that Just Work.
  • 64
  • 0
  • 9057
  • 13

Comments

Add your comment
User 283139 avatar

ceaseoleo replied ago:

2 votes Vote down Vote up Reply

A suggestion for anyone looking to expand on this, would be to build something in grails and play and compare. I prefer grails just because of the groovy language, but this framework does look promising

User 72237 avatar

tb74341 replied ago:

0 votes Vote down Vote up Reply

... can a project be deployed as a war file to Tomcat now? Remember looking at it way back when and that really wasn't an option (if I remember correctly that is).

User 358746 avatar

pepite_nl replied ago:

0 votes Vote down Vote up Reply

Yes it can using the play war command. A project can also be deployed to GAE using the play gae:deploy command using the latest builds

User 216023 avatar

sakuraba replied ago:

-3 votes Vote down Vote up Reply

Play is awesome. It is fun to develop, it is well thought out into most details and I switched to it from Grails and I am not looking back.

Nearly everything about Grails is implemented in a half-assed manner. It works for simple use-cases, but when you take it for a spin for your more complex domain, it quickly fails, because it was intended to work for simple "Book-Author" sample applications. Most of the documentation is based around those type of apps. Got anything more complicated? Good luck!

I could say that I switch to play because its hot-reloading is more robust, because it starts apps faster or because writing tests is a lot easier and faster to run. But those issues are not my motivation, it basically boils down to the half-assed-ness of Grails. That is the main reason why I am switching from Grails to Play. The half-assed nature of your tools will have a huge impact on the product you build. I can no longer accept waiting 1-2 years for issues to be fixed and having so many dumb workarounds for things that should just work out of the box. I dont wanna get excited again for new features just to debug them for 2 hours and afterwards find n JIRA entries for my use case.

User 283139 avatar

ceaseoleo replied ago:

1 votes Vote down Vote up Reply

you concerns about a complex domain/project, I have to disagree about. I've created a pretty complex project using grails, and the entire experience was actually really good, compared to doing the standard java way using the same tools of spring mvc, spring, hibernate. I can't compare it to play, but using the latest 1.2 release of grails, I haven't come across this half assed-ness you're talking about. I imagine you would have issues with rails in this case as well. Maybe you can expand on what you feel is lacking in the grails framework and how play improves on it, with examples.

User 358746 avatar

pepite_nl replied ago:

2 votes Vote down Vote up Reply

Play! and Grails share the same ideas and concepts. The biggest difference is that Play! is pure Java and does not rely on the servlet API. While Grails uses Spring under the hood, Play! does not delegate to a IoC framework. However, Play! of course delegates validations, persistence, etc to the appropriate libraries and make sure that error reporting is adjusted (Hibernate errors are improved for example).
I think Grails is a really good framework as well. It seems to me that Play! is more accessible because you stay in pure Java territory.

User 236075 avatar

henk replied ago:

0 votes Vote down Vote up Reply

How do you pronounce "Play!". Do you simply say "play", or do you really have to shout a little when saying it?

User 358746 avatar

pepite_nl replied ago:

0 votes Vote down Vote up Reply

You pronounce it exactly as if you were a kid totally exited by the idea of playing your favorite game ;) So there is a subtile intonation at the end indicating you are going to have a lot of fun.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.