> > I would just start with point 1 and do one topic area at a time.
Agree > I can't help but think some topics are subjective and fall into the > beauty (Groovy idiomatic) is in the eye of the beholder. > Okay, but the point here is "aesthetic over logic". The use of "var", as of today, falls "only" into the "beauty" category because there is no real need for it. We have it because we want Groovy to be familiar to Java developers? Okay, but why do we have to elevate it to something that is not? By that I mean "the new way of defining variables in Groovy"? Especially because "logically" `def` in Groovy stands for `Object` in any scenario we can use a type, while `var` only works in one scenario: variable definitions. `var` is redundant. `var` is unnecessary. `var` is a trick we think makes people happy, but this is an opinion, not a fact, it cannot be proven. > * var/def (for me it's the intended audience of viewers that lean me > in one direction or the other - if writing code/scripts for a Java > shop were Java developers are likely to be maintainers or a blog post > where numerous Java developers will read, I tend to favor var) > That's fine, but as you said, it is a subjective decision. I would like to use `var` as a return type placeholder meaning "this method returns a variable", so following your logic the Groovy community should be supporting my preference as well (I am a certified Java developer if that can help)
