Why we built a language instead of picking one

Every project starts the same way: pick a language, then assemble a stack around it: a web framework, a database driver, a WebSocket library, maybe an ML package. Before a single feature ships, a third of the budget is already gone to wiring dependencies together. We kept hitting that wall, so we asked a different question. What if the stack was the language? NIAO is our answer: a compiled, statically typed, memory-safe language with HTTP, databases, WebSockets and ML primitives in the standard library. The bet is that language-level unification, not another framework on top of an old language, is the next step after tools like Copilot proved developers want less friction, not more. NIAO's v1 compiler is active and benchmarks at 120k+ lines per second. This post walks through the design decisions that got us there.