I don't understand the reasoning on this. 1. I would not consider using or not using java 8's lambda's a "programming comfort" the paradigms introduced with Java 8 such as lambda's and streams fundamentally change how the source is written and in my experience results in concise, easier to understand code.
2. What exactly is the disruption caused by building to Java 8? The free version of Java 7 has been deprecated for 3 years. Java 8 is deprecated. By the end of the year Java 9 will be deprecated. If someone is running a version of Sling on a vm that's been unsupported for 3 years, they shouldn't they be fine with not upgrading to the latest module we release? 3. It's hard to context switch. Things don't work the same, remembering which API's are there and aren't. That's the way mistakes are made. It would provide greater consistency in the code, both in the writing of it, and the support of it. If the baseline was updated. - Jason On Wed, Jul 4, 2018, at 6:03 AM, Bertrand Delacretaz wrote: > On Tue, Jul 3, 2018 at 9:25 PM Jason E Bailey <[email protected]> wrote: > > It's things like that, that make me a sad developer... > > Having to use Java 7, you mean? > > I think if you're slightly modifying an existing module (especially a > very core one like "engine") the benefits of switching to Java 8 are > not worth the (potential) disruption, especially if it's just for > "programming comfort". > > If switching to Java 8 brings tangible benefits, a brief explanation > with a [LAZY] vote is probably just what you need to make it happen. > > -Bertrand
