On January 13, 2000, the loudest man in software became its most powerful. Steve Ballmer — Bill Gates's Harvard classmate, hired in 1980 as Microsoft's first business manager and famously employee number 30 — took over as chief executive. Gates slid sideways into a new title, "chief software architect," but the message was unmistakable: the founder was handing the wheel to the salesman. And the salesman had a voice you could hear through a closed door.
Ballmer inherited a company at the peak of its power and the depth of its danger. The antitrust trial was still smoldering. The web was rewriting the rules. And Windows itself was quietly split down the middle — a schism that Ballmer's first great product would finally heal.
Two Windows, One Kernel
For most of the 1990s, Microsoft shipped two different operating systems that happened to share a name. There was the consumer line — Windows 95, 98, and the unloved Millennium Edition — still rooted in MS-DOS, friendly to games and hardware but prone to freezing at the worst possible moment. And there was the business line, Windows NT and Windows 2000, built on a robust modern kernel that almost never crashed but shrugged at consumer software and games.
The dream, chased for years under codenames like Neptune and eventually Whistler, was to fuse them: give ordinary users the rock-solid NT foundation without losing the compatibility they relied on. That dream shipped on October 25, 2001, as Windows XP. Under its cheerful green "Luna" skin and that iconic rolling-hills desktop was, for the first time, a single codebase on the NT kernel serving home and office alike. It was Microsoft's most stable, most popular desktop release ever — so beloved that customers clung to it for well over a decade, long past the point Microsoft wanted them to let go.
The Bet Beyond Windows
Stabilizing the desktop was the defensive play. The offensive one was .NET — a sprawling initiative Microsoft began unveiling in mid-2000 to answer a frightening question: what happens to a company built on the Windows PC if the future belongs to the web and to servers?
At its heart .NET was a new way to build software. The Common Language Runtime executed "managed code," handling memory and security so developers didn't have to. A vast Framework Class Library gave them ready-made building blocks. And crucially, many languages could target the same runtime — including a brand-new one, C#, designed by Anders Hejlsberg, the engineer who had earlier created Turbo Pascal and Delphi. The .NET Framework 1.0 arrived in early 2002, bundled soon after into Windows itself. It became the backbone for a generation of Windows and enterprise applications.
Developers, Developers, Developers
To understand Ballmer's Microsoft, you have to understand one sweat-soaked moment. At a company event, a red-faced Ballmer stormed the stage and bellowed the word "developers" over and over — four, then more times — pumping his fists until the crowd roared. The clip became an internet legend, endlessly mocked. But strip away the theater and it was a genuine strategy, distilled to a single word.
Microsoft never won because its products were always the best. It won because it made itself the most rewarding place to build. Every developer who learned Visual Basic, shipped an app on Windows, or bet a career on C# was another root binding customers to the platform. XP gave those developers a stable target for their desktop software; .NET gave them a modern toolkit and a reason to stay. Ballmer's chant wasn't a punchline — it was the whole flywheel, said out loud.
It was also a bet with a blind spot. In fixing the desktop and courting the coders who lived on it, Microsoft was doubling down on the PC just as the ground began to shift beneath it. The stability of XP and the reach of .NET would carry the company for years — but a small, glowing rectangle was about to appear in a rival's hand.
Next time: the internet grows up, and Microsoft discovers that winning the browser war was not the same as winning the web.
Comments
Post a Comment