News for hackers. Stuff that matters.

A comment on Java 17 / JDK 17: General Availability. Parent comment

Re:Java 17 / JDK 17: General Availability by tathisit on Tuesday September 14, 2021 @12:17PM (#28527017)
Kotlin does it, but it's next to useless because the ecosystem makes heavy use of null.
[ Parent | on HN ]
Re:Java 17 / JDK 17: General Availability by Tainnor on Tuesday September 14, 2021 @12:55PM (#28527535)
what? I don't feel it's "pointless" at all. Many popular Java libraries and frameworks (including Spring) use nullability annotations which can be interpreted correctly by Kotlin. It's true that I can't be 100% sure not to get NPEs, but I think it's close enough and I've rarely seen NPEs in Kotlin codebases.
[ Parent | on HN ]
Re:Java 17 / JDK 17: General Availability by rickette on Tuesday September 14, 2021 @04:17PM (#28530480)
Indeed, Kotlin's null handling is great. NPE's in Kotlin code aren't common.
[ Parent | on HN ]
Re:Java 17 / JDK 17: General Availability by syncsynchalt on Tuesday September 14, 2021 @05:36PM (#28531694)
Kotlin is my suggestion too.

Kotlin (or any other JVM variant that does non-nullability in a seamless way) and coding guidelines should get you 90% of the way to a null-free world.

[ Parent | on HN ]