The Groovy project is looking for a new home

Post by coldtea » Tue, Jan 20, 2015, 12:35 AM UTC

pjmlp wrote: post #29

coldtea wrote: post #27

Earlier quoted context omitted.

> The fact remains, though, that whatever strengths Groovy has as a language it has struggled to gain significant traction Compared to what? JRuby? Groovy's adoption, from the number's I've seen, walks all over JRuby's. It's just that the Java world is not fashionable (besides say Clojure) and you don't often hear from the people who use Groovy in their enterprise projects, whereas 10 startups using the language-du-j…

No, but you do get presentations at local JUG and those have been pretty empty of Groovy content in the last years.

Post by jfoutz » Tue, Jan 20, 2015, 1:38 AM UTC

cowardlydragon wrote: post #17

revscat wrote: post #5

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,…

NOPE. Ruby doesn't offer one of Groovy's killer features: optional static typing. And Scala... far too alien and complex. There was some talk out there by one of the original Scala dudes talking about how there are something like 30 different fundamental types in Scala. Groovy offers the most accessible functional programming paradigms to Java programmers. It is a sweet spot.

Post by mikerichards » Tue, Jan 20, 2015, 2:34 AM UTC

Post by nimblegorilla » Tue, Jan 20, 2015, 2:48 AM UTC

prophetjohn wrote: post #42

bjfish wrote: post #12

I know and use both Ruby/Rails and Groovy/Grails and wanted to debunk a myth here: "Interest in Grails/Groovy is diminishing" - I won't comment on trends but there is still a large, active user base and community I won't list the benefits of Ruby/Rails over Groovy/Grails because I will assume the audience here is familiar with Ruby/Rails. Specifically here are some benefits of Groovy over Ruby: - Very good JVM toolin…

I haven't used Groovy much, so I may be completely missing something here, but how is the elvis operator different from a simple guard in Ruby? Based on the docs for elvis, it looks like potentiallyFalsyValue ?: safeDefault is exactly equivalent to potentially_falsy_value || safe_default in Ruby Further, the null-safe operator seems to be the same as #try in Rails and overuse of either is probably a bit of a smell th…

Post by olavgg » Tue, Jan 20, 2015, 5:55 AM UTC

vorg wrote: post #28

revscat wrote: post #5

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,…

> Given this I'm not particularly surprised to see Pivotal's decision here Pivotal's decision is likely based not only on what you see, but on what else they see but you can't. They can see trends and revenues before the rest of us can, like former SpringSource CEO Rod Johnson who jumped ship over to Scala. These are some concerns with Groovy I've blogged and commented about a lot over the past few years: * the failu…