51–60 of 72 posts
I often wish it had gained more momentum before Clojure and Scala showed up.
The Java interoperation is much, much cleaner than in Jython or JRuby due to Groovy being a first class JVM language.
Earlier quoted context omitted.
No, but you do get presentations at local JUG and those have been pretty empty of Groovy content in the last years.
I think people that go to JUGs and people that do enterprise development are entirely different species...
Earlier quoted context omitted.
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..
It's also extremely good in Intellij (at least, in Ultimate...which is what I'm using daily).
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.
Groovy is a very flexible language with an elegant and approachable syntax. It provides fantastic support for concurrency with gpars. It provides the ability to write static or dynamic code. It integrates seamlessly with Java. I feel groovy has created it's own space in the ecosystem, continues to grow and has a bright future.
And just a couple of hours ago I was thinking "How come I haven't seen any articles on Groovy on the front page in a while?". Seems its hype has been eclipsed by Clojure and Scala.
Also, improvements in the Java language are eroding it's raison d'être.
Earlier quoted context omitted.
If you're gonna trash talk Groovy, at least get your facts straight. Note: Static typing which has existed in Groovy forever.
Static typing (both type-checking and compilation) was added to Groovy for version 2.0 released in June 2012.
Earlier quoted context omitted.
Sorry to turn this into a framework war, but as someone who made the move from Groovy/Grails to Scala/Play Framework, I can't imagine ever going back. Or in other words, my answer to "A or B?" is "C".
My experience with Scala Play was very different. Scala is an interminably difficult language fraught with pitfalls. It's much easier to write unreadable Scala code than Groovy.
Props to what Guillaume has accomplished, but the original raison d'etre for Groovy existing has largely been supplanted by the rise of JRuby and Scala. When Groovy was initially developed JRuby was (arguably) not yet mature enough for production, so developers wanting to use Rails under the JVM were basically out of luck. Grails was developed in response to this need. Now that JRuby is more mature (and, as of today,…
Even though Pivotal Software is an amalgam, Pivotal received most of its culture from Pivotal Labs. To the extent that you can anthropomorphize a corporation, it really, really likes Ruby. Because of CF, it's warming up to Go fast. Spring is too big and important to neglect. But it's hard to see how Groovy/Grails fit into the big picture. It's not in vogue with the top decisionmakers and it's not critical to the business - it's just something that tagged along with Spring. I doubt anyone has any idea what to do with it.
Earlier quoted context omitted.
My experience with Scala Play was very different. Scala is an interminably difficult language fraught with pitfalls. It's much easier to write unreadable Scala code than Groovy.
Agreed. Groovy is in my opinion absolutely the nicest and friendliest language to read or write. Scala has some really cool features that I would love to see in other languages, but it also has a tendency to become somewhat unreadable and is a lot harder to get into when you're new to it.