Our company is setting standards of what developers can and can not use. For instance languages are .Net on the Windows side and Java for Unix projects. The .Net developers are allowed to use VBScript, but the Java developers are limited to Java only. I am trying to convince the architectural group that Groovy would be a great addition for both Windows and Unix development for scripting applications and small to medium projects. The same could be said for developing small to medium web projects with Grails instead of J2EE. Any help with convincing arguments would be greatly appreciated.
You cannot convinve anyone unless you have a sample project developed both in J2EE and Groovy and explain the pros of using Groovy. I'm planning to do this by building a sample application in Java/JSP/Servlets and in particular I'm going to use Groovy for my models and beans and try to first see the difficulties myself in both the apps and then may be present it to my colleagues.
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
From what I know, the advantage to using Groovy over Java or Grails over JEE is that Groovy/Grails are just simpler. Less code, less development time, less deployment time, etc. I know that Grails uses Spring & Hibernate underneath, so those are two less frameworks your developers would have to learn.
I'd recommend showing some examples of how Groovy is simpler than Java. Groovy Beans are one way, along with Collections and Processing XML. There are lots of others, but that'll give you a good start. Get familiar with the language, play around with it, learn it really well, and when you're convinced that it would be a great language to use on a project, you'll be able to convince the architecture group.
Well, Groovy is actually Java. So if they don't ask, don't tell
The fact is that I was able to have a fully CRUD-enabled web-application up and running in 5-10 minutes. You leverage all your known skills, because groovy uses Java, Spring, Hibernate, Struts, etc. That's how you appeal to management. No new training. No real headaches.
Joined: Oct 16, 2007
Also, I want to mention that I work for an extremely conservative company that is definitely not on the early adopter list of new technologies. Time and time again, management looked at ruby and rails and decided not to allow them.
Groovy however, is allowed, since anyone who can write java can pretty much read groovy code. And, if you don't know how to do it in groovy, you can always switch back to writing your code in java. When I was first starting out writing groovy, there were definitely times I had to do that. Now, not so much.
I love closures
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com