Conversation

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???
Whatever Judgingyou GIF
GIF
11
70
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.
2
2
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.
1
1
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.
1