Sure, and Kotlin is largely syntax sugar for Java. It's certainly nicer, but the semantics are largely the same.

I attribute Java's uptake to a large amount of marketing and support, which led to a massive ecosystem. Even a mediocre language like this one can find success when propped up like that.

Open jdk is where it's at

I attribute Java's uptake to a large amount of marketing and support, which led to a massive ecosystem. Even a mediocre language like this one can find success when propped up like that.

You can annotate types in Python, and it's actually pretty nice when used with Pyright/Pylance.

C++ is a monster. I'd suggest C instead to learn about these basic ideas.

But nobody else does, and I need it more on code I am consuming than producing. In fact, many functions rely on being able to send various types for different behavior. Dynamic programming is crazy to me. It's like guessing. I don't know what type your code is accepting and I have to guess based on the name of read your code directly.

I would argue that without consistent and enforced type hinting, dynamically typed languages offer very little benefit from type-checking at runtime. And with consistent, enforced type hinting, they might as well be considered actual statically typed languages.

Don't get me wrong, that's a good thing. Properly configured Python development environments basically give you both, even if I'm not a fan of the syntax.

You must not write much Kotlin then? It’s far more than sugar when a language fixes core issues in another.

It’s a modern, statically typed language that addresses many of Java’s longstanding limitations with robust type safety, expressive functional features, coroutine-based concurrency, and extensibility — all integrated natively. Interoperability with Java is a strength, not a sign of dependency.

Calling Kotlin merely syntactic sugar is like saying Swift is just Objective-C with prettier syntax — it misses the deep improvements in language design, safety, and developer experience.

For me it's the tooling surrounding it that makes it nice.

Python is easy, but it can also be infuriating. Every time I use it, I'm reminded how much I loathe the use of whitespace to define blocks, and I really miss the straightforward type annotations of strong, non-dynamically typed languages.

I used Java years ago for Android dev, but stopped when I stopped doing that. Every once in a while I'll get the itch to work on a new project, and always wonder if Java would be a good idea.

My hesitance is that I don't trust Oracle (and don't know to what extent they're involved nowadays), I'm not familiar enough with the ecosystem to know what is legacy crap to avoid, and I think it's generally seen as an uncool language, and I'm way too cool to be taking such risks.

Kotlin is now the language of choice for Android.

I'm still wondering what Java's niche is, it seems like it does everything, but nothing particularly well. I guess it found a home on Android, but I don't think that's because it's particularly well-suited for it.

Java was the new hotness when I was in the middle of my comp sci degree. The biggest benefit I found was javadocs. Other languages had shit documentation that usually didn’t match reality in comparison.

Java is nothing like Rust. Java was always sold as a low skill programmer language, Rust has a steep learning curve. Java tooling has always sucked where Rust has excellent tooling pretty much since 1.0, Java is extremely verbose and needs a lot of tools to generate code to be productive at all, Rust is very expressive and most people write the code by hand or just use built-in language features. Java has a culture of "who care about that backtrace in my log as long as the app does what it is supposed to" while Rust has a culture that very much cares about correctness more than performance. Java was always driven by CEOs pushing it on people from the top while Rust is very much a language programmers try to push into their companies from the bottom.

Also, none of the languages you listed have a very particular niche that differs from what they were used early on apart from Java which is now mostly used on the server and used to also be used in GUI applications more.

And Java is very much considered legacy in the vast majority of projects that use it.

There's always Kotlin. Of course I never understood the desirability of a VM language in the first place, why not just compile for different architecture?