Currently, Groovy and Grails are the non-Java things we’re most likely to work on as there has been a noticeable trend of people moving from Spring/Hibernate/etc towards Groovy/Grails/GORM. There are existing issues for Grails (http://jira.terracotta.org/jira/browse/CDV-1023) and Groovy (http://jira.terracotta.org/jira/browse/CDV-1024) if you want to vote them up.

Yes, the best thing we could do is to implement it ourself.
It’s also one of the most pleasant way but not possible in the near future when we are completly new to the products and technology. I just switch to the java platform and start learning things like zk, java, jboss rules, terracotta, have to choose between groovy and scala and so on, that’s a lot and doing what misses in them is not realistic, so due to the deep learning curve and amount of work, when nobody brings the magic :) unhappily you simply have to drop and switch to something else than can be realistic :), so the more i search for solutions, the more i see that for me Terracotta will be for the next time, if there is a next time :)

Your “second thing” is a nice proposition, do you have a Terracotta contact who would take the hand of some of the technical project responsible ? I think here as example of ZK web framework, Jboss Rules, Scala, Groovy and so on… being a kind of evangelist is, for the moment, my only potential capacity in the near future :)

I see you might be confident into future solutions around JRuby/Rails or Groovy/Grails or Scala/Lift, but which is a solution for some people can a problem for some others as for example you may be interested into groovy or scala but not into grails or lift :), well that does not sound very confortable to take a decision, and if i have to make to choice regarding the language on the jvm, that sounds more or less like a bet on the future :)

As an open-source company striving to pay it’s developers, we have to focus on big markets where the mass of developers are to get the biggest bang for the buck. For the moment, that means Java web apps built with Spring, Hibernate, Ehcache, Quartz, etc.

In the future (and maybe the not so far future), that may mean JRuby/Rails, Groovy/Grails, Scala/Lift, or whatever. So if you want those frameworks to be well supported, the best thing you could do is to implement it yourself. :) But the *second* best thing is to do what you can to ensure the popularity of those frameworks so that it makes business sense for us to spend developer time supporting them.

My hunch is that a year from now the Groovy/Grails story will be better than it is now.

Happy new year to everyone !!!
On my side, if i had a wish in the tech area and after reading “Feeling Groovy” blog article here and this current one, i would make the wish for either Groovy or Scala to be well “supported” into Terracotta.

What are the news on them if there are some and what would you advice to follow among these two for Terracotta use ?

Alex

I encourage you to blog the word and get people commenting for the good of hacker-kind ;-)

http://blog.terracottatech.com/2008/03/question_for_scala_users.html