Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

2018-06-13 Thread h2gr
I say 3. (I may be alone on this one, but I'd even suggest to consider some of the Java syntax compatibility, if this helps speed up Groovy 3. If I need to write Java code, I can always put it in .java files.) Haakon Hansen Den 2018-06-13 10:08, skrev Mario Garcia: I would say 3 as well

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

2018-06-13 Thread h2gr
I did come from Java myself, and I understand the argument to ease the transition from Java to Groovy, but as Java adopts language features from Groovy, I worry that supporting both syntaxes will create a more complex language with more options, more stuff to learn, and less clarity. Besides,

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

2018-06-13 Thread h2gr
Bloated, is the word I was looking for... Den 2018-06-13 19:46, skrev h...@abula.org: I did come from Java myself, and I understand the argument to ease the transition from Java to Groovy, but as Java adopts language features from Groovy, I worry that supporting both syntaxes will create a more