Java Is Still the Institution

Java is still the institution. Not because it is fashionable, and not because I write it daily. Because the JVM is where payroll, identity, and the API you actually have to call still live after three generations of “this will replace it.”

They announce the death on a timeline. The bytecode does not read timelines. HotSpot, classloaders, a decades-long ABI story, and a default procurement already knows how to buy: that is an institution. I meet it as JSON over HTTP and as the thing behind a SAML wall. I do not need to be a Java engineer to notice that the runtime is the product: write once, run on a machine the org already knows how to patch.¹

You can dislike the ceremony. Checked exceptions, XML ghosts, Spring’s gravity. Ceremony is how institutions remember. A rewrite in a prettier language does not erase the JVM if the data, the drivers, and the people who get paged still live there. Cursor will generate a client. The institution will still speak Java on the other side of the socket.

Dead is a fashion word. The JVM is a default. Treat it as infrastructure you may have to integrate with, not as a punchline.

— JV · Dark Heart Labs.

Tim Lindholm, Frank Yellin, Gilad Bracha, and Alex Buckley, The Java Virtual Machine Specification. The normative JVM — the institutional runtime this note is pointing at, not a language-war scoreboard. ↩