This is my frustration.
Where I work, I work in a QA role. The administration (who were / are Java Dev's) decided to move QA to write code in a scripting language (which is a good goal), and they choose Groovy as this language. It's fine and all... but their intention was: Let's pick a language easier to pick up and use than Java.
The problem is people who don't know Java very well (like me) have a very difficult time picking up Groovy. A language is only easy to pick up as there are beginner resources available. All learning resources on Groovy really target Java Dev's. Each book I pick up has a target audience of experienced Java Developers. Unlike Ruby, where I can find dozens of learning resources aimed at a true beginner. When I see material that explains that == in Java is not the same as in Groovy and Groovy treats it as a .equals and on they go, it's really lost on a guy like me... I have to first learn what this means in Java... get that understanding then roll back to Groovy and get an idea of how equivalence is different... and man what a waste of time, if my end goal is Groovy.
So this "easier" language really requires the individual to first learn Java... get some experience in Java... then roll back to picking up Groovy. Which invalidates the whole point in my case (the point being to pick a scripting language that is easy to pick up and the user doesn't have to learn Java.)
What a lot of people making decisions to force Groovy as official languages in companies, don't understand, is that not everyone is a Java developer. Typically QA roles are not Java Dev's or SDET's... So the enforcement of Groovy is fine, if Groovy was really aimed at beginners as well as Java Dev's... but it really isn't. I've found one so called "beginner's" tutorial online for Groovy. but it isn't really that good. I really wish there were many resources out there for Beginners to OO coming to Groovy - i.e. like the Ruby/Rails community has.