Why type script 7.0 was rewritten in go — and what it means for your dev stack | spf13
Search for Blog
Why TypeScript 7.0 Was Rewritten in Go — And What It Means for Your Dev Stack<br>Steve Francia<br>6 Jul 2026
Go<br>AI<br>Agentic-Development<br>Typescript<br>Systems-Language
Over the last year, the team that invented TypeScript ported the TypeScript compiler and tools to Go. Not Rust. Not C++. Go. Microsoft’s numbers show build times improving by roughly an order of magnitude in the Go-based TypeScript 7.0.<br>In the age of AI-assisted development, one of the largest JavaScript/TypeScript organizations on earth chose Go for its flagship tool.<br>That shouldn’t be surprising. Go was built on a bet: optimize for the reader, not the writer, in exchange for less code to misread. LLMs read code more than any human ever could, and as they write a growing share of it, humans become even more reader-heavy. Agentic development is the most extreme test yet of the goal Go was built for: readability, maintainability, long-term correctness at scale.<br>What about Python and TypeScript?<br>The conventional argument for Python and TypeScript in the AI era is strong on the surface. Python has PyTorch, LangChain, and the ML ecosystem. TypeScript has the web and a vast developer pool. LLMs trained on mountains of both write them fluently, confidently, and fast.<br>Python and JavaScript were designed as scripting languages: fast to write, forgiving, dynamic. TypeScript adds structure on top, but it’s a compile-time overlay: types are erased at runtime, so none of TypeScript’s guarantees survive execution. TypeScript hasn’t displaced JavaScript so much as grown alongside it: GitHub’s 2025 Octoverse report has TypeScript overtaking Python and JavaScript by monthly contributors, but JavaScript still generated nearly double the new repositories over the same 12 months, and GitHub’s own summary is blunt: “JavaScript is still massive,” and the combined “JavaScript/TypeScript ecosystem still accounts for more overall activity than Python alone.” Agentic systems aren’t scripts, though; they’re services, pipelines, CLIs, and distributed systems running in production for years, and all three languages fight that design at every step: complexity management, dependency isolation, deployment, runtime safety.<br>Go was designed as a systems language for large, long-lived software, and the industry is converging on exactly that category: compiled, safe, built to run for years, not scripted for an afternoon. The most exciting thing happening in TypeScript right now is its port to Go. The most exciting things happening in the Python world are mostly happening in Rust: Pydantic’s validation core is Rust, Polars is Rust, HuggingFace tokenizers is Rust, and Astral’s uv is Rust too.<br>Go’s share of that shift looks different but is just as telling: it’s the default choice for the infrastructure the current wave of agentic tools is built on. Ollama, the standard way to run local models, is Go. Weaviate, the vector database behind countless RAG and agent-memory stacks, is Go. Temporal, the durable-execution engine teams use to orchestrate long-running agent workflows, is Go. Charm’s Crush, a beautiful AI coding agent CLI in the same category as Google’s Antigravity, is Go too. Even GitHub’s own MCP server, the reference implementation for connecting AI agents to GitHub, is Go.<br>In a development loop, the question isn’t “which language is easiest to write?” It’s “which is easiest to write, review, and ship?” Agentic development multiplies that question. A machine now asks it hundreds of times a day.<br>The Agentic Loop Multiplies Every Weakness<br>An agentic coding loop looks like this: implement → build → test → analyze failure → self-correct → repeat. A human developer runs this loop maybe a dozen times per hour; an autonomous agent runs it dozens of times per task: what Anthropic’s guidance on coding agents describes as systems that “iterate on solutions using test results as feedback.” That frequency changes the economics of language choice.<br>Wes McKinney named this shift in his essay on agent ergonomics: once an agent is doing the coding, fast compile-test loops, frictionless distribution, and deterministic builds matter more than whether a language is pleasant for humans to type. He didn’t just write about it. Roborev, his continuous background code-review tool for AI coding agents, is built in Go.<br>Go solves four compounding problems that most engineers don’t notice, because they’re so used to the friction they no longer see it. Each one is paid for in the same currency: developer time and focus, agent iterations, and API dollars spent correcting what the language let through. Let’s walk through these problems in turn:<br>Build time<br>A several-minute build is routine for large Rust or C++...