Somewhat mild take: Java actually isn't even that bad tbh.

It's getting considerably more hate than it deserves. Yeah, it has things that make it suck and it deserves some of the shit it gets, but so does every other language. It has its advantages and it has its disadvantages.

It got better than 10 or 15 years ago, but I still see it as a verbose, boilerplate language.

With Kotlin there is absolutely no point in using Java anymore. Unless you are an idiot.

I had to use Java some years ago to fix a bug in a Dungeon Siege 2 mod, it was fairly easy. The only two annoying bits were installing eclipse and finding the right version of SWT to build the project.

So it would seem to me the tooling itself is problematic -- the language itself is OK.

Kotlin is an extension of this: heavily dependant on terrible tools right down to the documentation, more or less the same as not fixing anything. But the language as such is fine.

@Liebranca Kotlin is indeed held down by the tools and more importantly by the JVM.
But it does fix some things compared to java. It fixes the null bullshit by having non-nullable types and smart casting for nullable types.
It also has a (somewhat convoluted) version of (algebraic) sum types.

@Lensflare Very hard to escape fabricated issues, by which I mean to say such bullshit is generally artificial; doesn't even need to exist.

In that context, I can hardly tell a lot of these languages apart: whatever they are trying to solve is absolutely distant from problems I have. And so I've settled for indifference, where one only defecates on language a fair amount relative to the severity of the inevitably suffered headache.