the blog for developers

Groovy and IDEA, a mixed blessing [Updated]

I’ve been an Intellij IDEA user from the very, very beginning. I think we bought some of the first licenses. I’ve been promoting IDEA against Eclipse cultures for years. IDEA is the most usable IDE around. I’ve got several companies I worked for to buy IDEA although they are Eclipse shops. I got all people in the team I manage to use IDEA instead of Eclipse. I converted Eclipse users. I’m an evangelist. I love IDEA!

Now I’ve been working on Grails for some time, thinking about using it in a project and deciding if it’s better than JS for the task. And the Groovy support in IDEA is very very bad. The plugin is not from Intellij, but it reflects badly on them. So I have to decide if I should use Grails for the project, drop IDEA and move to Eclipse or drop Grails and stay with IDEA. Groovy with the current plugin is no option in the long run. Going to the forums on the IntelliJ site reveal lots of discouraging comments by IntelliJ employees. Groovy seems to have a much lower priority than Scala (very nice, but who uses it?), Ruby, Python and JS. And that although Groovy seems a natural choice for Java. When I, a long time IDEA user drop IDEA as a Java developer, they will lose a customer from their core group (Java developers) which sounds stupid from a marketing and sales point of view.

What a difficult choice, but currently I lean on dropping IDEA, after all those years. What can the Grails/Groovy community, the users and developers do to get better support from IntelliJ?

Update (see comments): “Actually right now the situation regarding Groovy support has changed, which you may have found out from recent forum posts. We are no longer actively developing the Scala plugin, and the team responsible for it is now working on a new Groovy plugin.”

You can leave a Reply here. Of course, you should follow me on twitter here.

You can share this post!
Do you want to tell others about this article? Use the social bookmark icons to submit this artice to the service of your choice. Thanks.

About the author: Stephan Schmidt has more than 15 years of internet technology experience and 10 years experience in agile. He was head of development, consultant and CTO and is a speaker, author and blog writer. He specializes in organizing and optimizing software development helping companies by increasing productivity with lean software development and agile methodologies. Want to know more? All views are only his own.
Leave a reply.

Comments

Hi Stephan,

Actually right now the situation regarding Groovy support has changed, which you may have found out from recent forum posts. We are no longer actively developing the Scala plugin, and the team responsible for it is now working on a new Groovy plugin. Right now the work is at a very early stage, and we don’t have any definite release plans or timeline. But the work does proceed quite actively, and just like the Ruby and Scala plugins, the Groovy plugin is developed under an open-source license. I’m sure that the guys working on the plugin will be happy to accept code contributions once the plugin is a bit more mature and stable.

stephan

Hi Dmitry,

that sounds good, thank you.

Sam

I agree with you on the situation with Groovy and IDEA. The current plugin is virtually worthless and using notepad would be almost as effective an IDE as IDEA at this point. Hopefully the IntelliJ development team will take this more seriously since it’s becoming clear that Groovy will be the most popular choice of scripting languages used by Java developers who have to continue to code with Java as well. Only people who are looking to drop Java entirely are looking at other languages like Ruby.

Leave a Reply

What people wrote somewhere else:

Additional comments powered by BackType

Guide to CodeMonkeyism

Over the last 4 years I wrote many articles on this blog. To make it easier for you to find the relevant ones, I've organized them into topics.

Top 10

6 reasons why my VC funded startup did fail

Go Ahead: Next Generation Java Programming Style

Java Interview questions: Write a String Reverser

The dark side of NoSQL

7 Bad Signs not to Work for a Software Company or Startup

Is Java dead?

Scala vs. Clojure

Never, never, never use String in Java

No future for functional programming in 2008 – Scala, F# and Nu

Clojure vs Scala, Part 2

Java Developer

Is Java Dead?

Go Ahead: Next Generation Java Programming Style

Be careful with magical code

All variables in Java must be final

Never, never, never use String in Java

Bending Java: More readable code with methods that do nothing?

NoSQL Guy

NoSQL: The Dawn of Polyglot Persistence

The dark side of NoSQL

Essential storage tradeoff: Simple Reads vs. Simple Writes

Sharding destroys the goals of your relational database

The unholy legacy of databases

Startup/CTO

Development Dream Teams

6 reasons why my VC funded startup did fail

American vs. European style of Software Development

12 Things to Reduce Your Lead Time and Time to Market

The high cost of overhead when working in parallel

Essential storage tradeoff: Simple Reads vs. Simple Writes

Job Seeker

Another Good (Java) Interview Question

7 Bad Signs not to Work for a Software Company or Startup

Java Interview questions: Write a String Reverser (and use Recursion!)

Java Interview questions: Multiple Inheritance

As a Manager: What I value in developers

Top 10 Tips (+1) to Get a Pay Raise

Agilist

What Developers Need to Know About Agile

5 Practices Better to Change in Your Scrum Implementation

Scrum is not about engineering practices

ScrumMaster and ZenMaster: The joke of certification

What is Trans-Scrum?