First, I must express my congratulations to the JRuby guys at the news that they have been hired to work fulltime on JRuby by Sun. This is great news as we may finally see a high quality Ruby VM for Java. The reaction on the Groovy list has ranged from the hysterical to the dismissive.
What do I personally think it means to Groovy? Well not a great deal actually. Groovy already has tight integration with Java and compiles to byte code hence its performance and integration is excellent. The work here lies with the JRuby guys.
In addition, I think this is a great thing for the Java community. Java has always been about offering choice to its developers, over in Ruby-land when you're looking for a web framework you have Rails and, umm... Rails. If JRuby gets Rails working on Java then it is just another choice amongst such great frameworks like WebWork, Cocoon, Rife and Grails.
And what about Grails? Well Grails' goals have always been very different, sure it was about creating a framework that had the essence of Rails, but it is the technology stack that it is built on that is important. Grails provides tight integration with Spring, Hibernate, SiteMesh and Quartz. Together they represent some of the most popular Java stacks out there that share a huge user base. The Spring+Hibernate stack is probably the most frequently used combination in building Java apps today and the goal of Grails was to create a framework that leveraged this allowing you to mix approaches.
We're also targeting tighter EJB3 support and in the future JPA support, so the direction here is very different to JRuby on Rails, which re-invents everything from scratch (controller layer, ORM layer etc.).
Overall I think this is great news and can only help improve the offering on the JVM and extend the choice available to Java developers.
4 comments:
Um, there are plenty of other web frameworks for Ruby (created both before and after Rails - remember Ruby's been around for over a decade). People have made Rails the poster child and a de facto standard in Ruby land, but it's not the only option.
I can't speak in details about the frameworks, though, since I don't spend much time in Ruby land. I just visit there sometimes.
thanks for the clarification Tom, I'm sure the hoards of users of these alternative Ruby web frameworks will appreciate it ;-)
Groovy's performance is excellent? I don't think so. Last time I checked, Groovy was much slower than Java and natively-compiled dynamic languages. Perhaps its performance is good compared to CPython and CRuby interpreters, I haven't tried them.
To clarify that statement Slava: Groovy has good performance relative to other dynamic JVM languages like JRuby which was the topic of this post.
Clearly it is no where near as fast as Java and never will be for obvious reasons
Post a Comment