The Untold Story of TypeScript | The Language That Fixed JavaScript

[00:00:00]JavaScript had conquered the web by 2010. It was the undisputed language of the interactive internet running on billions of devices across the planet.

[00:00:11]It was the only language that browsers could execute natively. A fact that made it indispensable. Yet the very qualities that made JavaScript so accessible, its flexibility and its forgiving nature were becoming a liability. The language had been designed in 10 days in 1995 to add small interactive behaviors to static web pages. It was never built to support sprawling millionline applications that would power global commerce, social networks, and cloud infrastructure. As applications grew larger, the cracks in the foundation became harder to ignore. A variable could hold a string in one function [music] and an array in another, and the interpreter would accept both without complaint. The code would run, but the behavior would often be unpredictable.

[00:01:02][music] Engineers would make a change to one part of a program, believing they understood its structure, only to discover that a distant, unrelated function had broken. Debugging these failures was time-conuming, expensive, and demoralizing. The industry had reached a contradiction. Its most critical infrastructure was built on a language that could not safely support the scale it had achieved. Inside the Microsoft campus in Redmond, Washington, a small team of engineers began working on a solution. The project was cenamed Strada and its architects were among the most respected language designers in the world. Anders Hellsburg, the Danish engineer who had created Turbo, Pascal, and Deli before leading the development of Microsoft C, understood the demands of large-scale systems better than almost anyone. Alongside him was Steve Lucco, a [music] technical fellow who had managed the Chakra JavaScript engine for Internet Explorer. They shared a conviction that the JavaScript language could be preserved while adding a layer of control that would make it suitable for enterprise applications.

[00:02:11]Their proposal was [music] audacious.

[00:02:13]They would create a new language that was a superset of JavaScript, [music] meaning every valid JavaScript program would also be valid in their new system.

[00:02:23]They would add optional static typing, allowing engineers to declare what kind of data a variable should hold, and a compiler would check those declarations for consistency before the code ever ran. The compiler would then erase the type information and output plain standard JavaScript. The browser would never see the types. It would execute the same JavaScript it had always executed, but the code would have been examined for errors in advance. This approach offered a powerful advantage.

[00:02:53]Engineers could adopt the new language incrementally. They could start with a single file, add type annotations, and let the compiler check their work. The rest of the project could remain plain JavaScript. [music] There was no requirement to rewrite everything at once. There was no new runtime to install or new virtual machine to support. The output was standard JavaScript that ran in any browser, any version of Internet Explorer, any version of Chrome, any version of Firefox, [music] and any version of NodeJS on the server. This backward compatibility was not a secondary consideration. It was the central design principle. If the new language required developers to abandon their existing [music] code or change their deployment infrastructure, it would fail immediately. The political environment inside Microsoft made this project even more difficult than the technical challenges. In 2010, Microsoft was still led by Steve Balmer, [music] who had famously described Linux as a cancer. The company viewed open-source as a threat to its intellectual property and its dominant business model.

[00:04:05]Hellsburg and Luco knew that their project had to be open-source to succeed. The JavaScript community would never trust a proprietary language from Microsoft regardless of its technical merits. Pitching an open-source project to Balmer's Microsoft was a delicate negotiation. The team had to demonstrate that the [music] strategic benefits of aligning with the open-source ecosystem outweighed the risks of giving away control.

[00:04:31]The project proceeded quietly without public announcements until the team had built enough momentum to protect it from internal opposition. The first public preview of Typescript version 0.8 8 arrived in October of 2012. Hosted on Microsoft's CodePlex platform, the initial reception was cautious. Many developers assumed this was another Microsoft attempt to embrace a standard and then extend it in proprietary directions. The company had a long history of such strategies and the JavaScript community was wary. Hellsburg [music] and his team continued to develop the language, releasing version 0.9 and then version 1.0 at Microsoft's build conference in April of 2014.

[00:05:20]The tools were improving, but adoption remained limited. Microsoft's [music] reputation was a persistent obstacle.

[00:05:28]The moment that changed everything occurred in March of 2015.

[00:05:34]Google announced that its Angular web framework would adopt TypeScript as its primary language for the upcoming Angular 2 release. This was not [music] a simple endorsement. Google had been developing its own language for Angular, a project called Atcript, which was designed to add type information and annotation capabilities to JavaScript.

[00:05:55][music] The teams at Microsoft and Google recognized that they were trying to solve the same problem in different ways. Rather than compete, they collaborated. [music] Google's atcript was merged into the TypeScript design and the TypeScript compiler was enhanced to support the metadata and decorators that Angular required. The decision to converge on TypeScript was a pragmatic compromise.

[00:06:20]Both companies wanted a reliable way to build large applications and Typescript was the best existing foundation.

[00:06:28]Google's adoption sent a powerful signal to the developer community. [music] If Google was willing to trust a Microsoft language for its flagship framework, then the technology was worth taking seriously. [music] The Angular 2 release in September of 2016 was a turning point. [music] Large organizations that had been waiting to see which direction the industry would move now had their answer. Slack began migrating its desktop application, a massive JavaScript code base with hundreds of thousands of lines. The migration took 6 months and [music] the TypeScript compiler caught numerous potential bugs that would have otherwise appeared in production.

[00:07:09]engineers [music] discovered that they could refactor with confidence, reworking large sections of the code without [music] fearing hidden dependencies. Airbnb also adopted TypeScript, but the sheer size of its codebase made the migration difficult.

[00:07:24][music] The company developed an internal tool called TS Migrate that automated much of the conversion process, [music] adding type annotations and fixing common issues. This tool was later released as open-source, demonstrating that even a successful migration required substantial investment. [music] GitHub's Octoverse report for August of 2025 recorded that Typescript had become the most used language on the platform by monthly contributor count. It had overtaken both Python and JavaScript with approximately 2.6 million contributors and growth of more than 1 million contributors over the previous year. This statistic did not mean that Typescript had become the most popular language for all programming tasks. It meant that in the open-source ecosystem, more developers were contributing to TypeScript projects than to any other language. The language had become a default for web development. The standard syntax for modern front-end frameworks [music] and a growing share of back-end services. The financial value of Typescript is indirect but substantial.

[00:08:32]Microsoft does not sell the language. It is free open-source software licensed under the Apache license 2.0. [music] The strategic benefit for Microsoft lies in developer relationships. Engineers who use TypeScript and Visual Studio Code, Microsoft's open-source code editor, develop habits and preferences that align with Microsoft's cloud platform, [music] Azure. This alignment does not guarantee that developers will choose Azure, but it makes Microsoft a more natural partner for their infrastructure needs.

[00:09:05]The company's cloud division has become its primary growth engine, reporting over $70 billion in total revenue for the third quarter of fiscal year 2025 with Microsoft Cloud generating $42.4 billion.

[00:09:21]Typescript is one piece of this ecosystem, a gateway language that connects millions of developers to Microsoft's broader portfolio of tools and services. The controversy surrounding Typescript is not about its technical merits in the abstract, but about the limitations of its approach.

[00:09:40]The type system is not sound. Developers can explicitly override the compiler's checks using the any type which disables type checking for a particular variable.

[00:09:52]They can also use type assertions to tell the compiler that a value has a specific type even when the compiler cannot verify that assertion. These escape hatches are necessary for practical use, but they mean that the compiler's guarantees are conditional.

[00:10:07]The language can also be slow on very large projects with complex conditional types and heavy reliance on third-party declaration files contributing to build times. Configuration options are extensive [music] and teams often struggle to find the right settings for their projects.

[00:10:24]Critics argue that TypeScript introduces complexity that can outweigh its benefits for smaller applications where plain JavaScript remains more productive. This is not a debate about whether types are always good or always bad. It is a debate about the appropriate use of a tool that is extremely powerful for some contexts [music] and unnecessarily heavy for others. One unusual incident illustrated how Typescript's technical decisions can have legal consequences.

[00:10:54]In early 2026, Anthropic accidentally exposed the TypeScript source code [music] of its Clawude Code product by including a source map file in a public npm package. Source maps are generated files that map compiled JavaScript back to the original TypeScript source, allowing developers to debug their applications using the original code.

[00:11:17]When Anthropic's package was published, the source map revealed more than 500,000 lines of TypeScript. The code was quickly copied to other repositories.

[00:11:28]Anthropic attempted to use the Digital Millennium Copyright Act to demand takedowns, but the legal status of copied source code that had been accidentally published was uncertain.

[00:11:39]The incident highlighted a recurring tension in the open-source ecosystem.

[00:11:44]Code that is not intended to be public can become public through configuration errors and once public it can be redistributed widely. The most important technical development in Typescript's history occurred in July of 2026 with the official release of version 7.0.

[00:12:03]The TypeScript compiler had been rewritten in the Go programming language, replacing the original implementation that was written in TypeScript itself and compiled to JavaScript. The decision to rewrite the compiler was driven by scale. [music] The original compiler was designed for code bases of hundreds of thousands of lines, but as TypeScript became the industry standard, projects routinely exceeded millions of lines. The compiler was slow and slowness was becoming a barrier to adoption for the largest organizations. The Go implementation uses native execution, parallelism, and shared memory to achieve roughly 10-fold performance improvements in many workloads. The architecture had reversed. Typescript began as a language that accepted JavaScript's [music] disorder and placed a system of checks around it. Over time, it became so widely used that its own infrastructure could no longer meet the scale it had helped create. [music] Microsoft rebuilt that infrastructure not by extending the original design, but by abandoning the self-hosting principle and adopting a different language, different runtime, and different concurrency model. The comparison with other languages clarifies [music] Typescript's distinctive strategy. JavaScript is its closest relative and the two are essentially the same language at runtime. [music] JavaScript offers the same execution environment without the type checker and for small or short-lived projects, it remains the simpler choice. Dart developed by [music] Google is also a statically typed language that compiles to JavaScript. But Dart was designed as a complete replacement with its own virtual machine and a focus on performance for mobile applications.

[00:13:49]Dart's early strategy included ambitions for direct browser support, but its modern success is [music] concentrated around Flutter and cross-platform application development. Typescript did not attempt to replace JavaScript.

[00:14:02][music] It entered the existing JavaScript world without asking developers to abandon their packages, their browsers, their syntax [music] or their runtime. It accepted the ecosystem as it was and added a layer of verification. The gradual integration of Typescript [music] into existing code bases proved essential to its success.

[00:14:24]Organizations did not need to commit to a complete rewrite. [music] They could adopt the language file by file, gaining confidence as the compiler identified issues they had not known existed. Over time, the type annotations became a form of documentation, explaining the intended structure of the program to new engineers who joined the team. The compiler also powered advanced editing features in Visual Studio Code and other editors, providing autocompletion, navigation, and safe refactoring. These features changed the development experience itself, making it easier to work with large code bases and reducing the cognitive load on engineers. The language's role in artificial intelligence has further increased its value. AI coding assistants can use type information to make more accurate predictions about the code they generate. The types [music] serve as constraints, reducing the probability that the assistant will produce nonsensical or incorrect output. As AI becomes more integrated into software development, [music] languages with rich type systems will likely become even more important. Typescript is well positioned for this trend with a type [music] system that is expressive enough to describe complex relationships in JavaScript programs. Typescript [music] succeeded because it refused to destroy what already worked. It accepted JavaScript's disorder, its historical compromises, and its limitations. It placed a system of checks around that disorder, making it manageable without demanding that the world change overnight. The language grew from a quiet project inside a company that distrusted open-source into the foundation of modern web development.

[00:16:08]Its final architectural reversal, the rewrite in Go, was not a rejection of its origins, but a recognition of its own success. The tool that had been created to discipline large JavaScript applications had become [music] so indispensable that its own architecture required replacement. Typescript is the layer through which much of the industry now understands JavaScript code. A testament to the power of incremental backward compatible change in a world that rarely grants such patience to its tools.