TypeScript's Journey: From JavaScript Fix to Go

Remember when a 56K modem felt revolutionary? Anders Hejlsberg does, and he’s been revolutionizing the developer experience since Turbo Pascal was the hot new thing on the block.

Anders Hejlsberg, the mind behind C# and TypeScript, sat down with GitHub to chat about his 40-year career, and if you listen closely, you can hear the hum of 8-bit nostalgia in the background. Hejlsberg's journey from Turbo Pascal to TypeScript isn't just a timeline of programming languages; it's a testament to the iterative nature of technology itself.

Turbo Pascal: Fast Times in the 80s

Turbo Pascal was the 80s equivalent of a rockstar in the developer world. Hejlsberg revolutionized the coding experience by cutting down compile times so significantly that developers almost had time for a second cup of coffee before the code was ready to run. It was about speed, affordability, and democratizing the coding process—charging $49.95 instead of a fortune was a punk rock move that paid off.

"With Turbo Pascal, you say run, it immediately compiles into memory," Hejlsberg recalls. It was a game-changer, much like shoulder pads and neon leg warmers.

JavaScript: The Neverending Story

Fast forward to the days when we all started to realize that JavaScript, much like a mullet, was a bit of a fashion statement that had overstayed its welcome. The language was everywhere, but it was about as easy to manage as a Tamagotchi. Enter TypeScript, Hejlsberg’s solution to make JavaScript less of a nightmare and more of a pleasant dream.

"Is JavaScript really that broken?" Anders pondered. Spoiler alert: yes, but TypeScript aimed to fix it by being a strict superset. This wasn’t about building a new language; it was about patching up the old one, like adding a sleek spoiler to a beat-up sedan.

Going Open Source: The Microsoft Awakening

When TypeScript launched, Microsoft wasn’t exactly the poster child for open source. It was more like the kid reluctantly invited to the party. Initially released on CodePlex (Microsoft’s less popular alternative to GitHub), TypeScript didn’t catch fire until it moved to GitHub in 2014. "Our trustworthiness... in open source at that time was not particularly high," Hejlsberg admits, which might be the understatement of the decade.

Why Go? Because Go Fast

And now, TypeScript is getting a makeover with a move to Go for a 10x performance boost. Why not Rust, you ask? Well, because when you want speed, sometimes you need to go back to basics. JavaScript, for all its charm, is like trying to run a marathon in flip-flops. Moving to Go promises to unleash the potential that’s been sitting idle, like that dusty Atari in your attic.

"We knew we were leaving money on the table left and right," says Hejlsberg. Porting the compiler to Go is about finally cashing in on that potential.

As we look at the shifting landscape of programming languages, Hejlsberg's journey teaches us that evolution in tech, much like a good mixtape, is about knowing what to keep, what to remix, and when it’s time to upgrade the player altogether.

—Mike Sullivan