Why I'm Building a Programming Language
Every serious system I have built eventually hits the same three walls. The language is pleasant but falls over under real failure. Or it survives anything and is miserable to write. Or it is fast and makes you pay for every line in blood. INDU is my refusal to keep choosing. It is a universal language and framework built on three borrowed pillars: Python's ease, Erlang's fault tolerance, and C's speed.
Wall one: the first hour
Python's real feature was never dynamic typing. It is that the first hour with Python feels like thinking out loud. Most languages lose people before the first hour ends: install toolchains, fight the package manager, learn which build file is angry at you. Ease is not a beginner feature. Ease is what lets an expert move at the speed of the idea. INDU treats that as a hard requirement, not a nice-to-have.
Wall two: failure is the default
Erlang was built for telephone switches that were not allowed to stop. Its answer was radical: expect things to fail, isolate them, supervise them, restart them, and let the system heal itself while it keeps running. My multi-agent work taught me the same lesson the hard way. Agents crash, tools time out, networks lie. A system of small processes that expect failure beats one big process that hopes for success. That philosophy belongs in the language itself, not in a framework you bolt on after the first outage.
Wall three: the hot path does not negotiate
C is still the honest answer to performance. No runtime surprises, no garbage-collection roulette in the middle of a hot loop. When the bottleneck shows up, and it always shows up, the language has to get out of the way. Ease and fault tolerance cannot become excuses for being slow where it counts.
Why write a language at all
Because every hour spent fighting your tools is an hour not spent on the problem. And because building a language is the best education in programming that exists: you stop blaming your tools, because the tools are yours now. The excuses become yours too.
INDU sits in the Foundation row of my project wall, which is where it belongs. It is a long game, built in public, one decision at a time. This journal will document the whole thing.