Of course +1000 to the idea :)
2018-02-14 4:39 GMT+01:00 Andres Almiray :
> Groovy Star has a nice ring to it, specially if the logo of the program
> links to the Groovy logo :-)
>
> ---
> Java Champion; Groovy Enthusiast
> JCP EC Associate Seat
> http://an
> Or for something with a bit more pep "Groovy Vanguard Developer /
> Contributor 2018" or "Groovy Crack 2018".
>
> Contrary to Java Champions, I would suggest tying it to a specific year:
>
I like the idea of having it associated with a year, but it doesn't have
to. Explanation below.
> That wa
That depends on whether this honor is designed to promote Groovy and say
thank you to people who are doing something for Groovy and the Groovy
ecosystem right now, or if it is to honor people who have done so in the
past, whatever they are doing right now.
Would you suggest we also honor Groov
PS: The process by which Groovy honors shall be bestowed is another
point that needs imho to be carefully considered, otherwise e.g. someone
with 50+ Facebook friends can easily swing any vote (I have seen this
happen before).
On 14.02.2018 12:23, Cédric Champeau wrote:
Or for something
PPS: I do not agree with you assessment of Kotlin: Apart from it being
always statically typed (less flexible than Groovy, but sometimes just
all one needs, and definitely easier for Java-only-developers to wrap
their head around; also helps avoid the annoying "only a scripting
language" tag),
I have asked this before but have not received any reply, so with
regards to Groovy Champions: What are thoughts on crowd funding (at
least) some part of Groovy development ?
Giving someone honors is good, but giving someone money is also nice. It
would not necessarily mean that it is actual p
One other thing from the no-brainers section that Kotlin does better
than Groovy: Ctors can be called without the new keyword.
(Groovy's offer in this regard is alas severly lacking, hence nobody
uses it...)
On 14.02.2018 22:50, MG wrote:
PPS: I do not agree with you assessment of Kotlin: Apart
