I was talking to an old friend and telling him that I was coding a lot in Groovy in my spare time. He asked me why I wasn't coding my project in Ruby. I really didn't have a good answer for him.
In fact I just looked back at some old Ruby code of mine and it does in fact look very similar to the Groovy code I've been writing. Hmm.
Securing Tapestry pages with Annotations, Part 1
-
Everyone wants all sorts of integrations for Tapestry with other frameworks,
but sometimes rolling your own is actually easier. Let's start with securing ...
1 day ago
3 comments:
Where does the question have it's origins.... is there something deserving about Ruby that makes it 'better'? Groovy might not be the sexiest of new dynamic languages, and perhaps to the new language purists it's practically sinful because its based on the old static Java..
So i'm curious.. what does Ruby have that I'm so at a loss for when using Groovy on a solid Java stack with a huge wealth of commons code?
Its never surely just about a language alone, it about an eco-system to assure you can create apps which are robust. Twitter continues to struggle on and considering the growth it's doing admirably. Nevertheless, it's the poster child for large scale Ruby implementations... so. then.. tumbleweeds?
Groovy is certainly a lot less popular. I think I'm using it because I'm comfortable in Java. Or perhaps just because Groovy is newer.
Another reason is that when I was looking at Ruby it mattered to me that there wasn't good IDE support. Whereas after moving on to Groovy, I'm no longer looking for IDE support.
Post a Comment