4 ms·
FWIW, it is not difficult to set up NullAway: https://github.com/uber/NullAway https://github.com/uber/NullAway
by jdm2212 3y ago
FWIW, it is not difficult to set up NullAway: https://github.com/uber/NullAway https://github.com/uber/NullAway
- lolinder 3y agoIt's also not nearly the same as having null checks be a first-class part of the language.
- jdm2212 3y agoYes, it does offend the language hipster instinct in me too to have to add 8 lines of gradle to a turn on a build plugin.
- ohgodplsno 3y agoAnd then have to deal with the fact that the libraries you consume don't use NullAway either.
- jdm2212 3y agoIf you import Java libraries into Kotlin, you can still get NPEs from the libraries. And if you don't import Java libraries into Kotlin, well... you could just write Java without those Java dependencies, too.
- jeroenhd 3y agoJava has tons of nice additions (Lombok, NullAway, Manifold) but that's not part of the language itself. When you bind yourself to libraries like these, you're stuck waiting for them to update whenever a new Java release comes out. That can take months or years, and sometimes a library just stops getting updated at all. If Java were to include NulLAway in their standard language, which they clearly can do if they wanted to, I would consider it to have feature parity with other modern languages.