This essay is telescopic. It can shrink or expand, depending on how much attention you are willing to give.
This is an AI-generated version (209 words, not yet human-reviewed). Show other sizes.
Multilingual Programming Infrastructure
-
Programming languages are not syntax variants. They are ontologies. Lisp, Prolog, APL, Erlang each carve the world at different joints.
-
For seventy years the stack was a funnel: many dialects at the surface, one von Neumann mind underneath. Worldviews evaporate at the first translation boundary.
-
Infrastructure becomes destiny. What is easy to build gets built, and a generation of capable engineers now cannot think declaratively — grammar you don't use, you lose.
-
LLMs should be the great multilingual moment. Instead they're the great homogenizer: every language accessible, one language inevitable. Not by decree, by gradient.
-
We built a translation layer without building a preservation layer. Water flows downhill, and the hill was shaped by GitHub.
-
Monoculture is spectacularly efficient right up until the blight arrives. Ask the Gros Michel banana. Ask the Irish potato.
-
What multilingual infrastructure needs: no flattening intermediate representation, visible seams that show what translation lost, rewarded round-trips, and deliberate cultivation of minority languages as a seed vault.
-
Infrastructure is where language stops being talk and becomes matter. We are quietly deciding which thoughts our grandchildren will find easy.
-
The machine isn't evil. It's just very good at going downhill. Our job is to keep some hills.
Original published: August 24, 2026