On Fri, Jan 7, 2022 at 12:19 PM Christoph Läu
As I said if there is any compelling reason e.g. our dependencies
require j17 I'm totally fine and won't argue to keep at all cost at j11,
but at the moment there is no need and no benefit (beside using some new
language features).
That's a fair analysis and we agree on the big lines.
I think we can agree that using new Java version => using new language features <=> writing better code faster => bring more functional value (stability, performance, features) => Happier users; Using new Java version => Happier users.
Where our opinion differs is on the "factor of impact" of such change. My personal experiences in my ecosystem give me the impression that although it doesn't seem huge before actually doing the change, it always reveals much more profitable than expected after; and telling people who want to stick to older versions of Java that they should also stick to older version of ${whatever} is actually bringing a positive result on both users as many do the switch to get newer/better ${whatever} and end up happier with it and start using newer Java for everything.
