[belfthrow]

I really hate how completely clueless people on hn are about java. This is not, and has not been an issue for many many years in Java and even the most junior of developers know how to avoid it. But oh no, go and rust is alwaayssss the solution sure.

[pythonaut_16]

Can you provide any examples or evidence of Java apps that prove this?

Because in my experience as of 2026, Java programs are consistently among the most painful or unpleasant to interact with.

[dionian]

IntelliJ IDEA is reasonably fast, but of course its hard to make a big desktop app in java be fast.

[belfthrow]

Crac / aot cache / ready now all can address this. Not even considering native aot. Multiple low latency trading systems across market markers, hedge funds and ibs prove this. But people just want to compare it to building a cli tool in go or rust.

[pythonaut_16]

But like can you provide an actual example of an application?

> But people just want to compare it to building a cli tool in go or rust.

This seems like the key. HN is definitely biased towards simpler, smaller tools. (And that's not a bad thing!). The most compelling JVM stories I hear are all from much larger scale enterprise settings.

Kafka being a good example. It's very good at what it does, but painful to manage and usually not worth the pain for anyone who's not in a mega enterprise.

[belfthrow]

Because in real life, real world applications software is large, long running and needs to be bulletproof. Clis are not powering the world's infrastructure via piped bash scripts. It really baffles me what people actually do as software engineers on here with some of the nonsense that gets thrown around.

[bombcar]

Ah, but let's port rust to the JVM!