My current #1 alternative is to manage individual nodes using something such as SmartFrog: http://www.smartfrog.org/
Are there any Java EE application servers that support sharding? Or does everyone manage their application landscapes w/ custom solutions?
1
@RobertFischer True, I've barely touched Grails' surface. Let's pick up here again once I find the time to change this.
@RobertFischer I wasn't referring to the implementation, but the developer's (usage) view. Seems pretty similar to me.
@graemerocher That's an argument I'll accept (assuming it's true). Let the best framework win …
@graemerocher I just don't buy the "Grails is better because it's standing on the shoulders of Java giants" argument
@graemerocher As I've said before, I don't even think there's anything bad about copying. And I have no doubts you've built cool stuff.
@graemerocher Point re Groovy taken and conceded. Doeesn't influence my opinion about Grails one bit, though. BTW:http://tinyurl.com/bbm2sw
@graemerocher why would I want to use JSR 311 for a dynamic language? A native Groovy REST API on top of eg. Restlet would surely be better?
@altosz +1. Real problems are never solved by any framework, library or tool, only by the people who use them.
@altosz What's next? Who knows? Maybe something built on Clojure - a much better language than either Groovy or Ruby.
@xymor That analogy is bullshit, as the similarities are *much* bigger. Copying is nothing bad, though, unless you do it badly.
@dehora Had Rails not trashed J2EE as much as it did (and thus grabbed many Java folks' attention), I doubt we'd have Grails. Or JSR 311 :-)
@altosz Grails is a very obvious copy of Rails; surely you agree? That makes Rails the original in my book (copies may be better, of course)