4 ms·

I really like to know why you were downvoted, because I made the same observations you did and basically came to the same conclusion. I'd add the really bad IDE

by emsy 12y ago

I really like to know why you were downvoted, because I made the same observations you did and basically came to the same conclusion. I'd add the really bad IDE support. I've met some developers that said the only thing that kept them from leaving Groovy was that Grails and Spock are really great and worth the trouble. Other than that I see Groovy's future more as a glue language and as a language for tools. Which I'd find very unfortunate because I like Groovy's simplicity & flexibility as a JVM language.

cowardlydragon 12y ago
Groovy IDE support is now really good in the groovy on grails tool suite, which is the main thing that I fear will disappear with this decision. Most refactors, pretty good line-by-line debugging, etc. Edit: GGTS is A spring-specific eclipse distribution..
- rufugee 12y ago
  It's also extremely good in Intellij (at least, in Ultimate...which is what I'm using daily).
  - emsy 12y ago
    I tried to install the Groovy plugins on a default Eclipse installation and never got the same result I got on the bloated default GGTS installation. But even with GGTS I had a mediocre experience at best. I tried the commercial version of IntelliJ two years ago and it was okay, but still lacking compared to the Java autocompletition. I'm really happy that the situation is better now. As I use Groovy more of a host for DSLs (like Gradle or Spock), I hope tooling for this areas will improve. In my eyes, this is Groovy's sweet spot.
    - rufugee 12y ago
      Auto-completion is excellent now. I'd suggest you give it another try.
michaelcampbell 12y ago
> I'd add the really bad IDE support. I find IntelliJ support quite excellent.