Re: Anyone playing with Groovy or Grails?

>From: Carsten Haese <carsten@uniqsys.com> > > > > For example, if there exists a standardized logging method in Java, >you'd > > have to duplicate it to Python or Ruby. > >How come? If you have a standardized logging method, you would have a >Java class for that, wouldn't you? Jython can derive from and >instantiate Java classes, so the duplication boils down to a very thin >layer of glue. > > > And of course you have to maintain staff that knows the language(s). > >True, but that's also the case for Groovy. > Jython isn't Python. (Yes, I understand that its still Python only using a Java interpreter...) And in reality, there's already enough Python in the infrastructure that you're not going to spend the time and or money to replace the infrastructure. The question becomes more of which language(s) does the client want to expend resources on and which will provide the most bang for the buck? The biggest problem with RoR is that it doesn't work well when you're trying to glue it on to an existing infrastructure and you're not following their naming conventions for the tables. (Yes I know you can work around this, but doing so takes away from RoR's advantages.) I think the issue is that you do have a series of scripting languages (Groovy, Python, Ruby) that seem to accomplish the same things. (Groovy being the youngest) We will definitely start to play with it and gauge our successes as well as if there's enough buzz behind it to make it viable long term. I definitely like working with Python. Just not really fond of Python/Oracle right now and you can guess what's wrong in that partnership. ;-) -G _________________________________________________________________ Spiderman 3 Spin to Win! Your chance to win $50,000 & many other great prizes! Play now! http://spiderman3.msn.com