this post was submitted on 22 Nov 2023
28 points (85.0% liked)

Programming

17319 readers
150 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 !webdev@programming.dev



founded 1 year ago
MODERATORS
 

In this article, we’ll debunk the notion that Java is a relic of the past and showcase the language’s modern features, thriving ecosystem, and unwavering presence in enterprise and open-source communities.

you are viewing a single comment's thread
view the rest of the comments
[–] gravitas_deficiency@sh.itjust.works 1 points 11 months ago (1 children)

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.

[–] huginn@feddit.it 1 points 11 months ago (1 children)

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 😭