this post was submitted on 22 Nov 2023
39 points (86.8% liked)
Programming
17526 readers
292 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah it can be slightly hairy because Java does a terrible job with nullability. I've also done an incremental migration of an android codebase to Kotlin.
Personally I think being forced to declare the nullability of a field is something backend developers should do more of. It helps eliminate some of the foot guns that otherwise get built into the code base.
I'm a bit of a kotlin fanboy though, I'll admit.
I 100% agree that explicit nullity is categorically better, and the vast majority of the entire software engineering field does too. The problem lies in the fact that explicit nullity was added in 2014 with Java 8, nearly two decades after Java 1 shipped in 1996. That’s a hell of a lot of technical inertia to overcome.
Yeah especially whether Java "runs on 1 billion devices" 😂
The question is why a new codebase in greenfield is still using basic Java 11 on a new 2023 project.
lol do NOT get me started 😭