Skip to main content

The Rise of Microsoft, Part 6: Windows

Windows

🎬 Prefer to watch? Here's the 60-second version:

Watch on YouTube ▶

💻 The Rise of Microsoft — a 20-part series. See all parts »  |  « Part 5: The Empire of DOS

In the fall of 1982, Bill Gates walked the floor of COMDEX in Las Vegas and stopped at a booth run by a company called VisiCorp. On the screen was something called Visi On — a graphical interface for the IBM PC, with a mouse, on-screen menus, and multiple programs sharing the same display. It was clumsy and slow, but Gates saw past that. The command line that had made Microsoft rich, the blinking C:\ prompt, suddenly looked like the past. The future was a screen full of pictures, and Microsoft did not own a single pixel of it.

That moment set off one of the longest, most public, and most stubborn bets in the company's history. Microsoft would spend three years, burn through a team lead, miss deadline after deadline, and earn open ridicule from the trade press — all to ship a product almost nobody wanted at first. The bet was Windows.

The announcement before the product

On November 10, 1983, Gates called a press conference in New York and announced Microsoft Windows: a graphical environment that would run on top of MS-DOS, add a mouse and on-screen menus, and — crucially — let outside developers write programs for it. Microsoft promised it would ship by April 1984. Hardware makers including Compaq, Zenith, and DEC lined up to support it; software houses like Lotus and Ashton-Tate signed on too. Notably absent from the stage was IBM, which rejected Windows and went off to build its own interface, TopView.

The announcement was, in a sense, the whole strategy. Microsoft did not yet have a finished product — it barely had a working one. What it had was a year earlier, in 1981, the company had shown it wanted a graphical interface, and now it wanted to plant a flag before Apple, VisiCorp, and Digital Research's GEM could define the standard. Gates had recruited Scott McGregor, one of the engineers behind Xerox PARC's original windowing system, to lead development in August 1983. But announcing a product is easier than building one.

Three years in the desert

April 1984 came and went with no Windows. Microsoft slid the date to May, then quietly stopped naming dates at all. The delays became a running joke; the trade press slapped Windows with the label "vaporware," software that existed in press releases and demos but never on a store shelf. Internally the project was a grind of redesigns. Early demos had shown overlapping windows, like the Macintosh that Apple shipped in January 1984; the shipping version was reworked to use tiled windows that sat side by side and never covered each other, with a menu bar tucked under each title bar.

Through it all, Gates refused to blink. In April 1984 he told InfoWorld that "our strategies and energies as a company are totally committed to Windows," and warned that "only applications that take advantage of Windows will be competitive in the long run." One observer later wrote that Gates had pushed Windows "almost fanatically for years." In January 1985, with the product still unfinished, McGregor left and a young, loud executive named Steve Ballmer took over the job of simply getting it out the door.

The screen full of windows

On November 20, 1985 — more than two years after the press conference — Microsoft finally shipped Windows 1.0, priced at $99. It ran as a 16-bit shell on top of MS-DOS 2.0, needed a mouse to be worth using, and came bundled with a suite of small programs that would become oddly familiar over the decades: Calculator, Calendar, Cardfile, Clock, Notepad, Paint, a terminal, a card game called Reversi, and a word processor called Write. Ballmer himself starred in a now-legendary television spot, bellowing about the price like a used-car salesman.

There was one more piece of maneuvering that would echo for years. As Windows neared release, Gates negotiated an agreement with Apple's John Sculley in which Apple licensed Microsoft the right to use certain visual displays from its software in Windows 1.0. Apple thought it was protecting the Macintosh; it had, in fact, signed a document Microsoft's lawyers would later wield as a shield in the long "look and feel" lawsuit of the late 1980s.

The reviews were lukewarm. Critics complained that Windows was slow, that almost no software ran on it, and that it did not live up to three years of hype. They were not wrong. Windows 1.0 was a commercial dud, succeeded by the barely-more-successful Windows 2.0 in December 1987. The graphical revolution Gates had glimpsed at COMDEX would not truly arrive under Microsoft's banner until Windows 3.0 in 1990. But the flag was planted. Microsoft had committed itself, fanatically and publicly, to the idea that the future of the PC was graphical — and it had five more years of stubbornness in the tank.

Next in the series: Part 7 — the 1986 IPO that turned a private software company into a public fortune, and minted a generation of "Microsoft millionaires" overnight.


🔗 Explore more from Syncster

Comments

Popular posts from this blog

Cursor AI Review: Is the AI Code Editor Worth It?

I've been using Cursor as my main code editor for a while now, and enough people have asked whether it's worth switching to that a proper review felt overdue. Short version: for me, yes — but with caveats. What is Cursor? Cursor is an AI-first code editor built as a fork of VS Code. That means every extension, theme, and keybinding you already use in VS Code works here, but with AI woven directly into the editing experience instead of bolted on as a plugin. It's made by Anysphere and can run models from OpenAI and Anthropic under the hood. What I like Tab completion is uncanny. Cursor predicts your next edit — not just the rest of the line, but the next change across the file. Once you get used to hitting Tab, going back to a plain editor feels slow. The Composer / Agent mode. You describe a change in plain language and it edits multiple files at once, showing you a diff to accept or reject. For refactors and boilerplate, this saves real time. It unde...

MacBook Pro M5 vs M5 Pro: Which One Should You Actually Buy?

Apple's latest 14-inch MacBook Pro comes in two very different flavors: the base M5 and the step-up M5 Pro . On paper they look similar — same gorgeous Liquid Retina XDR display, same design — but under the hood the gap is bigger than the names suggest. Here's a clear, no-hype breakdown, with concrete use cases so you can match the chip to your work. Quick spec comparison Spec M5 M5 Pro CPU 10-core (4 performance + 6 efficiency) Up to 18-core (6 performance + 12 efficiency) GPU 10-core Up to 20-core Neural Engine 16-core 16-core Memory bandwidth 153 GB/s 307 GB/s (roughly double) Unified memory 16 / 24 / 32 GB 24 / 48 / 64 GB Max storage Up to 4 TB SSD Up to 8 TB SSD Battery (video playback) Up to 24 hours Up to 22 hours Media engines Single encode/ProRes engine More encode/ProRes engines (higher configs) What actually changes between them More cores — the M5 Pro nearly doubles CPU cores and adds GPU cores, so sustained, multi-threaded work finishe...

How I used Google Sheets and Apps Script

Google Sheet is one of the most powerful spreadsheet application that exists online, rivaling with Microsoft's Excel. One of the main strengths is its strong support for collaboration with other users, much easier and popular than collaboration tools with Microsoft Office. Aside from plain spreadsheet, it also supports extensions such as macro. If you are familiar with macros on other office tools, they work almost the same. However, the most extension I use and tinker with is the Apps Scipt . Apps Script Extension One of the challenges I faced recently is how do I track or monitor reports in our department if they are submitted on time or worst, forgotten due to lack of better monitoring tools. So I thought if there can be simple applications that can be deployed or use by a more general user to allow reminding periodically what reports are approaching due dates or those that are past dues. Then I looked for a way, instead of creating a full blown app from scratc...