Conversation

Mar 17, 2021

I wrote a little Java today. And for a C++ dev, of the more modern variety, those new’s were painful: Timer timer C++ brain: Ah that’s good. Timer timer = new Timer(); C++ brain: Oh no, baby, what did you do???

GIF

read image description

ALT

Replying to

You can now use auto^Wvar for this :)

Replying to

Doesn’t help with the new 😭

Replying to

and

It's hard to get used to the == and != operators checking object identity for non-primitive types. It's also quite annoying that Object provides an object identity implementation of equals to everything by default. Hard to express how much I dislike class inheritance in general.

Replying to

and

They forgot to provide a proper equals implementation for arrays early so, so for arrays, they ended up being locked into the equals method checking object identity. So, for most stuff including strings, you use equals to check equality, but arrays need java.util.Arrays.equals.

Replying to

and

The next problem is that java.util.Arrays.equals will call the equals method for each element in the array so of course that doesn't work properly for nested arrays due to the messed up equals implementation. So, you need java.util.Arrays.deepEquals to deal with that. Sigh.

5:52 PM · Mar 18, 2021Twitter Web App

Replying to

and

Oh wow 😳

Replying to

and

I don't mind Java that much but I really look forward to migrating all of our Java projects to Kotlin. It will also be nice being able to using the latest version of Kotlin even when targeting platforms with an older runtime. Can't do that with Java which is really annoying.