As I've written before... THe deal with Groovy is I spent a year solid doing nothing but Ruby. Then I spent significant time with Groovy (still do for the day job). I've found Groovy to look good on paper, but has a lot of warts. It's kind of a hybrid language with Java, which has some positives, but there is a lot of baggage that goes along with java. Like monster stack dumps, lousy APIs based on Java APIs instead of clean slate, awkward access to many of the cool features, crap like getting the lame java array to string behavior, bizarre access to the command line calls.... just a lot of little stuff that adds up. If I'd never used Ruby before Groovy, I'd probably be more accepting of the warts. And let's be honest, Grails is a copy of Rails. And still doesn't have database migrations, which is one of my favorite rails features. The innovation rate in the Ruby community seems a lot faster than the Groovy community to me as well, so I'd rather be there.
So obviously, if I'm going non-Java lang I would go JRuby on Rails. I'm personally curious if there are any decent Java (the lang) web frameworks out there - there are so many there has to be a handful of good ones. Wicket has been mentioned a lot - what specifically is good about it? Same with spring. These were the 2 I had been thinking about before this thread popped up. On Sep 25, 8:20 pm, Steven Herod <[email protected]> wrote: > > And don't say Grails please, as I might as well just use JRuby on > > Rails.... just wondering if there is a good java web framework out > > there that is as rails-like as java can get? > > Actually, having done Grails and Rails (JRuby and Ruby), I'd still do > a Grails app over JRuby on Rails. > > Main reason is deployment, I've run into a few native extensions in > Ruby that don't work in JRuby and its just annoying in that regard. > > I basically stopped paying attention to Java Web frameworks after > discovering Grails, although I'm still looking for something that > makes the whole forms based data collection side of things completely > painless. > > ExtJS is good if you can deal with the JavaScript, A ExtGWT is a bit > more painful - it's not 'GWT with prettier controls' as I first > thought. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
