Wednesday, April 28, 2010

I wish the Play framework was available when I did server side Java

Before I started using Ruby about four years ago, almost all of my web development was either J2EE or plain old JSP apps (with some fun experiments with Lisp, Scheme, Prolog, etc.)

Even though Rails is my "go to" platform for efficiently writing web apps, I like to keep up with Scala + Lift, Java options on AppEngine, Clojure + Compojure, Seaside, etc. I just revisited the Play framework and I must admit some real regret that something like Play was not available when I did a lot of server side Java work.

Play borrows a lot from opinionated frameworks like Rails and a quick study is enough to be productive largely because of the similarities to Rails in the ease of setting up routes, database access, nice MVC separation, etc. Probably the neatest feature of Play is that Java source code is compiled on the fly using the Eclipse Java compiler so if you edit a Java controller of model file and refresh a web page you instantly see the effects of the code change. There is a Scala sub-project of Play also.

3 comments:

co said...

have you try grails?

grails is awesome, i have use rails and grails, i must say grails is far superior and more performant.
Play is nice as well

Mark Watson, author and consultant said...

Hello co,

I don't use rails because I don't use Groovy. I have nothing against Groovy but I use Ruby as my "go to" language to get stuff done so Rails is a more natural choice for me.

I do have good Java skills however which is why I keep an eye on the Play framework.

co said...

mi name is carlos,

as you know your java skills move quickly to groovy skills.

My problem with ruby is just the virtual machine and garbage collector. Nothing beats the jvm

greetings from chile, i always read you