Playing with Play Framework for Java

Recently I’ve been playing more seriously with the Play-Framework. Play is a newer rapid development web stack for developing web applications. My impressions in short: this is a very nicely framework for write applications, with much potential but which is at the very beginning. This means there aren’t awfully many features available (compare with Lift, also a recent framework for Scala on the JVM).

Good parts

The good parts I’ve found are:

  1. Java (JVM) based
  2. Aims for fun for developers
  3. Fast turnaround, automatically reloads Java classes, templates etc. which is one of the main gripes I have with Java, as stated in my “Java dead?” post:

    Rapid development and rapid turnaround. Java still falls flat, even with JRebel which allows seamless reloading of classes, RAD web frameworks like Wicket and splendid IDEs. Rails, Django and PHP are better and have a faster turn around. Period. Java is lacking here, and reloading changes look to be the biggest problem with Java development today.

  4. Real world developer oriented, not power oriented or hacker oriented. For example errors are shown in a nice way with the corresponding code in the browser.
  5. Error handling in Play

  6. Interesting modules available (Guice, Sass, GAE, OAuth), more Rails oriented than classic Java (which is a good thing!)
  7. No need to write getters and setters, they are automatically added. Another one of the gripes I have with Java
  8. Based on JPA, but other persistence like Siena supported
  9. Scala possible (Shorter, even nicer). Downside: Not as nice integrated as Lift, e.g. Option usage in Lift, composable attributes for domain classes
  10. Integrates Unit, Functional and Selenium (often aceptance tests) tests in one web page. Different testing styles can be used, e.g. JUnit with asserts, JUnit with should, Spec style and more.

The things I don’t like so much

There were some parts during my playing around, which I didn’t like with Play:

  1. I would prefer the Lift (or StringTemplate) way of templating, with no code in templates (or the RIFE way)
  2. Not on the NoSQL bandwagon – NoSQL really is the future for some web apps I believe
  3. Wish it would use a build system, not for building, but for dependency managment, packaging etc (Gradle for example, or at least Maven).
  4. Not yet a big community, modules limited, high risk bet
  5. Minor one: Bazar? Wouldn’t have thought this is needed with Git and Mercurial, don’t want to learn a third competing DVCS

Overall an interesting new comer, which brings new ideas to the Java table. Definitely something to watch.

181 thoughts on “Playing with Play Framework for Java”

  1. Pingback: nike air max patta
  2. Pingback: hoverboard
  3. Pingback: nike free flyknit
  4. Pingback: nike blazer prix
  5. Pingback: nike.com air max
  6. Pingback: electric scooter
  7. Pingback: 長財布 夏
  8. Pingback: fifa 16 coins
  9. Pingback: fut coins xbox
  10. Pingback: fut 14 coins
  11. Pingback: buy fifa coins pc
  12. Pingback: why buy fifa coins
  13. Pingback: fifa coins sms
  14. Pingback: nike outlet uk
  15. Pingback: 芸人 時計
  16. Pingback: Oakley Pas Cher
  17. Pingback: nike air max
  18. Pingback: Marque Longchamp
  19. Pingback: ベルト gucci
  20. Pingback: ????? ??? ?
  21. Pingback: Nike Tn Pas Cher
  22. Pingback: best cs go player
  23. Pingback: csgo 2
  24. Pingback: cs go player skins
  25. Pingback: cs go m4a4 skins
  26. Pingback: csgo ak skins
  27. Pingback: cosmetics mac
  28. Pingback: go cs
  29. Pingback: nike tn pas cher
  30. Pingback: cs go website
  31. Pingback: 36v 2 wheel
  32. Pingback: ems 2015 csgo
  33. Pingback: Nike Tn Pas Cher

Comments are closed.