Why low-latency Java still requires discipline?

I found claude and GPT very helpful on this, because java have a very sofisticated monitoring harness. Just ask the agent to connect to the running application (on kubernetes or whatever) on prod and do a java flight recording then analyze allocations.

I managed to improve some applications of ours from several garbage collections per second to several minutes between collections. That _really_ improve p99.

I get that blog posts often advertise a company's products, but this one had absolutely zero content other than advertising.

Even C requires discipline to write low latency code, if you think otherwise, you never used a profiler.

page doesn't load "En attente de la réponse de chronicle.software."

How about not using Java? Then you can have low latency.

Average go, rust, c++ and c will outperform amazing java programs, and the former will also be way way more easy to run, troubleshoot, interpret logs from.

Java is usch garbage in every stack.