Java

java.com is a download page, not a language page. It splits its audience between end users who need a runtime to open a desktop application and developers who want the JDK, calls Java “the #1 programming language and development platform”, says it “reduces costs, shortens development timeframes, drives innovation, and improves application services”, and names Oracle as “the stewards of Java” (Oracle as a cloud vendor lives in ../cloud-wiki). It links OpenJDK early-access builds. No version number, no adoption figure, and not one sentence about the language.

T1 — first-party, and the emptiest source in the corpus. Recorded that way on purpose.

What the emptiness shows

Every other home page here argues a design position: go removes choices, rust proves memory safety, haskell commits to purity, scheme states a rule about what not to add. Java’s public front door argues procurement — cost, timelines, enterprise fit — and routes anyone with a technical question elsewhere. That is what a language’s marketing looks like when the language no longer has to be sold to programmers, and it is the cleanest evidence yet for the caveat this spoke repeats: a front page tells you who the language is being sold to, not what it is.

The technical material exists at dev.java, the JDK documentation and the JEP process. None of it is here, so the corpus still has no source describing Java’s design or its evolution process, which is awkward given how much of the wiki depends on it.

The dependency the corpus already has on it

Java’s absence is load-bearing. clojure is hosted on the JVM, kotlin targets it with Java interop as its founding feature, jank exists because someone wanted Clojure’s semantics without Java interop, and rethinking-java-design-patterns rewrites the GoF catalog in functional Java. Four pages describe things relative to Java; none describes Java. See hosted-language — the host whose properties the guests keep inheriting is the one this wiki knows least about.

Growth edge, promoted to synthesis: the JEP process and a JDK release page would close both gaps at once — language-governance gains its best-documented corporate-plus-open-process case, and the JVM stops being an unexamined assumption.

Related

clojure · kotlin · jank · hosted-language · language-governance · rethinking-java-design-patterns · programming-language · synthesis