113

Let's reinvent java bytecode but... different

you are viewing a single comment's thread
view the rest of the comments
[-] magic_lobster_party@kbin.run 3 points 7 months ago* (last edited 7 months ago)

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.

[-] hydroptic@sopuli.xyz 2 points 7 months ago* (last edited 7 months ago)

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

[-] magic_lobster_party@kbin.run 3 points 7 months ago* (last edited 7 months ago)

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

[-] hydroptic@sopuli.xyz 0 points 7 months ago

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

this post was submitted on 05 Apr 2024
113 points (73.3% liked)

Programmer Humor

19544 readers
624 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS