Connect your Claude, Codex or OpenClaw for full transcripts on millions of podcasts. Two week free trial, cancel anytime.

Start free trial →
JG James Gosling On The Stack Overflow Podcast

“Rule one is thou must not kill your customer. And that goes for everything from people who build elevators to people who build toasters. Do not kill your customer. Nothing must go wrong ever.”

The Stack Overflow Podcast · Hands-On Engineering Podcasts · October 2026

“Rule one is thou must not kill your customer. And that goes for everything from people who build elevators to people who build toasters. Do not kill your customer. Nothing must go wrong ever.” — James Gosling, The Stack Overflow Podcast

Context

Gosling was explaining how Java began: Sun was working with consumer electronics makers, a world that cared far more about reliability than the pre-1995 computer industry did. Nobody asked him to write a language, he says; he and a few friends decided the compiler tools had to be fixed.

Transcript

The Stack Overflow Podcast Around 07:03 into the episode
James Gosling

I was never asked to create a programming language.

Ryan Donovan

Oh, all right.

James Gosling

…this in C. And this was a universe that cared deeply about reliability. And in the conventional computing industry of pre-1995, people were pretty casual about reliability and often being willing to trade reliability for performance. And this is kind of like what happens with cars, right? If you've got a high-performance car, they break more often. You know, same thing with computers, right? Rule one is thou must not kill your customer. And that goes for everything from people who build elevators to people who build toasters. Do not kill your customer. Nothing must go wrong ever. There was that. There was the emerging interconnectedness of it. I mean, one of the amusing things that was going on at the time was that all these companies were realizing that, oh, being interconnected would be useful. So they were all reinventing computer networking and they were all basically repeating the stupid things that people in the computer industry had tried. And I can't tell you how…

Ryan Donovan

Yeah. Because you're building that custom device. This was a world of very like proprietary hardware, proprietary software, right? Back in the early 90s.

James Gosling

The people who were building these devices, they hated the proprietary hardware thing. The interesting people to talk to were like the purchasing agents, the people who just bought the parts, because they're building circuit boards and boxes that they put the circuit boards into and stuff like…

Ryan Donovan

Sure. Memory issues are all over the place, right?

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from The Stack Overflow Podcast