System.logger, JDK Enhancement Proposals (JEP) and knowing about Java's future

An airhacks.fm conversation with Nicolai Parlog (@nipafx) about:

previous episode with Nicolai: "#163 The Endless Loop of Frustration and Challenge" JEPs, JEPs draft, what happens on the openJDK Mailing list, spending time with JEPs, knowing about the future, influencing current architecture with future standards, the System.logger was added in JDK 1.9, System.logger was intended for internal JDK user, but works fine for applications as well, JEP 264: Platform Logging API and Service, hystrix deprecation, dozer mapper is deprecated, the Eclipse Maven plugin, the fast NetBeans, great Visual Studio Code, hamcrest vs. assertj, consistency vs. micro-optimizations, why try with resources came in Java 9 first, effectively final in Java 9, where to put the context information, How to comment with JavaDoc, the Java 18 snippet tag and src/demo/java, JEP 413: Code Snippets in Java API Documentation, the cases for package-info.java, JavaDoc and metrics, testing the mocks, pointless unit tests, combining cyclomatic complexity with test coverage, crap4j

Nicolai Parlog on twitter: @nipafx, Nicolai's website: nipafx.dev