Interview with Heinz Kabutz
summary
Argues that returning null instead of empty collections is deliberately useful, calls java.util.Optional “a waste” and insists simple null checks make code clearer; criticizes checked exceptions and notes IOExceptions have roughly ~87 subclasses and motivated the creation of UncheckedIOException. Explains Java 9 module patching now needs a three-step patch compile/compile‑against/run process (versus the old -Xbootclasspath trick) and reminds that class loading must allow multiple classes with the same package/name so application servers can load alternate implementations.
AI-written summary · about
related talks
48mDo You Use the Optional Class as It Should Be
56mJava Sucks (So C# Didn't Have To)
50mModern Java Puzzlers
01h 05mJava 8: The Good, the Bad and the Ugly
57mDo You Use the Optional Class as it Should Be
45mWhat a Java Developer Can Learn from Haskell?
44mThe long good-bye to NPE
46mStreams in JDK 8: The Good, the Bad, and the Ugly