This post originated from an RSS feed registered with Java Buzz by dion. Original Post: RE: Why Standardize BeanShell and Groovy? Feed Title: techno.blog(Dion) Feed URL: http://feeds.feedburner.com/dion Feed Description: blogging about life the universe and everything tech Latest Java Buzz Posts Latest Java Buzz Posts by dion Latest Posts From techno.blog(Dion)

RMH has written a new entry, in which he gives his thoughts on Why Standardize BeanShell and Groovy?.

I am not trying to bash the JCP, or Groovy, or BeanShell.

However:

• I do not believe that standardizing anything before there are multiple parties involved that need to put a standard touch on it
• I believe standards should come on very late in the process, to clean up and make common ground (concurrency, not EJB)
• Although I can see how some "management" like the notion of standardization. It isn't a cure. We are seeing a lot of interest in Ruby, and it isn't a "standard". It just happens to be scratching an itch. If JRuby was 100% done and solid, then a whole lot of people would be using it. This has nothing to do with the fact that it is standardized or not.

So, first, make something that is very usable and useful. Maybe later in the day it will get standardized, but why are we putting so much into that?

Just my 2p.