Hi Ismael, +1 from me.
Looking at the list of languages features for JDK17, from a developer productivity standpoint, the biggest wins are probably pattern matching and java.util.HexFormat. Also, Java 11 is getting long in the tooth, even though we never adopted it. It was released 6 years ago, and according to wikipedia, Temurin and Red Hat will stop shipping updates for JDK11 sometime next year. (This is from https://en.wikipedia.org/wiki/Java_version_history .) It feels quite bad to "upgrade" to a 6 year old version of Java that is soon to go out of support anyway. (Although a few Java distributions will support JDK11 for longer, such as Amazon Corretto.) One thing that would be nice to add to the KIP is the mechanism that we will use to ensure that the clients module stays compatible with JDK11. Perhaps a nightly build of just that module with JDK11 would be a good idea? I'm not sure what the easiest way to build just one module is -- hopefully we don't have to go through maven or something. best, Colin On Fri, Dec 22, 2023, at 10:39, Ismael Juma wrote: > Hi all, > > I was watching the Java Highlights of 2023 from Nicolai Parlog[1] and it > became clear that many projects are moving to Java 17 for its developer > productivity improvements. It occurred to me that there is also an > opportunity for the Apache Kafka project and I wrote a quick KIP with the > proposal. Please take a look and let me know what you think: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=284789510 > > P.S. I am aware that we're past the KIP freeze for Apache Kafka 3.7, but > the proposed change would only change documentation and it's strictly > better to share this information in 3.7 than 3.8 (if we decide to do it). > > [1] https://youtu.be/NxpHg_GzpnY?si=wA57g9kAhYulrlUO&t=411
