Gary Kildall: The CP/M Genius Who Lost the IBM Deal to Bill Gates

SPEAKER_1 (0:00)

You have probably never heard the name Gary Kildall.

SPEAKER_2 (0:04)

Yeah, most people haven't, which is wild.

SPEAKER_1 (0:06)

It is. Yeah. Because if you look at the device you're using to listen to this right now, or the computer sitting on your desk, you are interacting with a digital landscape that he basically designed. I mean, we're talking about the person who built the very first practical operating system for personal computers.

He pioneered the tech that makes CD-ROMs work, built this massive multi-million dollar software empire from scratch.

SPEAKER_2 (0:29)

Yep, completely from the ground up.

SPEAKER_1 (0:31)

And yet despite all that undeniable genius, history mostly remembers him for a rumor, this myth that he capriciously decided to go fly an airplane instead of taking a crucial business meeting with IBM.

SPEAKER_2 (0:44)

It's honestly one of the most stunning contradictions in modern tech history.

SPEAKER_1 (0:48)

Seriously.

SPEAKER_2 (0:49)

We tend to like our historical narratives to be neat and tidy. We want a clear victor.

SPEAKER_1 (0:55)

Right, the whole Steve Jobs or Bill Gates narrative.

SPEAKER_2 (0:58)

But reality rarely works that way. And the narrative that survived about that day, it completely misrepresents the man.

SPEAKER_1 (1:06)

Well, that is exactly what we're going to fix today. Welcome to this Deep Dive. Our mission today is to uncover the true story of Gary Kildall. We want to look past the myths and really examine how one man shaped the architecture of the digital age, only to have his legacy almost completely eclipsed by Bill Gates and Microsoft.

SPEAKER_2 (1:24)

To truly understand the modern personal computer, you really have to understand Gary Kildall.

Because this isn't just a story about a single business deal gone wrong. It's a story about how the fundamental rules of software were written, how hardware learned to communicate, and ultimately, who gets the credit for building the modern world.

SPEAKER_1 (1:43)

Let's start from the beginning because his background isn't really what you'd expect from a Silicon Valley Titan.

SPEAKER_2 (1:48)

Not at all.

SPEAKER_1 (1:48)

I was looking at his early years and he wasn't some child prodigy hacking mainframes in a basement. He was born in Seattle in 1942 and his family actually ran a seamanship school.

SPEAKER_2 (1:59)

Yeah, that's a fascinating detail.

His father was a captain of Norwegian descent. His mother had Swedish roots, so they were very much tied to the maritime world.

SPEAKER_1 (2:07)

Wow.

SPEAKER_2 (2:08)

In high school, Gary actually considered himself a bit of a greaser.

SPEAKER_1 (2:11)

Wait, really a greaser?

SPEAKER_2 (2:13)

Yeah. He was into cars, having fun, that sort of thing. His original career plan was literally just to become a high school math teacher.

SPEAKER_1 (2:20)

So, how does a guy who wants to teach algebra end up inventing the modern operating system?

SPEAKER_2 (2:26)

Well, he earned his bachelor's degree in math, and then he stayed for a master's in computer science at the University of Washington in the late 60s. Okay. The technology just pulled him in. Eventually, he gets drafted into the Navy.

SPEAKER_1 (2:37)

But he doesn't go to sea, right?

SPEAKER_2 (2:39)

Right. Instead of going to sea, he fulfills his service by teaching at the Naval Postgraduate School down in Monterey, California.

SPEAKER_1 (2:45)

Oh, nice.

SPEAKER_2 (2:46)

During this time, he actually finishes his doctorate in 1972

SPEAKER_1 (2:49)

Okay. Let's unpack this because this places him perfectly in California just as the tech world is starting to boil over, right?

SPEAKER_2 (2:57)

Precisely.

It's the early 1970s. Intel is just starting to manufacture their early microprocessors.

SPEAKER_1 (3:04)

The 8008 and 8080 chips?

SPEAKER_2 (3:06)

Exactly. These were basically tiny brains for computers, but they were incredibly limited.

Intel actually loaned some of these very early systems to Kildall just to see what he could do with them.

SPEAKER_1 (3:17)

Okay. I want to pause right here because the sources mentioned he developed something called PLM in 1973, and it was the first high-level programming language for microprocessors. For those of us who don't write code for a living, what does a high-level language actually mean? Why was it such a big deal?

SPEAKER_2 (3:34)

Think about it like trying to build a house by physically directing every single swing of a hammer and every single turn of a screw.

SPEAKER_1 (3:42)

Sounds exhausting.

SPEAKER_2 (3:43)

It was.

Before PLM writing software for these tiny chips meant dealing with incredibly tedious low-level machine code. Right. You were essentially feeding the computer raw ones and zeros, or just highly cryptic commands, just to move a tiny piece of data from one microscopic register to another.

SPEAKER_1 (4:00)

That sounds absolutely agonizing.

SPEAKER_2 (4:02)