Also: everything is nullable. There are no safety guarantees to ensure you’ve done the necessary null checks. And if you miss your program will crash.

[–] [email protected] 5 points 7 months ago (1 children)

Oh yeah how did I forget the billion dollar mistake, definitely one of the worst misfeatures of Java

[–] [email protected] 3 points 7 months ago* (last edited 7 months ago) (1 children)

I think having null is great in some cases where you need to represent missing value. It’s just that there’s no good way to know for sure if you need to do null checks or not. The only way around it is to do null checks everywhere, which no one wants to do because fuck that. Nowadays there’s Optional which solves some of this, but it was introduced way too late.

If I were to redesign Java the first thing I would do is to add a nullable keyword or something.

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago) (1 children)

I think having null is great in some cases where you need to represent missing value.

Option types or sum types would probably be a much less terrible choice for this, although I guess some sort of nullable keyword counts as a sum type

[–] [email protected] 3 points 7 months ago* (last edited 7 months ago) (1 children)

Well, anything that can be captured at compile time or by the IDE is infinitely better than the situation we have today.

[–] [email protected] 0 points 7 months ago

Ha yeah, just about anything is better than the current status quo