WEBVTT - The Intel Story Part Two

0:00:04.519 --> 0:00:12.840
<v Speaker 1>Technology with tech Stuff from stuff works dot com. Hey there,

0:00:12.880 --> 0:00:17.000
<v Speaker 1>and welcome to text Stuff. I am your host, Jonathan Strickland.

0:00:17.200 --> 0:00:21.000
<v Speaker 1>I'm a senior writer here with how stuff works dot com.

0:00:21.040 --> 0:00:24.760
<v Speaker 1>And today we're going to continue our story about Intel,

0:00:25.440 --> 0:00:29.880
<v Speaker 1>a very important company in the history of Silicon Valley

0:00:29.920 --> 0:00:33.760
<v Speaker 1>and electronics and computing in general. Now, in our last episode,

0:00:34.080 --> 0:00:37.600
<v Speaker 1>we really focused on the origins of Intel and traced

0:00:37.640 --> 0:00:40.080
<v Speaker 1>it all the way back to the birth of the

0:00:40.159 --> 0:00:45.720
<v Speaker 1>semiconductor industry itself. Two of the co founders of Intel,

0:00:45.920 --> 0:00:50.280
<v Speaker 1>Gordon Moore and uh and Rob Noyce. They had come

0:00:50.360 --> 0:00:56.480
<v Speaker 1>from a a an organization that didn't treat them very well,

0:00:56.640 --> 0:00:59.840
<v Speaker 1>and so they, along with six other people, left that organization.

0:00:59.880 --> 0:01:03.640
<v Speaker 1>They became known as the Traitorous Eight and founded the

0:01:03.840 --> 0:01:07.959
<v Speaker 1>fair Child Semiconductor business under the umbrella of a larger

0:01:08.040 --> 0:01:13.240
<v Speaker 1>company that did camera and instrumentation work. Worked there for

0:01:13.240 --> 0:01:17.160
<v Speaker 1>about eleven years before they left that company to co

0:01:17.360 --> 0:01:21.399
<v Speaker 1>found Intel. And in our last episode, I ended right

0:01:21.440 --> 0:01:25.520
<v Speaker 1>around the time that they had introduced their first micro processor,

0:01:25.680 --> 0:01:28.960
<v Speaker 1>the four zero zero four. Now we're gonna pick up

0:01:29.000 --> 0:01:31.039
<v Speaker 1>from that point forward. We're also going to backtrack a

0:01:31.040 --> 0:01:34.720
<v Speaker 1>little bit just to explain some other details, and we're

0:01:34.720 --> 0:01:38.320
<v Speaker 1>gonna explore what Intel was all about since its founding

0:01:38.440 --> 0:01:43.200
<v Speaker 1>up until present day. Now, the four zero zero four

0:01:43.280 --> 0:01:46.760
<v Speaker 1>started off as one of a set of four chips.

0:01:47.200 --> 0:01:50.400
<v Speaker 1>It's like a package of four chips that were designed

0:01:50.440 --> 0:01:53.880
<v Speaker 1>specifically for another company. That company was the Nipon Calculating

0:01:53.920 --> 0:01:58.320
<v Speaker 1>Machine Corporation. Now, the original designation for those four chips

0:01:58.480 --> 0:02:04.880
<v Speaker 1>was the MCS DASH four. Along with that four oh

0:02:04.960 --> 0:02:08.400
<v Speaker 1>four or four zero zero four, I should say chip,

0:02:08.840 --> 0:02:12.520
<v Speaker 1>were three others. Right. You had a chip that was

0:02:12.600 --> 0:02:17.480
<v Speaker 1>a read only memory chip or ROM chip that was

0:02:17.639 --> 0:02:21.800
<v Speaker 1>responsible for storing the custom applications for calculating machines. So

0:02:21.919 --> 0:02:24.720
<v Speaker 1>essentially the programs of these calculating machines were stored and

0:02:24.760 --> 0:02:26.919
<v Speaker 1>read only memory. That meant that you could not write

0:02:27.000 --> 0:02:30.359
<v Speaker 1>over that information. It was always going to be there.

0:02:30.360 --> 0:02:33.480
<v Speaker 1>It was hard coded onto the chip itself, and that

0:02:33.600 --> 0:02:36.000
<v Speaker 1>way it made it efficient and reliable and you didn't

0:02:36.000 --> 0:02:39.640
<v Speaker 1>have to worry about accidentally erasing it. There also was

0:02:39.720 --> 0:02:44.000
<v Speaker 1>a random access memory chip or RAM chip. Random access

0:02:44.040 --> 0:02:48.760
<v Speaker 1>memory allows you to store data in a temporary storage space,

0:02:49.040 --> 0:02:52.280
<v Speaker 1>so that way the processor can call upon that data

0:02:52.360 --> 0:02:57.080
<v Speaker 1>quickly without having to search a deeper storage UH solution.

0:02:57.880 --> 0:03:01.560
<v Speaker 1>The fourth chip was a registered chip, and that was

0:03:01.600 --> 0:03:06.080
<v Speaker 1>handling the input output port, so taking in the information

0:03:06.160 --> 0:03:09.639
<v Speaker 1>from the input devices and being able to translate that

0:03:09.720 --> 0:03:13.240
<v Speaker 1>into whatever the commands were for the CPU to process. Now,

0:03:13.240 --> 0:03:16.960
<v Speaker 1>it was the CPU that really ended up changing everything.

0:03:17.760 --> 0:03:21.480
<v Speaker 1>So Intel designed the CPU as sort of a general

0:03:21.520 --> 0:03:26.720
<v Speaker 1>purpose programmable processor. Now it wasn't a true general purpose

0:03:26.760 --> 0:03:29.160
<v Speaker 1>processor yet. That wouldn't come until a little bit later,

0:03:29.560 --> 0:03:34.920
<v Speaker 1>but it showed the promise of this strategy. It wasn't

0:03:35.000 --> 0:03:39.320
<v Speaker 1>locked into a single practical application. So up until the

0:03:39.360 --> 0:03:45.080
<v Speaker 1>early nineteen seventies, hardware for computing machines was heavily customized

0:03:45.160 --> 0:03:48.800
<v Speaker 1>for each specific machine. In other words, the chips you

0:03:48.800 --> 0:03:52.880
<v Speaker 1>would find in one type of computer, we're completely incompatible

0:03:53.200 --> 0:03:56.200
<v Speaker 1>with every other type of computer. To design the processor

0:03:56.320 --> 0:03:59.240
<v Speaker 1>for these machines, you essentially had to go back to

0:03:59.600 --> 0:04:03.160
<v Speaker 1>the big inning and rebuild the wheel every single time

0:04:03.200 --> 0:04:05.960
<v Speaker 1>you wanted to do it. Uh. There wasn't really a

0:04:06.000 --> 0:04:09.480
<v Speaker 1>concept of a general purpose processor the way the four

0:04:09.600 --> 0:04:12.840
<v Speaker 1>zero zero four was, and the concept of plug in

0:04:12.920 --> 0:04:17.160
<v Speaker 1>play would be decades further into the future. Intel's move

0:04:17.240 --> 0:04:21.159
<v Speaker 1>to create this programmable processor allowed for an explosion in

0:04:21.279 --> 0:04:25.799
<v Speaker 1>various uses. So the four zero zero four would provide

0:04:25.800 --> 0:04:28.960
<v Speaker 1>the foundation for Intel's future chips, which then would become

0:04:30.000 --> 0:04:34.280
<v Speaker 1>an instrumental component in countless types of technology, not just

0:04:34.400 --> 0:04:40.640
<v Speaker 1>computers or calculators. It virtually guaranteed Intel's success in the market.

0:04:41.560 --> 0:04:44.400
<v Speaker 1>Beyond that, the processor was able to take advantage of

0:04:44.400 --> 0:04:48.040
<v Speaker 1>the advances and manturization that had followed the invention of

0:04:48.080 --> 0:04:51.360
<v Speaker 1>the transistor. Now you'll remember from part one of this

0:04:51.520 --> 0:04:55.280
<v Speaker 1>series that Gordon Moore the one of the co founders

0:04:55.320 --> 0:04:58.360
<v Speaker 1>of Intel. He was the guy who came up with

0:04:58.440 --> 0:05:01.559
<v Speaker 1>what we now call Moore's law. All he had made

0:05:01.720 --> 0:05:05.159
<v Speaker 1>an observation that observation would become Moore's laud But the

0:05:05.200 --> 0:05:10.719
<v Speaker 1>observation said that the balance of technology, economics and manufacturing

0:05:10.760 --> 0:05:15.679
<v Speaker 1>processes would mean that for the foreseeable future. And remember

0:05:15.680 --> 0:05:18.479
<v Speaker 1>he made this production back in nineteen sixty five, the

0:05:18.560 --> 0:05:23.919
<v Speaker 1>number of discrete elements on microprocessors, on semiconductor chips would

0:05:23.960 --> 0:05:27.440
<v Speaker 1>double every two years or so. So if you were

0:05:27.480 --> 0:05:30.520
<v Speaker 1>to get a semiconductor chip in nineteen sixty seven, it

0:05:30.560 --> 0:05:33.000
<v Speaker 1>would have twice the number of transistors that you would

0:05:33.040 --> 0:05:36.039
<v Speaker 1>have found on a on a semiconductor in nineteen sixty five.

0:05:36.440 --> 0:05:39.000
<v Speaker 1>The ones in nineteen sixty nine would have twice as

0:05:39.040 --> 0:05:43.360
<v Speaker 1>many as the ones from nineteen sixty seven, and so on. Now,

0:05:43.400 --> 0:05:45.719
<v Speaker 1>by the time Intel was ready to produce the four

0:05:45.839 --> 0:05:49.000
<v Speaker 1>zero zero four chip, they could make a single CPU

0:05:49.120 --> 0:05:55.120
<v Speaker 1>microprocessor that was as powerful as the famous Eniac computer. Now,

0:05:55.120 --> 0:05:58.280
<v Speaker 1>the Eniac computer was one of the first electronic computers

0:05:58.640 --> 0:06:03.240
<v Speaker 1>ever in the history of mankind. Uh. It was constructed

0:06:03.520 --> 0:06:08.760
<v Speaker 1>in the forties, came online more or less in and

0:06:09.640 --> 0:06:12.679
<v Speaker 1>at the time it was one of it was really

0:06:12.720 --> 0:06:16.120
<v Speaker 1>the most powerful electronic computer in existence. It was one

0:06:16.160 --> 0:06:18.800
<v Speaker 1>of the first ones, so obviously it didn't have a

0:06:18.800 --> 0:06:23.400
<v Speaker 1>whole lot of competition, but it took up an entire room.

0:06:23.440 --> 0:06:26.160
<v Speaker 1>It had a lot of very large components that generated

0:06:26.160 --> 0:06:29.200
<v Speaker 1>a ton of heat. It used vacuum tubes instead of transistors.

0:06:29.839 --> 0:06:34.680
<v Speaker 1>But for this supercomputer of the early days, it would

0:06:34.720 --> 0:06:38.680
<v Speaker 1>take up an entire room. Well until's first microprocessor chip

0:06:38.760 --> 0:06:43.880
<v Speaker 1>had the equivalent amount of power stored on a chip

0:06:43.920 --> 0:06:46.880
<v Speaker 1>of semiconductor material that was the size of your fingernail.

0:06:47.520 --> 0:06:50.000
<v Speaker 1>So you went from a device that took up the

0:06:50.200 --> 0:06:52.720
<v Speaker 1>entire room in a building, and it was a big room.

0:06:52.760 --> 0:06:55.599
<v Speaker 1>It wasn't like a little office to something that could

0:06:55.640 --> 0:06:59.839
<v Speaker 1>fit on your fingernail with the equivalent amount of processing power.

0:07:00.080 --> 0:07:06.839
<v Speaker 1>This was a transformational moment in computer history, and one

0:07:06.839 --> 0:07:09.039
<v Speaker 1>of these days I'm doing I'll do a full episode

0:07:09.440 --> 0:07:12.520
<v Speaker 1>about the Eniac computer and also how it came to

0:07:12.600 --> 0:07:15.000
<v Speaker 1>be and the people who worked on it. It was

0:07:15.040 --> 0:07:18.520
<v Speaker 1>a fascinating device all on its own. In the decade

0:07:18.800 --> 0:07:22.560
<v Speaker 1>that it was in operation from around nineteen to nineteen

0:07:22.600 --> 0:07:27.920
<v Speaker 1>fifty five, researchers estimate that it ran more calculations during

0:07:27.960 --> 0:07:31.680
<v Speaker 1>that ten year period than all the calculations that had

0:07:31.720 --> 0:07:36.760
<v Speaker 1>been performed by humans leading up to that moment. So

0:07:36.880 --> 0:07:40.960
<v Speaker 1>in ten years, it did more calculations than all of

0:07:41.080 --> 0:07:45.600
<v Speaker 1>humans had done throughout history leading up to the creation

0:07:45.640 --> 0:07:52.840
<v Speaker 1>of the Eniac. That is incredible. But then it ended

0:07:52.920 --> 0:07:57.280
<v Speaker 1>up dying after it was struck by lightning. So it

0:07:57.320 --> 0:07:59.480
<v Speaker 1>has a tragic end to that story, which also means

0:07:59.480 --> 0:08:02.120
<v Speaker 1>it would make a great subject for a podcast in

0:08:02.160 --> 0:08:06.239
<v Speaker 1>the future. I think that maybe thour got a little

0:08:06.280 --> 0:08:09.400
<v Speaker 1>miffed that we humans that we're getting really confident, and

0:08:09.440 --> 0:08:11.200
<v Speaker 1>so he can kind of nipped in the bud. But

0:08:11.440 --> 0:08:15.360
<v Speaker 1>that's another story. Let's get back to Intel Now, if

0:08:15.400 --> 0:08:18.680
<v Speaker 1>you want to know what the clock speed was of

0:08:18.720 --> 0:08:21.960
<v Speaker 1>the four zero zero four, it's initial speed was one

0:08:22.200 --> 0:08:26.640
<v Speaker 1>d eight killer hurts. Now, clock speeds, in case you

0:08:26.640 --> 0:08:30.239
<v Speaker 1>aren't aware, they're measured in hurts, and it's a measure

0:08:30.280 --> 0:08:33.520
<v Speaker 1>of how many clock cycles a CPU can perform in

0:08:33.559 --> 0:08:37.360
<v Speaker 1>a second. So a hundred eight killer hurts clock speed

0:08:37.400 --> 0:08:42.160
<v Speaker 1>means that the processor can perform one eight thousand clock

0:08:42.280 --> 0:08:48.040
<v Speaker 1>cycles every second. In an ideal world, every single individual

0:08:48.160 --> 0:08:52.240
<v Speaker 1>instruction sent to a processor takes up one clock cycle.

0:08:52.760 --> 0:08:56.440
<v Speaker 1>So you could translate this as saying this processor was

0:08:56.480 --> 0:09:01.600
<v Speaker 1>capable of completing one hundred eight thousand inst ductions every second.

0:09:02.400 --> 0:09:05.920
<v Speaker 1>That's not exactly true because not all instructions take a

0:09:06.000 --> 0:09:10.720
<v Speaker 1>single clock cycle, and efficiency makes a big difference, but

0:09:11.120 --> 0:09:14.240
<v Speaker 1>it gives you a general idea of the capabilities of

0:09:14.240 --> 0:09:19.520
<v Speaker 1>this microprocessor. Now, really, when you get down to it,

0:09:19.600 --> 0:09:23.040
<v Speaker 1>everything that a processor does takes up a certain number

0:09:23.040 --> 0:09:26.439
<v Speaker 1>of clock cycles, and it depends on what the processor

0:09:26.559 --> 0:09:29.360
<v Speaker 1>needs to do, but it tells you there's a physical

0:09:29.520 --> 0:09:33.760
<v Speaker 1>limit to the number of tasks a processor can complete

0:09:34.080 --> 0:09:37.200
<v Speaker 1>within a given amount of time. So a second in

0:09:37.200 --> 0:09:42.079
<v Speaker 1>this case, if you are throwing stuff at the processor,

0:09:42.160 --> 0:09:45.720
<v Speaker 1>that takes fewer clock cycles than what it is capable

0:09:45.760 --> 0:09:48.880
<v Speaker 1>of doing. Things should run pretty smoothly, right. If the

0:09:48.960 --> 0:09:51.880
<v Speaker 1>number of instructions you're sending to the processor is less

0:09:51.880 --> 0:09:56.400
<v Speaker 1>than the processors clock speed, it should be a pretty

0:09:56.440 --> 0:10:00.720
<v Speaker 1>smooth experience for you on the user side of the computer.

0:10:01.160 --> 0:10:03.960
<v Speaker 1>But as you start to throw more processor hungry tasks

0:10:04.080 --> 0:10:06.800
<v Speaker 1>at the chip, you can start to slow down because

0:10:06.920 --> 0:10:11.120
<v Speaker 1>you might be throwing more directions per second than it

0:10:11.200 --> 0:10:13.840
<v Speaker 1>can handle, and then you start getting lag and things

0:10:14.160 --> 0:10:17.200
<v Speaker 1>get jittery and slow. There are a lot of other

0:10:17.200 --> 0:10:19.760
<v Speaker 1>factors that affect us as well, including how efficient that

0:10:19.840 --> 0:10:24.280
<v Speaker 1>processor is. Some processors are more efficient and can do

0:10:24.840 --> 0:10:30.280
<v Speaker 1>the same task with fewer clock cycles than a similar processor.

0:10:30.640 --> 0:10:34.240
<v Speaker 1>So if you get two different processors and they have

0:10:34.320 --> 0:10:37.640
<v Speaker 1>similar clock speeds, but one of them is designed and

0:10:37.760 --> 0:10:42.000
<v Speaker 1>optimized so that it's much more efficient, you can do

0:10:42.240 --> 0:10:45.040
<v Speaker 1>more with that processors than you can with the other one,

0:10:45.120 --> 0:10:48.280
<v Speaker 1>even if they're both rated at the same clock speed,

0:10:48.600 --> 0:10:52.920
<v Speaker 1>just because the other one handles tasks more efficiently than

0:10:53.040 --> 0:10:56.440
<v Speaker 1>it's uh than it's peer. This is true even if

0:10:56.480 --> 0:11:00.920
<v Speaker 1>you have two processors that have different clock speeds. If

0:11:00.920 --> 0:11:04.959
<v Speaker 1>you've got one processor that has a measurably faster clock

0:11:05.040 --> 0:11:08.640
<v Speaker 1>speed than your first one, but the first one is

0:11:08.679 --> 0:11:12.960
<v Speaker 1>still more efficient. You can still end up having a

0:11:12.960 --> 0:11:19.600
<v Speaker 1>better experience using the quote unquote slower microprocessor because it

0:11:19.720 --> 0:11:23.000
<v Speaker 1>is more efficient in its design. So that's something to

0:11:23.080 --> 0:11:27.200
<v Speaker 1>keep in mind if you're ever shopping for microprocessors. Just

0:11:27.360 --> 0:11:30.679
<v Speaker 1>looking for that clock speed is not really an indicator

0:11:30.760 --> 0:11:35.199
<v Speaker 1>of how good that microprocessor is. It is an indicator,

0:11:35.720 --> 0:11:37.640
<v Speaker 1>but it is not the only one you should pay

0:11:37.679 --> 0:11:40.199
<v Speaker 1>attention to. It's kind of like when you go shopping

0:11:40.240 --> 0:11:43.480
<v Speaker 1>for digital cameras and you start looking at megapixel numbers.

0:11:44.200 --> 0:11:49.440
<v Speaker 1>Larger megapixel numbers doesn't necessarily equate with better pictures. There

0:11:49.480 --> 0:11:52.880
<v Speaker 1>are a lot of other factors that are very important

0:11:52.920 --> 0:11:57.200
<v Speaker 1>when it comes to color, representation, contrast, all of these

0:11:57.240 --> 0:12:01.640
<v Speaker 1>other elements that go into creating digital images. So I

0:12:01.679 --> 0:12:03.559
<v Speaker 1>just want to bring that out here in this part

0:12:03.600 --> 0:12:06.040
<v Speaker 1>of the podcast, just in case you are looking at

0:12:06.440 --> 0:12:08.480
<v Speaker 1>building a computer and you want to find a really

0:12:08.480 --> 0:12:12.040
<v Speaker 1>good micro processor. Just going for that high number is

0:12:12.040 --> 0:12:14.280
<v Speaker 1>not a guarantee that you're getting the absolute best for

0:12:14.320 --> 0:12:17.080
<v Speaker 1>your money. You have to take these other elements into consideration.

0:12:18.000 --> 0:12:20.880
<v Speaker 1>Uh So, I know it's a bit of a tangent.

0:12:21.400 --> 0:12:26.080
<v Speaker 1>But it's important to remember just because otherwise we oversimplify

0:12:26.200 --> 0:12:31.239
<v Speaker 1>and say a higher clock speed equals a faster, better processor.

0:12:31.400 --> 0:12:38.040
<v Speaker 1>That's not always the case. Uh. Anyway, back in Killer

0:12:38.120 --> 0:12:43.520
<v Speaker 1>Hurts was wicked fast. That was a really fast processing time. Today,

0:12:43.640 --> 0:12:47.520
<v Speaker 1>something like Intel's Core I seven KB Lake processor can

0:12:47.600 --> 0:12:51.160
<v Speaker 1>run at four and a half giga Hurts. That means

0:12:51.240 --> 0:12:55.120
<v Speaker 1>it can run four and a half billion clock cycles

0:12:55.160 --> 0:12:57.600
<v Speaker 1>per second. It can handle four and a half billion

0:12:57.640 --> 0:13:00.840
<v Speaker 1>instructions per second. Compare that to the four zero zero

0:13:00.880 --> 0:13:03.520
<v Speaker 1>four that was a hundred eight thousand, four and a

0:13:03.520 --> 0:13:07.559
<v Speaker 1>half billion. You start to see the power of Moore's

0:13:07.640 --> 0:13:11.400
<v Speaker 1>law how that plays out over time, and being able

0:13:11.440 --> 0:13:16.760
<v Speaker 1>to go into the billions of instructions per second would

0:13:16.760 --> 0:13:19.840
<v Speaker 1>probably have amazed even Gordon Moore back in the day,

0:13:19.920 --> 0:13:23.360
<v Speaker 1>because when he was making this observation he didn't necessarily

0:13:23.440 --> 0:13:28.239
<v Speaker 1>think this would be sustainable indefinitely. He thought that eventually

0:13:28.240 --> 0:13:32.080
<v Speaker 1>we would run into some sort of fundamental limit as

0:13:32.120 --> 0:13:34.840
<v Speaker 1>to what we are able to accomplish, and at that

0:13:34.920 --> 0:13:38.680
<v Speaker 1>point the actual progression would break down and you would

0:13:38.720 --> 0:13:43.280
<v Speaker 1>no longer be able to have a processor that's effectively

0:13:43.320 --> 0:13:47.640
<v Speaker 1>twice as powerful two years into the future because we

0:13:47.679 --> 0:13:51.360
<v Speaker 1>would have bumped up against some sort of fundamental limit

0:13:51.520 --> 0:13:55.120
<v Speaker 1>that would prevent us from doing that. Now, for the

0:13:55.160 --> 0:13:58.560
<v Speaker 1>four zero zero four, Intel was using two inch wafers,

0:13:59.120 --> 0:14:04.079
<v Speaker 1>which is interesting because typically semiconductor companies were using twelve

0:14:04.120 --> 0:14:08.559
<v Speaker 1>inch wafers to design microchips, but Intel was using two

0:14:08.559 --> 0:14:11.439
<v Speaker 1>inch wafers for this one. And that might sound delicious.

0:14:11.480 --> 0:14:15.240
<v Speaker 1>You're hearing wafer, you might be thinking cookies. It's not.

0:14:15.600 --> 0:14:18.360
<v Speaker 1>The wafer is called that because it's a big circular disk,

0:14:18.760 --> 0:14:21.040
<v Speaker 1>or in the case of the four zero zero four,

0:14:21.080 --> 0:14:25.400
<v Speaker 1>they're using small circular discs. But a wafer is a substrate.

0:14:25.960 --> 0:14:30.760
<v Speaker 1>It's a foundation. It is the ground upon which you

0:14:30.800 --> 0:14:34.920
<v Speaker 1>build a processor or you build a circuit. It's made

0:14:34.920 --> 0:14:39.600
<v Speaker 1>of semiconductor material It's frequently silicon these days, it's more

0:14:39.640 --> 0:14:42.280
<v Speaker 1>often silicon than anything else, but there are other types

0:14:42.320 --> 0:14:45.560
<v Speaker 1>of semiconductor materials, so I don't want you thinking silicon

0:14:45.760 --> 0:14:50.160
<v Speaker 1>is the one and only type. There are others. Silicon

0:14:50.640 --> 0:14:55.760
<v Speaker 1>wafers are usually twelve inches in diameter, not two inches

0:14:55.800 --> 0:14:58.479
<v Speaker 1>in diameter, so this was a bit of a departure.

0:14:58.720 --> 0:15:01.640
<v Speaker 1>But you have to imagine in a really shiny disk

0:15:01.800 --> 0:15:04.440
<v Speaker 1>that has like a grid like pattern across it that's

0:15:04.440 --> 0:15:08.840
<v Speaker 1>repeated over and over and over again. Uh, the patterns

0:15:08.880 --> 0:15:11.800
<v Speaker 1>that you see, that's actually the patterns of where circuits

0:15:12.040 --> 0:15:15.120
<v Speaker 1>will be laid. So it's not just a design, that's

0:15:15.160 --> 0:15:19.080
<v Speaker 1>actually the physical architecture of where the circuits are going

0:15:19.120 --> 0:15:22.200
<v Speaker 1>to be. They don't just come out that way. They

0:15:22.240 --> 0:15:25.080
<v Speaker 1>have to be etched that way. When you first create

0:15:25.320 --> 0:15:28.320
<v Speaker 1>these silicon wafers and you and you get them polished,

0:15:28.600 --> 0:15:32.520
<v Speaker 1>they are just reflective. They don't have any grid like

0:15:32.600 --> 0:15:36.240
<v Speaker 1>patterns on them. Now, for the geometrically minded out there,

0:15:36.280 --> 0:15:38.840
<v Speaker 1>you might wonder, why the heck would you produce round

0:15:39.040 --> 0:15:44.640
<v Speaker 1>silicon wafers when microprocessors are rectangular. Now, obviously you can

0:15:44.800 --> 0:15:48.080
<v Speaker 1>build a bunch of microprocessors on top of a wafer

0:15:48.080 --> 0:15:51.040
<v Speaker 1>and then you cut them out. So you use your

0:15:51.080 --> 0:15:55.720
<v Speaker 1>wafer to be the the foundation for all of your microprocessors.

0:15:55.760 --> 0:15:58.800
<v Speaker 1>You you etch it out using a repeated pattern over

0:15:58.840 --> 0:16:02.640
<v Speaker 1>and over again. You build out the microprocessors, then you

0:16:02.680 --> 0:16:04.480
<v Speaker 1>cut them all out, and you get your little dies

0:16:04.840 --> 0:16:10.200
<v Speaker 1>of of CPU chips or other microchips, doesn't have to

0:16:10.240 --> 0:16:13.320
<v Speaker 1>be just ae CPU. Other microchips also followed this pattern,

0:16:14.040 --> 0:16:16.680
<v Speaker 1>but you're thinking, well, if it's round and ultimately the

0:16:16.760 --> 0:16:19.360
<v Speaker 1>chips are square, that means there's a lot of waste, right, Like,

0:16:19.440 --> 0:16:23.960
<v Speaker 1>you start to get where the edges of the the

0:16:24.040 --> 0:16:28.400
<v Speaker 1>individual microprocessors are coming up against the edge of the disk. Well,

0:16:28.440 --> 0:16:30.960
<v Speaker 1>square and circle, they're not going to match up perfectly,

0:16:30.960 --> 0:16:33.280
<v Speaker 1>so you're gonna have some wasted material. Why would you

0:16:33.320 --> 0:16:37.360
<v Speaker 1>go with a disc in the first place. Well, in

0:16:37.440 --> 0:16:39.160
<v Speaker 1>order to answer this question, I'm gonna have to talk

0:16:39.200 --> 0:16:42.000
<v Speaker 1>about how these chips are made today for the most part.

0:16:42.080 --> 0:16:45.200
<v Speaker 1>But remember that the process back when Intel made it's

0:16:45.240 --> 0:16:48.560
<v Speaker 1>four zero zero four chip was similar but not nearly

0:16:48.600 --> 0:16:53.160
<v Speaker 1>as sophisticated as the way we do it today. Um,

0:16:53.200 --> 0:16:58.600
<v Speaker 1>the microprocessor manufacturers cut wafers up to make several microprocessors

0:16:58.600 --> 0:17:03.640
<v Speaker 1>per wafer, but that does create some way. So here's

0:17:03.720 --> 0:17:09.560
<v Speaker 1>why we have round wafers instead of say, square wafers.

0:17:09.600 --> 0:17:15.480
<v Speaker 1>It's because we grow the wafers and it's done in

0:17:15.480 --> 0:17:18.240
<v Speaker 1>a very interesting way. So imagine that your goal is

0:17:18.280 --> 0:17:22.800
<v Speaker 1>to create a sheet of silicon that's perfect from a microprocessor.

0:17:23.040 --> 0:17:25.720
<v Speaker 1>That means you have to have an incredible amount of

0:17:26.200 --> 0:17:29.000
<v Speaker 1>pure silicon, or as close to pure silicon as you

0:17:29.040 --> 0:17:34.680
<v Speaker 1>can possibly manage. Any sort of impurity will introduce electrical

0:17:34.800 --> 0:17:39.080
<v Speaker 1>elements into your substrate that you don't want because that's

0:17:39.119 --> 0:17:41.200
<v Speaker 1>going to create errors. So you need it to be

0:17:41.240 --> 0:17:44.040
<v Speaker 1>as pure as you possibly can make it. You then

0:17:44.080 --> 0:17:47.040
<v Speaker 1>treat it to allow transistors and other components to transmit

0:17:47.080 --> 0:17:51.800
<v Speaker 1>electricity across the circuit without having it bleed through or

0:17:51.880 --> 0:17:55.960
<v Speaker 1>leach away the substrate. Because silicon is a semiconductor and

0:17:55.960 --> 0:17:58.760
<v Speaker 1>can either conduct or insulate based on properties, it is

0:17:58.840 --> 0:18:03.639
<v Speaker 1>ideal for this. And we start with sand. Sand has

0:18:03.680 --> 0:18:07.760
<v Speaker 1>a very high percentage of silicon in it, and again

0:18:07.840 --> 0:18:11.720
<v Speaker 1>silicon is our semiconductor material of choice. The sand gets

0:18:11.760 --> 0:18:14.800
<v Speaker 1>melted down and then you eventually end up with a

0:18:14.840 --> 0:18:19.360
<v Speaker 1>material called polly or poly silicon, and you use this

0:18:19.480 --> 0:18:22.960
<v Speaker 1>to um you separate out as much of the impurities

0:18:23.000 --> 0:18:27.800
<v Speaker 1>as you possibly can to you get to pure silicon.

0:18:28.480 --> 0:18:32.240
<v Speaker 1>You melt down ingots of this stuff into a purged

0:18:32.480 --> 0:18:35.760
<v Speaker 1>furnace at a temperature of more than two thousand, five

0:18:35.840 --> 0:18:39.640
<v Speaker 1>hundred degrees fahrenheit, which is more than one thousand, three

0:18:39.880 --> 0:18:45.760
<v Speaker 1>d seventy degrees c intigrade. The furnace must be purged

0:18:45.880 --> 0:18:50.480
<v Speaker 1>with oargon gas to make certain there's no unintended impurities present.

0:18:50.600 --> 0:18:52.720
<v Speaker 1>You want to make sure that you've gotten rid of

0:18:52.760 --> 0:18:56.919
<v Speaker 1>anything that could end up affecting the silicon as you

0:18:56.960 --> 0:18:59.920
<v Speaker 1>try to create a wafer. Now, at this point there's

0:19:00.000 --> 0:19:07.159
<v Speaker 1>about one non silicon atom per billion silicon atoms, so

0:19:07.240 --> 0:19:10.480
<v Speaker 1>that's incredibly pure. You get a billion silicon atoms and

0:19:10.480 --> 0:19:15.240
<v Speaker 1>then one thing that is not silicon. That's pretty pure.

0:19:17.119 --> 0:19:21.920
<v Speaker 1>You then have all of this molten silicon inside a crucible,

0:19:22.000 --> 0:19:27.399
<v Speaker 1>which is like a giant, uh cylindrical column, and it

0:19:27.520 --> 0:19:31.919
<v Speaker 1>keeps that molten silicon nice and hot. The crucible starts

0:19:31.960 --> 0:19:36.359
<v Speaker 1>to spin in a given direction. For the purposes of

0:19:36.400 --> 0:19:41.080
<v Speaker 1>this discussion, will say it's spinning witter shans, also known

0:19:41.119 --> 0:19:45.800
<v Speaker 1>as counter or anti clockwise, so it's spinning anti clockwise.

0:19:46.760 --> 0:19:52.199
<v Speaker 1>You then insert a seed crystal of silicon. It's about

0:19:52.280 --> 0:19:55.160
<v Speaker 1>the size and shape of a pencil, and you put

0:19:55.200 --> 0:19:59.880
<v Speaker 1>this it's lowered down by machine, into the molten sil

0:20:00.080 --> 0:20:03.879
<v Speaker 1>con and it acts as sort of the nucleaic spot

0:20:04.080 --> 0:20:06.679
<v Speaker 1>for other silicon crystals to form. And this way you

0:20:06.720 --> 0:20:14.240
<v Speaker 1>get a a very regular crystalline structure, a mono crystalline

0:20:14.280 --> 0:20:19.400
<v Speaker 1>structure of silicon, and this seed will turn in the

0:20:19.400 --> 0:20:22.480
<v Speaker 1>opposite direction of the crucible, So in our example, it

0:20:22.520 --> 0:20:28.400
<v Speaker 1>would turn clockwise while the crucible turns counterclockwise. Now, as

0:20:28.440 --> 0:20:35.320
<v Speaker 1>this happens, you end up creating this column, this cylindrical

0:20:36.040 --> 0:20:42.520
<v Speaker 1>column of pure silicon or mostly pure silicon. Uh, and

0:20:42.560 --> 0:20:45.679
<v Speaker 1>you get that monocrystalline structure all the way throughout the

0:20:45.880 --> 0:20:51.960
<v Speaker 1>entire thing. When you withdraw the cooled silicon from the crucible,

0:20:52.440 --> 0:20:56.120
<v Speaker 1>it looks like a giant silicon log that tapers at

0:20:56.119 --> 0:20:59.840
<v Speaker 1>an end because that's where you've been pulling the sea

0:21:00.160 --> 0:21:03.679
<v Speaker 1>crystal out, where you've been very slowly drawing it upwards.

0:21:03.720 --> 0:21:08.320
<v Speaker 1>You you draw it incredibly slowly, like a millimeter and

0:21:08.320 --> 0:21:12.399
<v Speaker 1>a half per minute, so it's a very very slow process.

0:21:12.480 --> 0:21:16.200
<v Speaker 1>You're not just whipping the crystal out of the molten silicon.

0:21:17.320 --> 0:21:20.400
<v Speaker 1>Doing this ends up creating, like I said, a tapered column.

0:21:20.960 --> 0:21:24.399
<v Speaker 1>And the silicon has great tent sile strength, meaning you

0:21:24.440 --> 0:21:29.600
<v Speaker 1>can suspend it from a thread like amount of silicon,

0:21:29.760 --> 0:21:35.119
<v Speaker 1>and even though it weighs between two and four pounds

0:21:35.240 --> 0:21:40.080
<v Speaker 1>or between a hundred and two hundreds, it'll hold it. However,

0:21:40.280 --> 0:21:43.080
<v Speaker 1>is very brittle, so while it has great tent sile strength,

0:21:43.160 --> 0:21:44.919
<v Speaker 1>if you were to just try and cut it. It

0:21:44.960 --> 0:21:50.120
<v Speaker 1>would cut very easily. The column or pole of silicon

0:21:50.560 --> 0:21:54.520
<v Speaker 1>would be about twelve inches or so in diameter, and

0:21:54.560 --> 0:21:57.040
<v Speaker 1>you would then use that to slice it into wafers.

0:21:57.080 --> 0:22:01.320
<v Speaker 1>So imagine this log of silicon and you put it

0:22:01.359 --> 0:22:06.280
<v Speaker 1>through a device that uses very thin wire cutters or

0:22:06.440 --> 0:22:09.480
<v Speaker 1>wire blades. I guess I should say they're not cutters,

0:22:09.480 --> 0:22:12.639
<v Speaker 1>they're they're blades made a very very thin wire that

0:22:12.800 --> 0:22:17.760
<v Speaker 1>then just zoom through this column and chop it up

0:22:17.800 --> 0:22:20.800
<v Speaker 1>into these very thin wafers. They're about a millimeter thick,

0:22:22.200 --> 0:22:25.840
<v Speaker 1>and you can get quite a few out of one

0:22:25.880 --> 0:22:30.400
<v Speaker 1>column of this silicon material. At that point, you send

0:22:30.440 --> 0:22:33.199
<v Speaker 1>them to another device to polish them out, because the

0:22:33.359 --> 0:22:38.919
<v Speaker 1>cutting creates uneven set sections on the surface of the wafers,

0:22:38.960 --> 0:22:41.120
<v Speaker 1>so you have to polish it to remove as much

0:22:41.160 --> 0:22:43.320
<v Speaker 1>of that unevenness as you can. But even that's not

0:22:43.400 --> 0:22:48.520
<v Speaker 1>good enough, because when you're building microprocessors, you're working on

0:22:48.600 --> 0:22:52.160
<v Speaker 1>the microns scale or smaller. These days, you're working on

0:22:52.560 --> 0:22:58.080
<v Speaker 1>the nano scale. At that scale, even the tiniest of

0:22:58.480 --> 0:23:02.040
<v Speaker 1>bumps or grooves is going to look like an enormous

0:23:02.040 --> 0:23:05.240
<v Speaker 1>mountain range or incredible valley. You have to buff it

0:23:05.280 --> 0:23:08.000
<v Speaker 1>all out and get it as level as you possibly can.

0:23:08.400 --> 0:23:11.560
<v Speaker 1>So after putting it through the polishing machine, you typically

0:23:11.560 --> 0:23:15.880
<v Speaker 1>would need to chemically treat the wafers to get them

0:23:15.920 --> 0:23:20.400
<v Speaker 1>as smooth as they possibly can be. Now, the next

0:23:20.440 --> 0:23:24.040
<v Speaker 1>step would involve etching the wafers to create the pattern

0:23:24.480 --> 0:23:29.320
<v Speaker 1>for your circuits. So this is sort of like building

0:23:29.359 --> 0:23:34.840
<v Speaker 1>the blueprint for the circuits directly onto the substrate itself.

0:23:35.640 --> 0:23:39.040
<v Speaker 1>Uh So, obviously, any sort of flaw in either the

0:23:39.119 --> 0:23:45.640
<v Speaker 1>silicon material or it's physical properties, whether it's the unevenness

0:23:45.880 --> 0:23:49.399
<v Speaker 1>or maybe there's an impurity that has fallen down and

0:23:49.480 --> 0:23:52.760
<v Speaker 1>touched the wafer, it's enormous when you get down to

0:23:52.800 --> 0:23:57.200
<v Speaker 1>that scale, so the tiniest of imperfections can completely ruin

0:23:57.640 --> 0:24:06.960
<v Speaker 1>a chip. For etching, Intel uses a light sensitive layer

0:24:07.400 --> 0:24:11.280
<v Speaker 1>called photo resist and coats the surface of the wafer.

0:24:12.240 --> 0:24:17.520
<v Speaker 1>That's essentially an etch resistant material. Anything that UH encounters

0:24:17.520 --> 0:24:21.200
<v Speaker 1>it is going to resist being etched. And they let

0:24:21.280 --> 0:24:25.040
<v Speaker 1>this layer harden and then they use other little stencil

0:24:25.240 --> 0:24:29.840
<v Speaker 1>like devices called masks. The masks cover parts of the

0:24:29.920 --> 0:24:32.920
<v Speaker 1>chip while allowing other parts of the chip, or rather

0:24:33.000 --> 0:24:35.760
<v Speaker 1>I should say cover parts of the wafer and allow

0:24:35.840 --> 0:24:40.000
<v Speaker 1>other parts of the wafer uh to be exposed. You

0:24:40.080 --> 0:24:44.960
<v Speaker 1>then use ultra violet light, which turns the photo resist

0:24:45.040 --> 0:24:50.720
<v Speaker 1>material it encounters soluble, and through the process of building

0:24:50.720 --> 0:24:52.760
<v Speaker 1>a circuit, you have to use lots and lots of

0:24:52.760 --> 0:24:56.320
<v Speaker 1>different masks, essentially, lots of different stencils, and lots of

0:24:56.359 --> 0:24:59.880
<v Speaker 1>applications of this ultra violet light. Because circuits are really

0:25:00.040 --> 0:25:03.760
<v Speaker 1>three dimensional creations. They're not just two dimensional. They're not

0:25:03.840 --> 0:25:08.000
<v Speaker 1>just width and and height. There's also depth to them.

0:25:08.080 --> 0:25:11.080
<v Speaker 1>So you use a sequence of these masks and you

0:25:11.720 --> 0:25:15.240
<v Speaker 1>expose the wafer to ultraviolet light. Each time the ultra

0:25:15.320 --> 0:25:19.840
<v Speaker 1>violet light hits through the mask and contacts the photo

0:25:19.960 --> 0:25:23.119
<v Speaker 1>resistive layer below, it makes it soluble. You then treat

0:25:23.520 --> 0:25:27.480
<v Speaker 1>the wafer with a chemical that removes all the soluble material.

0:25:28.000 --> 0:25:32.080
<v Speaker 1>So that's you're left with everything else. You've etched away,

0:25:32.119 --> 0:25:34.520
<v Speaker 1>all the stuff you do not want. All the stuff

0:25:34.560 --> 0:25:38.199
<v Speaker 1>you do want remains on the wafer. That is the

0:25:38.200 --> 0:25:43.960
<v Speaker 1>blueprint for your circuit. At that point, then you would

0:25:44.520 --> 0:25:47.639
<v Speaker 1>implant some ions, which are charged particles. They can have

0:25:47.680 --> 0:25:50.000
<v Speaker 1>either a positive or a negative charge, depending upon the

0:25:50.040 --> 0:25:52.320
<v Speaker 1>application you need them to be. You would either put

0:25:52.320 --> 0:25:55.240
<v Speaker 1>in positive ions or negative ions, but you use that

0:25:55.640 --> 0:25:58.359
<v Speaker 1>in the silicon itself. This is called doping. This is

0:25:58.480 --> 0:26:02.600
<v Speaker 1>used in semiconductors all the time to specifically dictate how

0:26:02.640 --> 0:26:08.640
<v Speaker 1>the semiconductor performs under specific circumstances. While you're etching, you're

0:26:08.640 --> 0:26:13.400
<v Speaker 1>creating channels for what will become transistors. The transistors themselves

0:26:13.520 --> 0:26:17.080
<v Speaker 1>must be deposited into the channels, and today Intel uses

0:26:17.160 --> 0:26:21.879
<v Speaker 1>a method called atomic layer deposition to apply materials to

0:26:21.920 --> 0:26:24.600
<v Speaker 1>the wafer surface at a level of precision necessary for

0:26:24.640 --> 0:26:28.800
<v Speaker 1>components on the nanoscale, because at that scale you're talking

0:26:28.880 --> 0:26:31.199
<v Speaker 1>about something so small you can't even see it with

0:26:31.280 --> 0:26:34.959
<v Speaker 1>an optical microscope. You would need a scanning electron microscope

0:26:35.000 --> 0:26:36.880
<v Speaker 1>or something similar in order to even get a look

0:26:36.920 --> 0:26:40.000
<v Speaker 1>at it, so obviously you have to have atomic precision

0:26:40.080 --> 0:26:45.520
<v Speaker 1>with this. Intel also uses electroplating to deposit copper ions

0:26:45.640 --> 0:26:48.320
<v Speaker 1>onto the transistor, and if you listen to my History

0:26:48.359 --> 0:26:52.040
<v Speaker 1>of Electricity episodes, you'll hear more about electroplating and how

0:26:52.080 --> 0:26:56.240
<v Speaker 1>that works. Now, since the individual components on microprocessors now

0:26:56.320 --> 0:27:00.440
<v Speaker 1>measureing the nanometers, it's critical that from this point forward,

0:27:00.880 --> 0:27:06.199
<v Speaker 1>all potential contaminants have to be eliminated from the fabrication area.

0:27:06.680 --> 0:27:09.360
<v Speaker 1>That means anyone working within the environment has to wear

0:27:09.400 --> 0:27:13.440
<v Speaker 1>a special suit often called a bunny suit, to eliminate

0:27:13.480 --> 0:27:18.200
<v Speaker 1>the possibility of dust, skin, or hair getting into the environment. Also,

0:27:18.480 --> 0:27:21.359
<v Speaker 1>they tend to have very powerful air conditioning systems which

0:27:21.359 --> 0:27:25.040
<v Speaker 1>are circulating and filtering the air on a very frequent basis.

0:27:25.400 --> 0:27:28.679
<v Speaker 1>Uh intel They're setup has air coming in from the

0:27:28.720 --> 0:27:31.399
<v Speaker 1>ceiling vents and the ceiling allow air to come down,

0:27:31.960 --> 0:27:35.359
<v Speaker 1>and then vents on the floor pull air away and

0:27:35.400 --> 0:27:38.840
<v Speaker 1>it does this constantly, so you're constantly circulating and filtering

0:27:38.880 --> 0:27:42.240
<v Speaker 1>the air to remove any potential pollutants that could ruin

0:27:42.800 --> 0:27:48.600
<v Speaker 1>a microprocessor. This is what gives us the term clean room,

0:27:48.640 --> 0:27:52.600
<v Speaker 1>and the clean rooms in semiconductor facilities tend to be

0:27:52.640 --> 0:27:56.960
<v Speaker 1>a Class one clean room, meaning there more free of

0:27:56.960 --> 0:28:01.800
<v Speaker 1>pollutants than even the most advanced hospitals. Are so extremely

0:28:01.920 --> 0:28:07.199
<v Speaker 1>clean environments, obviously, all the equipment that's being used has

0:28:07.240 --> 0:28:10.520
<v Speaker 1>to be absolutely spotless, because again, you introduce a tiny

0:28:10.560 --> 0:28:13.840
<v Speaker 1>impurity and you ruin a microchip, or worse yet, you

0:28:13.920 --> 0:28:16.919
<v Speaker 1>might ruin an entire wafer, which means all of the

0:28:16.920 --> 0:28:19.520
<v Speaker 1>microchips that would have been produced on that wafer are

0:28:19.560 --> 0:28:23.480
<v Speaker 1>a loss. You you'd have to throw them out. From

0:28:23.480 --> 0:28:27.600
<v Speaker 1>the beginning, Intel had to work on ways to design, miniaturize,

0:28:27.600 --> 0:28:30.919
<v Speaker 1>and imprint circuit layouts onto silicon, and this continues to

0:28:30.960 --> 0:28:34.639
<v Speaker 1>be an engineering challenge as companies like Intel attempt to

0:28:34.720 --> 0:28:37.960
<v Speaker 1>keep up with the observations Gordon Moore made decades ago.

0:28:38.760 --> 0:28:42.760
<v Speaker 1>The individual transistors are acting like switches, so they either

0:28:42.880 --> 0:28:46.560
<v Speaker 1>complete a circuit and allow electrons to move through, or

0:28:46.600 --> 0:28:49.520
<v Speaker 1>they break a circuit and they keep electrons from moving through.

0:28:49.600 --> 0:28:52.880
<v Speaker 1>And they're turned on and off by these devices called gates.

0:28:53.400 --> 0:28:57.000
<v Speaker 1>So a gates either open or it's closed, and that

0:28:57.080 --> 0:29:02.040
<v Speaker 1>tells you you know, essentially that the microprocessors. Ultimately their

0:29:02.120 --> 0:29:06.200
<v Speaker 1>job is traffic management. They're managing the movement of electrons

0:29:06.320 --> 0:29:11.479
<v Speaker 1>because they represent single pieces of information, either a zero

0:29:11.720 --> 0:29:14.040
<v Speaker 1>or a one and off or an on, a no,

0:29:14.440 --> 0:29:17.959
<v Speaker 1>or a yes. And collectively, when you get lots of

0:29:18.000 --> 0:29:20.800
<v Speaker 1>these dull pieces of information, you can describe much more

0:29:20.840 --> 0:29:25.680
<v Speaker 1>complex concepts than just on or off, and that's where

0:29:25.680 --> 0:29:31.000
<v Speaker 1>you get into the very basics of computer science. So

0:29:33.640 --> 0:29:38.760
<v Speaker 1>all of this, these different components have to be etched

0:29:38.920 --> 0:29:41.560
<v Speaker 1>onto the silicon, and that's because in the later stages

0:29:41.560 --> 0:29:44.720
<v Speaker 1>of manufacturing, the individual elements of the microprocessor have to

0:29:44.760 --> 0:29:46.800
<v Speaker 1>be deposited on the wafer. That can be up to

0:29:46.880 --> 0:29:52.880
<v Speaker 1>thirty layers of of material put onto a wafer before

0:29:52.880 --> 0:29:56.680
<v Speaker 1>it becomes a chip, and each incredibly tiny element needs

0:29:56.680 --> 0:29:58.880
<v Speaker 1>to be in its proper place. And these days, chip

0:29:58.920 --> 0:30:03.880
<v Speaker 1>manufacturers use variation of lithography to essentially print the components

0:30:04.440 --> 0:30:08.800
<v Speaker 1>onto the circuit etchings to build the microprocessor layer by layer.

0:30:08.880 --> 0:30:15.960
<v Speaker 1>It is incredibly precise and difficult to imagine. But we'll

0:30:15.960 --> 0:30:19.320
<v Speaker 1>talk more about that a little bit later on. First,

0:30:19.960 --> 0:30:29.400
<v Speaker 1>let's take a quick break to thank our sponsor. Back

0:30:29.400 --> 0:30:32.240
<v Speaker 1>to the four zero zero four. It had an impressive

0:30:32.440 --> 0:30:37.040
<v Speaker 1>number of transistors for the time. It had about two

0:30:37.080 --> 0:30:42.080
<v Speaker 1>thousand three transistors on this one chip. Uh, the micro

0:30:42.240 --> 0:30:46.360
<v Speaker 1>processors of today leave this processor behind in the dust.

0:30:46.400 --> 0:30:49.000
<v Speaker 1>That doesn't exist in those clean rooms I just talked about. So,

0:30:49.080 --> 0:30:53.680
<v Speaker 1>for example, the Broadwell E family of Intel processors, which

0:30:53.720 --> 0:30:57.800
<v Speaker 1>is actually from a couple of generations back well, they

0:30:58.000 --> 0:31:00.000
<v Speaker 1>launched in two thousand and sixteen and have a trans

0:31:00.000 --> 0:31:04.120
<v Speaker 1>sister account of about three point four billion. So you

0:31:04.160 --> 0:31:07.720
<v Speaker 1>went from two thousand, three hundred way back in nineteen

0:31:07.840 --> 0:31:11.640
<v Speaker 1>seventy one to three point four billion in two thousand, sixteen.

0:31:11.680 --> 0:31:15.280
<v Speaker 1>So yeah, Moore's law is no joke. While today's chips

0:31:15.280 --> 0:31:18.080
<v Speaker 1>have components that can measure just a smidge more than

0:31:18.120 --> 0:31:21.840
<v Speaker 1>a dozen nanometers in width, the four zero zero four

0:31:22.080 --> 0:31:28.240
<v Speaker 1>circuit line was ten microns wide, or ten thousand nanometers,

0:31:28.280 --> 0:31:31.800
<v Speaker 1>So the transistors of nineteen seventy one measured about ten

0:31:31.840 --> 0:31:35.720
<v Speaker 1>thousand nanometers wide. Today it's more like fourteen if you're

0:31:35.760 --> 0:31:41.720
<v Speaker 1>getting a top of the line processor, fourteen nanometers instead

0:31:41.720 --> 0:31:45.360
<v Speaker 1>of ten thousand. If you're wondering exactly how much that is,

0:31:45.400 --> 0:31:47.520
<v Speaker 1>because it's still kind of hard to imagine even like

0:31:47.640 --> 0:31:50.320
<v Speaker 1>ten thousand nanometers, how white is that, well, that's one

0:31:50.360 --> 0:31:54.440
<v Speaker 1>tenth the width of your typical human hair. Human hair

0:31:54.520 --> 0:31:58.840
<v Speaker 1>tends to be around a hundred thousand nanometers wide, not

0:31:59.000 --> 0:32:03.560
<v Speaker 1>long wide, or at least so I'm told I have

0:32:03.640 --> 0:32:06.320
<v Speaker 1>to take a lot about hair on faith these days.

0:32:07.560 --> 0:32:12.200
<v Speaker 1>I miss having hair. Well. The four zero zero four

0:32:12.280 --> 0:32:16.680
<v Speaker 1>launched and changed the world of electronics and computers. In

0:32:16.760 --> 0:32:20.280
<v Speaker 1>nineteen seventy two, Intel would expand, opening up an assembly

0:32:20.320 --> 0:32:26.040
<v Speaker 1>plant in Penang, Malaysia. This was Intel's first international manufacturing facility.

0:32:26.160 --> 0:32:30.520
<v Speaker 1>Intel also acquired a company called Microma, which was experimenting

0:32:30.520 --> 0:32:34.280
<v Speaker 1>with a new technology themselves. They were offering up digital

0:32:34.280 --> 0:32:38.160
<v Speaker 1>watches that had liquid crystal displays. This was pretty new

0:32:38.200 --> 0:32:42.160
<v Speaker 1>in the early seventies. So Intel got into the wearables

0:32:42.200 --> 0:32:45.080
<v Speaker 1>business just a couple of years after it was founded,

0:32:45.400 --> 0:32:48.080
<v Speaker 1>and people would think, oh, I thought Intel got into

0:32:48.120 --> 0:32:52.000
<v Speaker 1>the wearables business pretty recently with providing chips that could

0:32:52.000 --> 0:32:55.040
<v Speaker 1>be found in lots of different types of products out

0:32:55.040 --> 0:32:59.200
<v Speaker 1>there now. As it turns out, this early attempt to

0:32:59.200 --> 0:33:03.200
<v Speaker 1>get into wearables didn't really pan out for Intel. Uh.

0:33:03.240 --> 0:33:07.080
<v Speaker 1>Intel held onto Microma for about six years, but they

0:33:07.080 --> 0:33:11.720
<v Speaker 1>found that they had real trouble meeting consumer expectations and

0:33:11.760 --> 0:33:15.600
<v Speaker 1>figuring out exactly what consumers wanted. Because Intel was not

0:33:15.760 --> 0:33:21.880
<v Speaker 1>a consumer electronics company. Intel was building products for other businesses.

0:33:22.520 --> 0:33:26.440
<v Speaker 1>So Intel would create a processor that some other computer

0:33:26.520 --> 0:33:31.280
<v Speaker 1>manufacturer would use in its products. Intel wasn't building stuff

0:33:31.360 --> 0:33:36.680
<v Speaker 1>specifically for the end consumer, and as a result, they

0:33:36.760 --> 0:33:40.000
<v Speaker 1>weren't really good at running Microma as a business. They

0:33:40.040 --> 0:33:42.520
<v Speaker 1>held onto it for about six years and then they

0:33:42.560 --> 0:33:45.400
<v Speaker 1>sold it for a big loss. They lost about fifteen

0:33:45.440 --> 0:33:49.120
<v Speaker 1>million dollars on it. They sold it for less than

0:33:49.120 --> 0:33:51.840
<v Speaker 1>what they bought it, so it was a a tough

0:33:52.000 --> 0:33:55.880
<v Speaker 1>lesson for Intel in those early days. Jumping back to

0:33:56.640 --> 0:34:00.480
<v Speaker 1>two again, Intel created the first eight bit micro processor,

0:34:00.680 --> 0:34:04.560
<v Speaker 1>also known as the eight zero zero eight. Now, this

0:34:04.600 --> 0:34:07.360
<v Speaker 1>one obviously was more powerful than the four zero zero four,

0:34:07.400 --> 0:34:10.320
<v Speaker 1>but it still wouldn't really transform the world. It wouldn't

0:34:10.320 --> 0:34:13.600
<v Speaker 1>be until nineteen seventy four when the company introduced the

0:34:13.680 --> 0:34:16.719
<v Speaker 1>eight zero eight zero or the eight. This was the

0:34:16.760 --> 0:34:21.280
<v Speaker 1>first true general purpose microprocessor. So the four zero zero

0:34:21.320 --> 0:34:23.680
<v Speaker 1>four and the eight zero zero eight had laid the

0:34:23.719 --> 0:34:27.800
<v Speaker 1>groundwork for the eight, but it was this a D

0:34:27.960 --> 0:34:31.600
<v Speaker 1>eight that would become the basis for microprocessors in everything

0:34:31.719 --> 0:34:35.880
<v Speaker 1>from computers and calculators to traffic lights because it was

0:34:35.920 --> 0:34:39.279
<v Speaker 1>a true general purpose processor that could be used for

0:34:39.320 --> 0:34:42.360
<v Speaker 1>all sorts of different applications. So we often think of

0:34:42.440 --> 0:34:46.480
<v Speaker 1>Intel as the company that makes the processors in computers,

0:34:46.520 --> 0:34:49.319
<v Speaker 1>but the truth is they make processors that are in

0:34:49.560 --> 0:34:53.440
<v Speaker 1>all sorts of different gadgets and devices and products, not

0:34:53.600 --> 0:34:57.920
<v Speaker 1>just computers and phones. This made into one of the

0:34:57.960 --> 0:35:01.680
<v Speaker 1>most competitive companies in the space. They offered up a

0:35:01.760 --> 0:35:05.640
<v Speaker 1>computing solution in a small package for an aggressive price,

0:35:06.080 --> 0:35:09.560
<v Speaker 1>and as a result, Intel became the global leader in

0:35:09.600 --> 0:35:12.120
<v Speaker 1>microchips and held onto that title for a while. The

0:35:12.200 --> 0:35:15.240
<v Speaker 1>cost of the eight was just three d sixty dollars,

0:35:15.280 --> 0:35:18.360
<v Speaker 1>which you know they were. Intel was saying, this is

0:35:18.360 --> 0:35:21.240
<v Speaker 1>a computer on a chip. You get all the power

0:35:21.480 --> 0:35:24.279
<v Speaker 1>of a computer on a single chip that can be

0:35:24.320 --> 0:35:29.480
<v Speaker 1>incorporated into lots of different applications, and it's three sixty bucks,

0:35:29.480 --> 0:35:33.120
<v Speaker 1>which was much cheaper than full computer systems. So Intel

0:35:33.200 --> 0:35:36.600
<v Speaker 1>was doing really, really well in these days. It was

0:35:36.640 --> 0:35:40.000
<v Speaker 1>also dominant in the area of memory chips at the time,

0:35:40.360 --> 0:35:43.279
<v Speaker 1>so remember Intel had started by making chips that were

0:35:43.440 --> 0:35:47.080
<v Speaker 1>for memory, not for processing. By the end of nineteen

0:35:47.080 --> 0:35:50.719
<v Speaker 1>seventy four, Intel held eighty two point nine percent of

0:35:50.760 --> 0:35:54.719
<v Speaker 1>the d RAM chip market. Now this would change over

0:35:54.760 --> 0:35:57.440
<v Speaker 1>the next decade because other companies would get involved in

0:35:57.560 --> 0:36:01.440
<v Speaker 1>making memory chips and the competition got really fierce. And

0:36:01.480 --> 0:36:04.440
<v Speaker 1>once you get a ton of different companies all competing

0:36:04.440 --> 0:36:07.480
<v Speaker 1>with each other making the same stuff, you'll see that

0:36:07.560 --> 0:36:10.279
<v Speaker 1>product your your market share will start to drop over time,

0:36:10.360 --> 0:36:15.799
<v Speaker 1>unless you're making crazy deals by undercutting your competition. So

0:36:16.000 --> 0:36:20.880
<v Speaker 1>by a decade later, Intel's sharing the d RAM market

0:36:20.880 --> 0:36:22.839
<v Speaker 1>would have dropped all the way down to one point

0:36:22.920 --> 0:36:26.120
<v Speaker 1>three per cent. But while that memory chip business had

0:36:26.160 --> 0:36:30.760
<v Speaker 1>become incredibly competitive. Intel was still dominant in the microprocessor market,

0:36:31.440 --> 0:36:35.000
<v Speaker 1>so it wasn't as big a deal even though their

0:36:35.040 --> 0:36:41.160
<v Speaker 1>memory chip business was leaking away over time, or at

0:36:41.200 --> 0:36:44.719
<v Speaker 1>least was getting uh was being less dominant in the

0:36:44.760 --> 0:36:47.000
<v Speaker 1>market over time to the point where they had dropped

0:36:47.000 --> 0:36:50.920
<v Speaker 1>down to one point three within a decade. Because they

0:36:50.920 --> 0:36:55.160
<v Speaker 1>were the definitive name in microprocessors and more than balanced out,

0:36:55.760 --> 0:36:59.040
<v Speaker 1>they were able to recapture a lot of that success

0:36:59.080 --> 0:37:03.600
<v Speaker 1>with the microprocesss. In nineteen Robert Neiss, who was again

0:37:03.600 --> 0:37:06.120
<v Speaker 1>while the co founders, became the chairman of the board

0:37:06.160 --> 0:37:09.400
<v Speaker 1>at Intel. Noise was known as an executive who issued

0:37:09.520 --> 0:37:13.319
<v Speaker 1>the lavish trappings that many CEOs and chairpersons have indulged in.

0:37:14.280 --> 0:37:17.360
<v Speaker 1>He remained in leadership positions at Intel until his retirement,

0:37:17.840 --> 0:37:21.240
<v Speaker 1>which must not have suited him very well because after

0:37:21.239 --> 0:37:23.920
<v Speaker 1>he retired, he then went on to become the leader

0:37:23.960 --> 0:37:29.160
<v Speaker 1>of a semiconductor manufacturing consortium called Sema Tech. And Noise

0:37:29.200 --> 0:37:31.960
<v Speaker 1>would pass away in nineteen nine at the age of

0:37:32.000 --> 0:37:35.400
<v Speaker 1>sixty two. His leadership style would remain a very powerful

0:37:35.440 --> 0:37:39.120
<v Speaker 1>influence at Intel. It became sort of the model of

0:37:39.320 --> 0:37:44.040
<v Speaker 1>how leaders were expected to behave over at Intel, largely

0:37:44.080 --> 0:37:46.200
<v Speaker 1>that you were supposed to have kind of a let's

0:37:46.200 --> 0:37:49.799
<v Speaker 1>get to work sort of attitude and not have too

0:37:49.800 --> 0:37:54.640
<v Speaker 1>many lavish trappings of the executive's life. Uh, the idea

0:37:54.719 --> 0:37:59.279
<v Speaker 1>being that everyone should benefit, not just whomever's at the top. UM.

0:37:59.520 --> 0:38:03.040
<v Speaker 1>I don't know if that's how Intel's culture is now.

0:38:03.200 --> 0:38:06.920
<v Speaker 1>I haven't ever been at Intel's corporate headquarters, but I

0:38:06.960 --> 0:38:11.040
<v Speaker 1>know for a long time his values specifically were upheld

0:38:11.080 --> 0:38:15.640
<v Speaker 1>as the model for future Intel executives. Now, as you

0:38:15.719 --> 0:38:19.319
<v Speaker 1>might imagine, Intel's line of processors became more powerful with

0:38:19.400 --> 0:38:22.680
<v Speaker 1>every generation and stuck pretty close to Gordon Moore's predictions.

0:38:23.120 --> 0:38:26.600
<v Speaker 1>The processor's power tended to double every two years or so.

0:38:27.040 --> 0:38:32.000
<v Speaker 1>In nine, Intel introduced the sixteen bit eight eight six

0:38:33.200 --> 0:38:37.880
<v Speaker 1>eight six could work on to eight bit instruction sets simultaneously,

0:38:38.000 --> 0:38:41.280
<v Speaker 1>so it had a parallel processing component in it. However,

0:38:41.520 --> 0:38:45.239
<v Speaker 1>at the time, most software relied on eight bit processors

0:38:45.400 --> 0:38:49.120
<v Speaker 1>and couldn't take advantage of this sixteen bit capability, so

0:38:49.160 --> 0:38:52.440
<v Speaker 1>it's almost like it was future proofed that the software

0:38:52.480 --> 0:38:57.360
<v Speaker 1>that was out wasn't really able to enjoy the benefit

0:38:57.440 --> 0:39:01.560
<v Speaker 1>of the sixteen bit processor at the time. However, there's

0:39:01.600 --> 0:39:06.240
<v Speaker 1>a generally held belief that's been proven true multiple times

0:39:06.239 --> 0:39:10.360
<v Speaker 1>that if you build a really super strong processor, it

0:39:10.440 --> 0:39:12.759
<v Speaker 1>does not take long before someone figures out a way

0:39:12.800 --> 0:39:15.239
<v Speaker 1>to take advantage of that to build the software that

0:39:15.440 --> 0:39:18.279
<v Speaker 1>makes the best use or at least takes up a

0:39:18.320 --> 0:39:23.080
<v Speaker 1>great deal of that new super fast processors abilities. Uh.

0:39:23.160 --> 0:39:24.920
<v Speaker 1>In fact, you can get to a point where software

0:39:24.920 --> 0:39:31.320
<v Speaker 1>bloat outpaces processor performance. So it feels like generation over generation,

0:39:31.360 --> 0:39:33.879
<v Speaker 1>your processors are getting slower, But that's not really the case.

0:39:33.920 --> 0:39:37.520
<v Speaker 1>It's just that software is getting more bloated. Sometimes it's

0:39:37.560 --> 0:39:42.040
<v Speaker 1>a combination of the two. Actually. Well, by this time,

0:39:42.160 --> 0:39:45.680
<v Speaker 1>Intel was starting to face competition with Motorola, which had

0:39:45.719 --> 0:39:48.600
<v Speaker 1>introduced its own line of microprocessors in a line known

0:39:48.640 --> 0:39:51.680
<v Speaker 1>as the sixty eight thousand. This was the type of

0:39:51.719 --> 0:39:55.160
<v Speaker 1>microprocessors that would end up being used in Apple products

0:39:55.160 --> 0:39:59.080
<v Speaker 1>for a very long time. Motorola was the big uh

0:39:59.600 --> 0:40:03.320
<v Speaker 1>provide leader of micro processors for Apple. For many years,

0:40:04.840 --> 0:40:08.160
<v Speaker 1>there was a race to see which microprocessor architecture would

0:40:08.280 --> 0:40:11.000
<v Speaker 1>end up becoming the industry standard, which one is going

0:40:11.040 --> 0:40:14.680
<v Speaker 1>to be used in personal computers the most, and a big,

0:40:14.760 --> 0:40:19.759
<v Speaker 1>juicy contract helped assure that space for Intel. The contract

0:40:19.800 --> 0:40:24.239
<v Speaker 1>came from International Business Machines Corporation, which is better known

0:40:24.280 --> 0:40:28.600
<v Speaker 1>as IBM. IBM chose the eight bit processor from Intel,

0:40:28.640 --> 0:40:32.080
<v Speaker 1>called the eight eight, to be the processor of choice

0:40:32.080 --> 0:40:36.320
<v Speaker 1>in the official IBM personal computer. Line eight was based

0:40:36.320 --> 0:40:40.719
<v Speaker 1>off the design of the eighty six, the sixteen bit processor,

0:40:41.560 --> 0:40:45.160
<v Speaker 1>but the eight was an eight bit processor, so essentially

0:40:45.160 --> 0:40:48.960
<v Speaker 1>the eight had half of the address bus disabled to

0:40:49.080 --> 0:40:52.200
<v Speaker 1>make it an eight bit processor. Eventually, the pairing of

0:40:52.280 --> 0:40:55.640
<v Speaker 1>Intel chips with the Windows operating system a few years

0:40:55.800 --> 0:40:59.640
<v Speaker 1>down the line would lead to the nickname Windtell for

0:40:59.760 --> 0:41:03.440
<v Speaker 1>I b M Compatible machines, and it just showed that

0:41:03.520 --> 0:41:08.600
<v Speaker 1>Intel was considered a standard part of the IBM compatible universe.

0:41:09.160 --> 0:41:12.280
<v Speaker 1>You had an Intel processor and you had the Windows

0:41:12.320 --> 0:41:15.720
<v Speaker 1>operating system. If you didn't have those things, people didn't

0:41:15.719 --> 0:41:18.120
<v Speaker 1>really think of it as a PC. They thought of

0:41:18.160 --> 0:41:20.920
<v Speaker 1>it as something else, uh, which is a little weird,

0:41:21.239 --> 0:41:24.320
<v Speaker 1>but that just goes to show that, you know, Intel

0:41:24.360 --> 0:41:28.480
<v Speaker 1>had made some very savvy moves to become indispensable in

0:41:28.520 --> 0:41:31.480
<v Speaker 1>the personal computing industry, which ended up taking off like

0:41:31.520 --> 0:41:35.520
<v Speaker 1>gangbusters in the eighties. Now, around this time, Intel also

0:41:35.600 --> 0:41:39.759
<v Speaker 1>introduced a new innovation in computing called coprocessors. Now, these

0:41:39.760 --> 0:41:43.080
<v Speaker 1>were chips designed to take on certain tasks that typically

0:41:43.600 --> 0:41:47.160
<v Speaker 1>would go to the computer's CPU. But by freeing up

0:41:47.200 --> 0:41:50.959
<v Speaker 1>the CPU from doing those little tasks, they could run

0:41:51.120 --> 0:41:56.200
<v Speaker 1>software more efficiently. They could concentrate on the harder computational problems,

0:41:56.440 --> 0:41:59.640
<v Speaker 1>and these coprocessors would free up the CPUs by taking

0:41:59.640 --> 0:42:03.560
<v Speaker 1>on those more mundane tasks because they were very specialized

0:42:03.640 --> 0:42:06.960
<v Speaker 1>microprocessor chips and they were very efficient at handling very

0:42:07.000 --> 0:42:11.480
<v Speaker 1>specific types of computer problems. This kept the chips efficient

0:42:11.560 --> 0:42:13.839
<v Speaker 1>and kept their price down, and it also opened up

0:42:13.840 --> 0:42:17.480
<v Speaker 1>a new market for Intel to dominate. The company was

0:42:17.520 --> 0:42:20.760
<v Speaker 1>really growing rapidly at this time. Back when it was founded,

0:42:20.800 --> 0:42:26.280
<v Speaker 1>Intel had a grand total of twelve employees, but by

0:42:26.280 --> 0:42:30.319
<v Speaker 1>that number had grown to more than fifteen thousand employees.

0:42:30.880 --> 0:42:33.960
<v Speaker 1>Intel's founders tried hard to avoid falling into the same

0:42:34.000 --> 0:42:37.480
<v Speaker 1>traps they had encountered over at fair Child Semiconductor. They

0:42:37.480 --> 0:42:41.360
<v Speaker 1>were really striving to have open communication between executives and

0:42:41.440 --> 0:42:43.760
<v Speaker 1>everybody else. They wanted to make sure that their plans

0:42:43.760 --> 0:42:46.520
<v Speaker 1>were transparent, that everyone knew which way that the company

0:42:46.560 --> 0:42:50.560
<v Speaker 1>was going, and that people's concerns were listened to. Because

0:42:50.880 --> 0:42:54.040
<v Speaker 1>the founders of Intel had come from an environment where

0:42:54.080 --> 0:42:56.319
<v Speaker 1>they felt like they weren't being listened to, and they

0:42:56.400 --> 0:42:58.759
<v Speaker 1>didn't want Intel to turn into the same sort of thing.

0:42:59.560 --> 0:43:02.120
<v Speaker 1>But I've see that becomes a challenge when your workforce

0:43:02.239 --> 0:43:06.080
<v Speaker 1>numbers in the thousands of employees. So it was not

0:43:06.200 --> 0:43:10.640
<v Speaker 1>an easy thing for Intel to try and do. Now,

0:43:10.680 --> 0:43:13.160
<v Speaker 1>if you remember my podcast about the story of Macintosh,

0:43:13.239 --> 0:43:16.360
<v Speaker 1>you know I don't like to focus on every single

0:43:16.480 --> 0:43:20.359
<v Speaker 1>product that a company offers, because it just bogs down

0:43:20.440 --> 0:43:24.000
<v Speaker 1>the show. With Intel, it's particularly important. I don't do

0:43:24.040 --> 0:43:27.600
<v Speaker 1>that because the company has has had dozens of different

0:43:27.640 --> 0:43:31.400
<v Speaker 1>microprocessors in its history and hundreds of other types of products.

0:43:31.760 --> 0:43:34.120
<v Speaker 1>So we're gonna focus on a few important highlights rather

0:43:34.160 --> 0:43:36.440
<v Speaker 1>than a rundown of all the chips. Now, I don't

0:43:36.480 --> 0:43:38.719
<v Speaker 1>want to be here for a week going over an

0:43:38.719 --> 0:43:42.920
<v Speaker 1>impressive but exhaustive list of specs. I do want to

0:43:42.920 --> 0:43:47.200
<v Speaker 1>talk about some of the important early processors, though, because

0:43:47.360 --> 0:43:51.520
<v Speaker 1>I think it's it shows Intel strategy and also some

0:43:51.600 --> 0:43:53.880
<v Speaker 1>of the mistakes the company has made over its years.

0:43:55.719 --> 0:43:58.040
<v Speaker 1>The first one I would like to talk about is

0:43:58.080 --> 0:44:03.080
<v Speaker 1>the eight one six, which followed a sixteen bit architecture.

0:44:03.160 --> 0:44:07.720
<v Speaker 1>Is based off that eight six line from before starting

0:44:07.760 --> 0:44:11.800
<v Speaker 1>with the until began to incorporate components in the micro

0:44:11.960 --> 0:44:16.680
<v Speaker 1>processor that would normally be independent on a computer's motherboard. So,

0:44:16.719 --> 0:44:19.359
<v Speaker 1>in other words, Intel was looking at different parts of

0:44:19.360 --> 0:44:21.400
<v Speaker 1>the mother board and saying, well, we can lump this

0:44:21.480 --> 0:44:26.000
<v Speaker 1>in with the CPU. We can increase the response of

0:44:26.040 --> 0:44:29.520
<v Speaker 1>the CPU, we can make it more efficient, we can

0:44:29.600 --> 0:44:33.160
<v Speaker 1>decrease latency, and as a result, the entire computing experience

0:44:33.200 --> 0:44:37.720
<v Speaker 1>goes faster. This does not necessarily mean the CPU itself

0:44:37.840 --> 0:44:42.320
<v Speaker 1>is clocking faster. It's just again making that architecture more efficient.

0:44:43.160 --> 0:44:49.200
<v Speaker 1>So that was Intel strategy. The integration made sense. It

0:44:49.280 --> 0:44:52.800
<v Speaker 1>made the CPUs more efficient, made the computers much more fast.

0:44:53.120 --> 0:44:55.839
<v Speaker 1>And later that same year, Intel would release the eight

0:44:56.000 --> 0:44:58.600
<v Speaker 1>two eighties six, and at this point we would just

0:44:58.640 --> 0:45:01.440
<v Speaker 1>call it the two eight six. We would also end

0:45:01.520 --> 0:45:04.719
<v Speaker 1>up calling the next two computers the three six and

0:45:04.760 --> 0:45:07.720
<v Speaker 1>the four eight six. They were all from the same

0:45:07.880 --> 0:45:12.400
<v Speaker 1>kind of family of microprocessors. There were obviously changes and

0:45:12.480 --> 0:45:16.719
<v Speaker 1>redesigns with each generation, but they were all based off

0:45:16.719 --> 0:45:24.879
<v Speaker 1>that same architecture. In Intel Creative It's first reduced instruction

0:45:25.120 --> 0:45:31.160
<v Speaker 1>set computer or RISK microprocessor. These are more specialized processors

0:45:31.160 --> 0:45:35.280
<v Speaker 1>that concentrate on a relatively narrow band of computer instructions,

0:45:35.280 --> 0:45:38.319
<v Speaker 1>which means it can go really fast as long as

0:45:38.360 --> 0:45:41.280
<v Speaker 1>the instructions sent to it are within that narrow band.

0:45:41.320 --> 0:45:46.640
<v Speaker 1>It's kind of like a bureaucracy. Bureaucracies can handle forms

0:45:46.680 --> 0:45:50.160
<v Speaker 1>that are filled out properly very well. That's what a

0:45:50.200 --> 0:45:53.440
<v Speaker 1>bureaucracy does. But if you have a case that is

0:45:53.480 --> 0:45:59.719
<v Speaker 1>outside of the normal line, bureaucracies are terrible because they're

0:45:59.719 --> 0:46:03.960
<v Speaker 1>not signed to process stuff that's outside the norm. If

0:46:04.000 --> 0:46:07.040
<v Speaker 1>they can process something that's inside the norm, it should

0:46:07.040 --> 0:46:09.480
<v Speaker 1>go very fast. Same sort of thing is true with

0:46:09.600 --> 0:46:14.359
<v Speaker 1>risk microprocessors, except we're talking about computational problems, not licenses

0:46:14.400 --> 0:46:17.520
<v Speaker 1>and other issues that we would have when we encounter bureaucracies.

0:46:19.040 --> 0:46:22.480
<v Speaker 1>The first person to theore rise a risk microprocessor was

0:46:22.560 --> 0:46:26.239
<v Speaker 1>John Coke of IBM Research in nineteen seventy four, and

0:46:26.320 --> 0:46:29.880
<v Speaker 1>David Patterson, who taught at the University of California at Berkeley,

0:46:30.120 --> 0:46:33.040
<v Speaker 1>has the credit of coming up with the term. Intel's

0:46:33.160 --> 0:46:37.759
<v Speaker 1>I nine sixty risk microprocessors and its descendants would find

0:46:37.880 --> 0:46:44.359
<v Speaker 1>use in many applications, including military systems. In the three

0:46:44.760 --> 0:46:48.240
<v Speaker 1>six debuted, and it was the first CPU Intel designed

0:46:48.239 --> 0:46:53.600
<v Speaker 1>to be fully backwards compatible with previous CPUs. This was

0:46:53.640 --> 0:46:57.080
<v Speaker 1>a design decision that was carried forward into future microprocessors,

0:46:57.080 --> 0:46:59.640
<v Speaker 1>and it was also Intel's first thirty two bit x

0:46:59.680 --> 0:47:02.239
<v Speaker 1>a D six processor. It could support up to four

0:47:02.320 --> 0:47:06.520
<v Speaker 1>gigabytes of system memory, which at the time was a

0:47:06.680 --> 0:47:10.960
<v Speaker 1>truly enormous amount. Nobody really expected to use for gigabytes

0:47:11.000 --> 0:47:16.000
<v Speaker 1>of memory back in the mid eighties, but the architecture

0:47:16.080 --> 0:47:19.640
<v Speaker 1>texture was capable of supporting it. Now, that's not to

0:47:19.680 --> 0:47:22.720
<v Speaker 1>say that everything Intel touch turned into gold at this time.

0:47:23.080 --> 0:47:25.719
<v Speaker 1>The company also designed a processor called the i A

0:47:25.880 --> 0:47:29.600
<v Speaker 1>p X thirty two, and as you would guess by

0:47:29.640 --> 0:47:32.359
<v Speaker 1>the name and number, this did not follow the same

0:47:32.480 --> 0:47:36.319
<v Speaker 1>architecture as the X eight six chips did. This was

0:47:36.440 --> 0:47:40.520
<v Speaker 1>meant to expand its product line and differentiate microprocessors by

0:47:40.560 --> 0:47:44.520
<v Speaker 1>following a brand new architecture, but the design process did

0:47:44.560 --> 0:47:48.120
<v Speaker 1>not go smoothly. There were lots of flaws that were

0:47:48.120 --> 0:47:51.320
<v Speaker 1>introduced into the final processor design, and it was a

0:47:51.400 --> 0:47:54.480
<v Speaker 1>much more complicated design than the eight six line, and

0:47:54.520 --> 0:47:58.799
<v Speaker 1>it wasn't particularly efficient. So ultimately Intel would end up

0:47:58.800 --> 0:48:02.600
<v Speaker 1>shelving the product and saying that this was not a success.

0:48:03.520 --> 0:48:06.120
<v Speaker 1>Later in another attempt to break away from the x

0:48:06.160 --> 0:48:08.759
<v Speaker 1>A D six processor line, Intel would introduce the I

0:48:09.040 --> 0:48:14.240
<v Speaker 1>eight sixty Risk. While the early Risk microprocessors weren't intended

0:48:14.239 --> 0:48:17.040
<v Speaker 1>to go into personal computers, this was not true of

0:48:17.040 --> 0:48:20.840
<v Speaker 1>the I eight sixty. Unfortunately, like the I A p

0:48:21.160 --> 0:48:24.759
<v Speaker 1>X four thirty two, the microprocessor was flawed. It would

0:48:24.800 --> 0:48:27.960
<v Speaker 1>stall out when the processor encountered computational problems that were

0:48:27.960 --> 0:48:31.560
<v Speaker 1>outside of scope. So again, it's like that bureaucracy. When

0:48:31.880 --> 0:48:36.160
<v Speaker 1>a form doesn't have the right capability of capturing the

0:48:36.200 --> 0:48:38.480
<v Speaker 1>information you need, and you go to the bureaucracy, you're

0:48:38.480 --> 0:48:40.719
<v Speaker 1>gonna get the run around, and it's gonna be painful

0:48:40.760 --> 0:48:44.880
<v Speaker 1>and slow and laborious. Same thing was true with this processor.

0:48:45.000 --> 0:48:48.880
<v Speaker 1>It could not handle all computational problems efficiently, and that

0:48:49.280 --> 0:48:53.000
<v Speaker 1>eventually led to it not being a particularly powerful or

0:48:53.080 --> 0:48:58.520
<v Speaker 1>popular UH product in Intel's line. But the four six

0:48:58.600 --> 0:49:00.960
<v Speaker 1>was a different story that the first x A D

0:49:01.080 --> 0:49:05.399
<v Speaker 1>six CPU to incorporate an element called the functional processing unit,

0:49:05.560 --> 0:49:09.280
<v Speaker 1>or FPU, which until that time had been a separate

0:49:09.320 --> 0:49:14.480
<v Speaker 1>component from the CPU. This decreased latency between the FPU

0:49:14.680 --> 0:49:18.759
<v Speaker 1>and CPU, which translated again to faster computing speeds. The

0:49:18.840 --> 0:49:21.720
<v Speaker 1>first of these were running at clock speeds of fifty

0:49:21.800 --> 0:49:26.600
<v Speaker 1>mega hurts or fifty million clock cycles per second. Starting

0:49:26.600 --> 0:49:31.240
<v Speaker 1>a n Intel's ad campaign, Push made the company's slogan

0:49:31.400 --> 0:49:36.279
<v Speaker 1>Intel inside a common phrase in computer circles, into on

0:49:36.400 --> 0:49:40.840
<v Speaker 1>a really clever way of convincing computer companies to include

0:49:40.880 --> 0:49:45.160
<v Speaker 1>Intel chips and to use this phrase Intel inside, both

0:49:45.200 --> 0:49:48.840
<v Speaker 1>in the marketing strategy and on the computers themselves. The

0:49:48.880 --> 0:49:52.960
<v Speaker 1>way Intel convinced companies to do this as they said, Hey,

0:49:53.000 --> 0:49:55.640
<v Speaker 1>if you include our chips and you include the phrase

0:49:55.760 --> 0:50:00.440
<v Speaker 1>Intel inside in your marketing, we will pay for half

0:50:00.440 --> 0:50:04.960
<v Speaker 1>of your marketing costs. So they would shoulder half of

0:50:05.040 --> 0:50:09.400
<v Speaker 1>the marketing budget of these companies for print and television ads.

0:50:10.000 --> 0:50:13.239
<v Speaker 1>That's an enormous amount of money and Intel spent millions

0:50:13.239 --> 0:50:16.279
<v Speaker 1>of dollars doing this. But as a result, they were

0:50:16.320 --> 0:50:22.080
<v Speaker 1>able to essentially guarantee that their name would become synonymous

0:50:22.080 --> 0:50:25.080
<v Speaker 1>with computers. People thought, well, if I'm buying a computer,

0:50:25.239 --> 0:50:28.160
<v Speaker 1>a PC at any rate, not a Mac, then it's

0:50:28.200 --> 0:50:30.600
<v Speaker 1>gonna have that Intel and side sticker on there. It's

0:50:30.600 --> 0:50:33.280
<v Speaker 1>gonna have Intel inside on all the advertising, and Intel

0:50:33.320 --> 0:50:36.400
<v Speaker 1>became a household name, so it was a very valuable

0:50:36.560 --> 0:50:42.440
<v Speaker 1>move on Intel's part. In n Intel introduced the Pentium

0:50:42.600 --> 0:50:46.279
<v Speaker 1>line of processors. I remember when that happened because it

0:50:46.320 --> 0:50:49.080
<v Speaker 1>confused me because I was used to two eighty six

0:50:49.120 --> 0:50:51.480
<v Speaker 1>three eight six for eighty six, and then it went

0:50:51.560 --> 0:50:55.200
<v Speaker 1>to Pentium. These were still built on the X eight

0:50:55.320 --> 0:50:58.760
<v Speaker 1>six processor architecture, but they did depart from that eighty

0:50:58.800 --> 0:51:01.799
<v Speaker 1>six naming system. They decided to go with more trademark

0:51:01.920 --> 0:51:04.759
<v Speaker 1>names and less about just numbers. They part of this

0:51:05.000 --> 0:51:10.080
<v Speaker 1>was probably to appeal to a larger audience of computer consumers,

0:51:10.640 --> 0:51:15.360
<v Speaker 1>people who probably didn't really care for referring to processors

0:51:15.400 --> 0:51:20.160
<v Speaker 1>by what seemed to be meaningless numbers to them. Now,

0:51:20.160 --> 0:51:22.360
<v Speaker 1>as you can imagine, these chips were more efficient and

0:51:22.400 --> 0:51:25.080
<v Speaker 1>faster than their predecessors, and this helped usher in an

0:51:25.120 --> 0:51:29.680
<v Speaker 1>era of PC gaming. Among other things, the faster processors

0:51:29.719 --> 0:51:33.120
<v Speaker 1>allowed game developers to create software that was graphically intense

0:51:33.160 --> 0:51:36.279
<v Speaker 1>and fast paced. And while games had always been part

0:51:36.400 --> 0:51:40.480
<v Speaker 1>of personal computer history ever since personal computers had first

0:51:40.640 --> 0:51:44.720
<v Speaker 1>come on the scene, they now could rival consoles, which

0:51:44.840 --> 0:51:49.879
<v Speaker 1>are essentially specific computers designed to run very particular types

0:51:49.920 --> 0:51:54.399
<v Speaker 1>of software. So a console video game console like the

0:51:54.600 --> 0:51:57.080
<v Speaker 1>Xbox or back in the day of this the Super

0:51:57.160 --> 0:52:03.560
<v Speaker 1>Nintendo Nintendo Entertainment System. It's just a specialized computer. But uh,

0:52:03.680 --> 0:52:07.760
<v Speaker 1>Intel was able to show that with these Pentium processors,

0:52:08.960 --> 0:52:13.000
<v Speaker 1>personal computers could run games that would rival even the

0:52:13.040 --> 0:52:18.080
<v Speaker 1>best consoles. But there was a big problem. Those first

0:52:18.120 --> 0:52:21.160
<v Speaker 1>Pentium chips had a design flaw in them that would

0:52:21.239 --> 0:52:26.919
<v Speaker 1>cause the microprocessor to make it incorrect calculation for certain processes. Now,

0:52:26.960 --> 0:52:31.280
<v Speaker 1>this incorrect calculation didn't happen frequently, but it did happen,

0:52:32.000 --> 0:52:34.600
<v Speaker 1>and while Intel had hoped that perhaps the flaw was

0:52:34.640 --> 0:52:38.280
<v Speaker 1>so minor as to go unnoticed, that did not happen.

0:52:39.320 --> 0:52:43.239
<v Speaker 1>The reason that was noticed was due to a mathematician

0:52:43.520 --> 0:52:48.600
<v Speaker 1>named Thomas Nicely. It was a professor Nicely was actually

0:52:48.640 --> 0:52:52.880
<v Speaker 1>working on a math problem involving twin primes. So a

0:52:52.960 --> 0:52:56.000
<v Speaker 1>twin prime is a set of two prime numbers that

0:52:56.120 --> 0:53:00.480
<v Speaker 1>differ by just two. So three and five are both

0:53:00.480 --> 0:53:03.480
<v Speaker 1>prime numbers and their twin primes because five miles three

0:53:03.480 --> 0:53:07.520
<v Speaker 1>equals two, five and seven are twin primes. Seven milus

0:53:07.560 --> 0:53:11.400
<v Speaker 1>five is two. But as numbers get larger, primes become

0:53:11.680 --> 0:53:16.880
<v Speaker 1>less frequent, and twin primes become even more rare. The

0:53:16.880 --> 0:53:21.080
<v Speaker 1>philosopher Euclid created a proof that suggested there's an infinite

0:53:21.160 --> 0:53:24.640
<v Speaker 1>number of prime numbers, and he believed that the same

0:53:24.800 --> 0:53:27.000
<v Speaker 1>was going to be true of twin primes, but he

0:53:27.000 --> 0:53:31.080
<v Speaker 1>had no way of proving it well. Euclid was thinking

0:53:31.200 --> 0:53:34.520
<v Speaker 1>that way back in three hundred b c. It wouldn't

0:53:34.520 --> 0:53:36.920
<v Speaker 1>be until the twentieth century before someone came up with

0:53:36.920 --> 0:53:40.640
<v Speaker 1>a means of describing this mathematically, and that person was

0:53:40.880 --> 0:53:45.839
<v Speaker 1>Vigo Brune, a Norwegian mathematician. He said that the sum

0:53:46.120 --> 0:53:50.120
<v Speaker 1>of the reciprocals of twin primes would converge to a

0:53:50.200 --> 0:53:53.680
<v Speaker 1>constant sum that later on we would call Bruns constant.

0:53:54.360 --> 0:53:56.880
<v Speaker 1>And in case you're rusty on your mathematical terms, a

0:53:56.960 --> 0:53:59.400
<v Speaker 1>reciprocal of a number is what you get when you

0:53:59.480 --> 0:54:02.880
<v Speaker 1>take one and divide it by that number in question.

0:54:03.360 --> 0:54:07.279
<v Speaker 1>So let's say you start with five. The reciprocal of

0:54:07.360 --> 0:54:14.040
<v Speaker 1>five is one five, because again you're looking at the

0:54:14.120 --> 0:54:16.279
<v Speaker 1>one divided by the number you had started with, or

0:54:16.560 --> 0:54:19.239
<v Speaker 1>point two if you prefer. So. Brun figured out that

0:54:19.280 --> 0:54:22.560
<v Speaker 1>if you took the reciprocals of twin primes and you

0:54:22.680 --> 0:54:26.480
<v Speaker 1>added the two reciprocals together, they converged on a number

0:54:26.520 --> 0:54:29.160
<v Speaker 1>that would end up again being called Bruins constant, and

0:54:29.200 --> 0:54:31.840
<v Speaker 1>by nineteen seventy six that constant was calculated to be

0:54:31.880 --> 0:54:37.680
<v Speaker 1>approximately one point nine oh two one six o five

0:54:38.000 --> 0:54:42.680
<v Speaker 1>four for twin primes up to one hundred billion. But hey,

0:54:42.719 --> 0:54:44.799
<v Speaker 1>that's not good enough for math. We need to be

0:54:44.880 --> 0:54:49.160
<v Speaker 1>more specific than that. So enter Thomas Nicely, who bought

0:54:49.160 --> 0:54:52.960
<v Speaker 1>a computer in n with a Pentium processor and he

0:54:53.000 --> 0:54:55.960
<v Speaker 1>wanted to run calculations related to Bruin's constant. But as

0:54:56.000 --> 0:54:58.319
<v Speaker 1>he did so, he was coming up with errors that

0:54:58.360 --> 0:55:01.200
<v Speaker 1>should not have been there, and he was eventually able

0:55:01.200 --> 0:55:04.360
<v Speaker 1>to track it down to a design flaw and Intel's

0:55:04.440 --> 0:55:06.640
<v Speaker 1>chips that only showed up if you were doing some

0:55:06.680 --> 0:55:11.040
<v Speaker 1>really big calculations. That's when the flaw would make itself apparent,

0:55:11.120 --> 0:55:15.000
<v Speaker 1>but most people would never see it. At first, Intel

0:55:15.040 --> 0:55:18.880
<v Speaker 1>tried to shirk this issue, but intense pressure caused the

0:55:18.920 --> 0:55:22.480
<v Speaker 1>company to change its tune. So eventually Intel issued a

0:55:22.520 --> 0:55:26.480
<v Speaker 1>recall offering a free replacement of the affected print Pentium

0:55:26.560 --> 0:55:30.279
<v Speaker 1>chips with a modified chip that corrected this error, and

0:55:30.360 --> 0:55:34.080
<v Speaker 1>that recall would end up costing Intel four hundred seventy

0:55:34.200 --> 0:55:40.760
<v Speaker 1>five million dollars. Ouch. Well, we've got a bit more

0:55:40.800 --> 0:55:43.840
<v Speaker 1>history of Intel to talk about But before I wrap

0:55:43.880 --> 0:55:46.839
<v Speaker 1>all this up, let's take another quick break to thank

0:55:46.880 --> 0:55:58.759
<v Speaker 1>our sponsor. In Intel would debut the Pentium two. They

0:55:58.800 --> 0:56:01.400
<v Speaker 1>actually had a slight missed up between the Pentium and

0:56:01.400 --> 0:56:04.440
<v Speaker 1>the Pentium two called the Pentium Pro that didn't go

0:56:04.480 --> 0:56:06.400
<v Speaker 1>over so well, but the Pentium two was a slightly

0:56:06.440 --> 0:56:10.320
<v Speaker 1>different story, and Intel also introduced two new product lines

0:56:10.320 --> 0:56:14.120
<v Speaker 1>of processors, the Cellern and Zion brands. Now, these were

0:56:14.200 --> 0:56:18.879
<v Speaker 1>based off of Intel's existing architecture, but they had very

0:56:18.920 --> 0:56:23.320
<v Speaker 1>specific implementations where some of the bells and whistles weren't

0:56:23.360 --> 0:56:25.440
<v Speaker 1>present on them. This allowed them to be used for

0:56:25.520 --> 0:56:31.000
<v Speaker 1>very specific implementations, like you could have mid range UH

0:56:31.160 --> 0:56:36.399
<v Speaker 1>servers for example, or lower priced computers because you had

0:56:37.480 --> 0:56:39.799
<v Speaker 1>the same sort of processors but with some of the

0:56:39.840 --> 0:56:46.120
<v Speaker 1>features turned off essentially in these more mid range machines UH.

0:56:46.160 --> 0:56:49.600
<v Speaker 1>That was Intel's attempt at serving all different levels of

0:56:49.640 --> 0:56:55.640
<v Speaker 1>the market, not just the premium customers. So later on,

0:56:56.040 --> 0:57:00.359
<v Speaker 1>from that point, Intel introduced the Pentium three, which would

0:57:00.360 --> 0:57:03.600
<v Speaker 1>become the first microprocessor to break the one giga hurts

0:57:03.719 --> 0:57:06.839
<v Speaker 1>clock speed. Intel had been in a race with its

0:57:06.840 --> 0:57:10.799
<v Speaker 1>competitor a m D to create the first commercial processor

0:57:11.280 --> 0:57:14.560
<v Speaker 1>that could hit a giga hurts clock speed, and at

0:57:14.560 --> 0:57:17.560
<v Speaker 1>one point Intel even had a model of the Pentium

0:57:17.600 --> 0:57:20.160
<v Speaker 1>three that had a processing speed of or a clock

0:57:20.200 --> 0:57:23.680
<v Speaker 1>speed I should say of one point one three giga hurts,

0:57:23.720 --> 0:57:28.640
<v Speaker 1>but that one was unstable. Uh A. A review found

0:57:28.880 --> 0:57:32.080
<v Speaker 1>the performance was unstable and so that one got recalled.

0:57:33.000 --> 0:57:36.040
<v Speaker 1>But still gigga hurts clock speed meant that it could

0:57:36.080 --> 0:57:42.000
<v Speaker 1>complete a billion instructions per second under ideal circumstances. By

0:57:42.040 --> 0:57:44.920
<v Speaker 1>the late nineteen nineties, Intel was starting to get into

0:57:44.960 --> 0:57:48.680
<v Speaker 1>the business of buying other businesses. It was acquiring other

0:57:48.760 --> 0:57:52.880
<v Speaker 1>businesses to get into new markets that included wireless communications products,

0:57:53.400 --> 0:57:57.840
<v Speaker 1>networking components, and controlled chips for specific types of applications,

0:57:57.840 --> 0:58:00.320
<v Speaker 1>such as the kind you might find in v equal

0:58:00.360 --> 0:58:03.800
<v Speaker 1>control systems. And if you listen to my shows about

0:58:03.840 --> 0:58:06.680
<v Speaker 1>the Macintosh, you know that. In two thousand five, Steve

0:58:06.800 --> 0:58:10.200
<v Speaker 1>Jobs shocked the tech world when he announced that Mac

0:58:10.240 --> 0:58:13.600
<v Speaker 1>computers would move away from their traditional CPUs and use

0:58:13.760 --> 0:58:19.320
<v Speaker 1>Intel CPUs instead. Intel maintained a competitive advantage over others

0:58:19.360 --> 0:58:23.280
<v Speaker 1>in the space, but this also came at a pretty

0:58:23.320 --> 0:58:28.160
<v Speaker 1>stiff price. In two thousand nine, the European Union found

0:58:28.160 --> 0:58:33.840
<v Speaker 1>guilty Intel guilty of alleged monopolistic actions. In other words,

0:58:33.880 --> 0:58:36.800
<v Speaker 1>they said that Intel was effectively acting like a monopoly

0:58:36.960 --> 0:58:40.680
<v Speaker 1>within the European Union, and they hit Intel with a

0:58:40.760 --> 0:58:45.920
<v Speaker 1>fine that was one point four five billion dollars. That

0:58:46.040 --> 0:58:49.040
<v Speaker 1>same year, Intel had to pay its competitor, A m D,

0:58:49.520 --> 0:58:53.560
<v Speaker 1>a hefty sum of one point to five billion dollars

0:58:54.040 --> 0:58:56.280
<v Speaker 1>as part of a settlement in which am D had

0:58:56.320 --> 0:59:00.640
<v Speaker 1>accused Intel of using leverage on computer company is two

0:59:01.440 --> 0:59:06.760
<v Speaker 1>put Intel products in instead of other processors into those computers.

0:59:06.800 --> 0:59:09.479
<v Speaker 1>So essentially am D was saying Intel was being anti

0:59:09.520 --> 0:59:14.600
<v Speaker 1>competitive and really putting the screws to computer manufacturer saying

0:59:14.600 --> 0:59:17.800
<v Speaker 1>you've got to use Intel products and not anyone else,

0:59:18.520 --> 0:59:22.280
<v Speaker 1>and uh, that is not legal, which is why the

0:59:22.400 --> 0:59:26.280
<v Speaker 1>lawsuit happened, and eventually the two settled. Now I could

0:59:26.320 --> 0:59:30.400
<v Speaker 1>talk about how every generation of Intel's chips were faster,

0:59:31.560 --> 0:59:36.360
<v Speaker 1>included more on board memory, had faster bus speeds, greater

0:59:36.440 --> 0:59:39.680
<v Speaker 1>clock speeds, lower latency, but we can just sum it

0:59:39.760 --> 0:59:42.760
<v Speaker 1>up to say the company kept following a strategy that

0:59:42.880 --> 0:59:47.280
<v Speaker 1>it branded the tick talk strategy. So let me tell

0:59:47.280 --> 0:59:50.880
<v Speaker 1>you what TikTok it means and and why that has

0:59:50.920 --> 0:59:55.920
<v Speaker 1>recently changed. So TikTok is a two part strategy to

0:59:56.040 --> 1:00:03.280
<v Speaker 1>developing the microprocessors of today or really yesterday at this point,

1:00:03.280 --> 1:00:07.840
<v Speaker 1>because again we're just now beyond TikTok. The tick part

1:00:08.720 --> 1:00:14.160
<v Speaker 1>involves looking at the architecture you designed on your previous

1:00:14.200 --> 1:00:19.480
<v Speaker 1>generation of micro chips. So you look at that architecture

1:00:19.520 --> 1:00:22.360
<v Speaker 1>and you look at the size of it, and you decide,

1:00:22.480 --> 1:00:25.520
<v Speaker 1>how can I shrink down these components to the next

1:00:25.720 --> 1:00:30.520
<v Speaker 1>smaller size. That is your tick. So you might look

1:00:30.560 --> 1:00:34.320
<v Speaker 1>at a generation of processors that have forty five nanometer components,

1:00:34.960 --> 1:00:37.400
<v Speaker 1>and your challenge is to figure out how to shrink

1:00:37.480 --> 1:00:41.520
<v Speaker 1>down that same design so that the components measure thirty

1:00:41.520 --> 1:00:45.600
<v Speaker 1>two nanometers not forty five. And you follow essentially the

1:00:45.640 --> 1:00:48.480
<v Speaker 1>same blueprint as you did before, only you can cram

1:00:48.720 --> 1:00:52.680
<v Speaker 1>more stuff into that blueprint because you reduced the size

1:00:52.680 --> 1:00:55.560
<v Speaker 1>of the individual components. You freed up some space by

1:00:55.600 --> 1:01:02.080
<v Speaker 1>making everything smaller. However, at these sizes, how those components

1:01:02.120 --> 1:01:06.480
<v Speaker 1>are arranged matters more and more. So you could just

1:01:06.600 --> 1:01:10.880
<v Speaker 1>keep shrinking the components down as your research and development

1:01:10.880 --> 1:01:17.120
<v Speaker 1>allows you to make ever smaller pieces, but that only

1:01:17.160 --> 1:01:19.600
<v Speaker 1>gets you so far. What you really need to do

1:01:19.720 --> 1:01:23.480
<v Speaker 1>is figure out how to arrange those new smaller pieces

1:01:23.520 --> 1:01:27.200
<v Speaker 1>in the ideal configuration to get the most efficient use

1:01:27.280 --> 1:01:30.240
<v Speaker 1>out of them. And this is the TALK step. So

1:01:30.280 --> 1:01:33.080
<v Speaker 1>in TICK you figure out how to shrink stuff down further,

1:01:33.520 --> 1:01:36.640
<v Speaker 1>and talk you figure out how to rearrange these new

1:01:36.760 --> 1:01:40.240
<v Speaker 1>smaller components so that they work the best way you

1:01:40.320 --> 1:01:44.280
<v Speaker 1>possibly can make them. So in our example, we would

1:01:44.320 --> 1:01:48.200
<v Speaker 1>be looking at those thirty two nanometer components and figuring

1:01:48.200 --> 1:01:53.760
<v Speaker 1>out the right architecture to maximize their efficiency. And the TikTok.

1:01:54.000 --> 1:01:58.400
<v Speaker 1>Generations of a single family of processors are going to

1:01:58.440 --> 1:02:02.480
<v Speaker 1>have the same size opponents, They're just gonna have different configurations.

1:02:02.920 --> 1:02:05.400
<v Speaker 1>The TICK is going to be based on the previous generation.

1:02:05.840 --> 1:02:11.760
<v Speaker 1>The TALK is the new architecture to maximize the efficiency

1:02:11.880 --> 1:02:15.960
<v Speaker 1>of the new sized components. And then your next TICK

1:02:16.640 --> 1:02:19.400
<v Speaker 1>is going to be taking those thirty two nanometer components

1:02:19.440 --> 1:02:21.760
<v Speaker 1>and figuring out how to shrink them down even further,

1:02:22.360 --> 1:02:26.640
<v Speaker 1>but within the same general architecture as your previous generation.

1:02:27.080 --> 1:02:32.640
<v Speaker 1>Tick talk, tick talk. That was pretty much how Intel

1:02:32.760 --> 1:02:38.240
<v Speaker 1>ran things uh for quite a few generations of processors.

1:02:39.240 --> 1:02:43.360
<v Speaker 1>Now Intel follows a new strategy. It calls it the

1:02:43.480 --> 1:02:49.480
<v Speaker 1>process architecture Optimize pattern others will call this tick talk

1:02:49.560 --> 1:02:54.280
<v Speaker 1>talk because again, the first one is shrinking components down

1:02:54.320 --> 1:02:59.160
<v Speaker 1>to a new smaller size, the second means finding a

1:02:59.200 --> 1:03:03.520
<v Speaker 1>better arch at lecture for those sized components, and the

1:03:03.560 --> 1:03:07.520
<v Speaker 1>third one is refining that design even further, so you're

1:03:07.560 --> 1:03:12.400
<v Speaker 1>staying on the same size of components for three generations

1:03:12.600 --> 1:03:15.720
<v Speaker 1>in a row. UH. This means that you don't have

1:03:15.760 --> 1:03:17.440
<v Speaker 1>to spend so much time trying to figure out how

1:03:17.480 --> 1:03:20.000
<v Speaker 1>are you going to shrink things down even further as

1:03:20.040 --> 1:03:25.240
<v Speaker 1>you gradually get closer and closer to a fundamental physical limitation. UH.

1:03:25.280 --> 1:03:29.640
<v Speaker 1>That being where quantum physics comes in and doesn't play

1:03:29.760 --> 1:03:32.800
<v Speaker 1>nicely with your designs anymore, and you get things like

1:03:32.840 --> 1:03:39.120
<v Speaker 1>electron tunneling where electrons seem to leak through transistors, and

1:03:39.160 --> 1:03:43.080
<v Speaker 1>since transistors are meant to control the flow of electrons,

1:03:43.120 --> 1:03:46.000
<v Speaker 1>this is what we in the computer biz often call

1:03:46.640 --> 1:03:51.200
<v Speaker 1>a bad thing. It introduces the possibility of errors and miscalculations,

1:03:51.560 --> 1:03:55.960
<v Speaker 1>and you don't want that in your processor, so it

1:03:56.080 --> 1:03:59.680
<v Speaker 1>ends up extending the amount of time Intel spends on

1:04:00.560 --> 1:04:05.880
<v Speaker 1>a specific size of dye for their their chips, but

1:04:05.960 --> 1:04:10.560
<v Speaker 1>it also maximizes the efficiency of that while engineers continue

1:04:10.560 --> 1:04:15.280
<v Speaker 1>to work on the next breakthrough. One other thing I

1:04:15.280 --> 1:04:19.240
<v Speaker 1>need to touch on before I conclude is the concept

1:04:19.320 --> 1:04:23.320
<v Speaker 1>of multi core processors, because Intel story doing that as well.

1:04:24.280 --> 1:04:28.680
<v Speaker 1>Intel's work with parallel processing way back in the nineties

1:04:29.120 --> 1:04:33.920
<v Speaker 1>provided the basis for multi core processors. Multi core processors

1:04:33.920 --> 1:04:39.240
<v Speaker 1>can handle several computational problems simultaneously, which brings the clock

1:04:39.320 --> 1:04:41.760
<v Speaker 1>speeds to bear on the problems to solve them in

1:04:41.800 --> 1:04:45.520
<v Speaker 1>parallel rather than in sequence. So one core might be

1:04:45.560 --> 1:04:48.520
<v Speaker 1>working on one problem, another core could be working on

1:04:48.720 --> 1:04:51.520
<v Speaker 1>a separate problem, So dual core processors. You could do

1:04:51.600 --> 1:04:54.760
<v Speaker 1>two of these, quad core four and so on and

1:04:54.800 --> 1:04:57.720
<v Speaker 1>so forth. And there's also threading as well, you can

1:04:57.800 --> 1:05:04.080
<v Speaker 1>thread different copy stational problems. But ultimately the concept we

1:05:04.120 --> 1:05:06.760
<v Speaker 1>need to really focus on here is that idea of

1:05:06.800 --> 1:05:11.880
<v Speaker 1>parallel processing, because for certain types of computational problems, parallel

1:05:11.920 --> 1:05:17.120
<v Speaker 1>processing is much much faster than doing sequential processing where

1:05:17.160 --> 1:05:21.040
<v Speaker 1>you're just going down a list of instructions. Even if

1:05:21.080 --> 1:05:25.520
<v Speaker 1>you make a really really super fast CPU, if it's

1:05:25.520 --> 1:05:28.720
<v Speaker 1>tackling a very long list of instructions that could otherwise

1:05:28.720 --> 1:05:32.400
<v Speaker 1>be divided up, a multi core processor might be more

1:05:32.440 --> 1:05:38.440
<v Speaker 1>effective than a very fast single core CPU. I like

1:05:38.520 --> 1:05:41.160
<v Speaker 1>to use an analogy whenever I talk about this, and

1:05:41.280 --> 1:05:44.160
<v Speaker 1>long time listeners of tech stuff are probably familiar with

1:05:44.200 --> 1:05:46.680
<v Speaker 1>us because I've used it before, but I find it's

1:05:46.920 --> 1:05:50.240
<v Speaker 1>very helpful if you're trying to understand the difference between

1:05:50.480 --> 1:05:56.479
<v Speaker 1>a super fast CPU and a fast but not as

1:05:56.720 --> 1:06:01.680
<v Speaker 1>crazy fast multi core processor. So we're going to imagine

1:06:01.840 --> 1:06:08.680
<v Speaker 1>a math class and you've got essentially sixteen kids in

1:06:08.720 --> 1:06:12.280
<v Speaker 1>this math class, right, one of those kids is a

1:06:12.320 --> 1:06:16.600
<v Speaker 1>math genius. She's a prodigy. She's so smart she can

1:06:16.680 --> 1:06:20.080
<v Speaker 1>complete any problem in a fraction of the time of

1:06:20.120 --> 1:06:23.680
<v Speaker 1>any of her other classmates. Her classmates, by the way,

1:06:23.800 --> 1:06:27.680
<v Speaker 1>are smart. They're they're not They're not slower anything, they're

1:06:27.680 --> 1:06:32.040
<v Speaker 1>just not geniuses like she is. Now, on any given

1:06:32.240 --> 1:06:35.920
<v Speaker 1>singular problem, the genius is always going to solve it

1:06:36.000 --> 1:06:40.640
<v Speaker 1>faster than her her other classmates. They're just never going

1:06:40.680 --> 1:06:44.440
<v Speaker 1>to be as fast as she is for any one problem.

1:06:44.560 --> 1:06:47.880
<v Speaker 1>But imagine the teacher hands out the test, and the

1:06:47.920 --> 1:06:51.680
<v Speaker 1>test has fifteen problems on it, So there are fifteen

1:06:51.720 --> 1:06:55.640
<v Speaker 1>problems you have to solve, and they're sixteen kids in

1:06:55.640 --> 1:07:00.160
<v Speaker 1>the class, including the genius. The teacher gives the genius

1:07:00.200 --> 1:07:04.000
<v Speaker 1>a test that has all sixteen, all fifteen problems on it.

1:07:04.440 --> 1:07:07.440
<v Speaker 1>So she has to solve all fifteen of those problems

1:07:07.480 --> 1:07:10.160
<v Speaker 1>as quickly as she can. But he tells the other

1:07:10.280 --> 1:07:14.640
<v Speaker 1>fifteen students, you each will tackle one of these problems,

1:07:14.680 --> 1:07:18.200
<v Speaker 1>and he assigns them. Student one has problem one, Student

1:07:18.280 --> 1:07:21.000
<v Speaker 1>two has problem to, and so on all the way

1:07:21.040 --> 1:07:24.960
<v Speaker 1>down the fifteen problems, and they have their job is

1:07:25.000 --> 1:07:30.080
<v Speaker 1>to complete their problem, their one problem before the genius

1:07:30.120 --> 1:07:35.240
<v Speaker 1>can complete all fifteen problems. Well, this is sort of

1:07:35.240 --> 1:07:39.080
<v Speaker 1>what multi core processors are capable of doing. They divide

1:07:39.120 --> 1:07:43.600
<v Speaker 1>up problems into different parts, and collectively they can solve

1:07:43.680 --> 1:07:47.880
<v Speaker 1>that big problem faster than a really super fast processor

1:07:48.000 --> 1:07:51.920
<v Speaker 1>could nine times out of ten, ninety nine times out

1:07:51.920 --> 1:07:55.680
<v Speaker 1>of a hundred, nine times out of a thousand. Those

1:07:55.760 --> 1:07:59.240
<v Speaker 1>fifteen students are going to finish their individual problems before

1:07:59.280 --> 1:08:02.760
<v Speaker 1>the math genie can work through all fifteen on her test.

1:08:03.960 --> 1:08:05.800
<v Speaker 1>And you might say, well, that's not fair to like,

1:08:05.920 --> 1:08:08.120
<v Speaker 1>that's not the point. It's an analogy to explain how

1:08:08.200 --> 1:08:12.800
<v Speaker 1>multi core processors work from a kind of high level approach.

1:08:13.240 --> 1:08:15.760
<v Speaker 1>It gets a lot more technical than that, obviously, but

1:08:15.840 --> 1:08:20.240
<v Speaker 1>that's just to explain that for certain types of computational problems,

1:08:20.560 --> 1:08:24.280
<v Speaker 1>parallel processing is much more effective. Now, there are types

1:08:24.320 --> 1:08:28.600
<v Speaker 1>of computational problems that cannot be broken into parallel processing,

1:08:28.920 --> 1:08:33.280
<v Speaker 1>and for those a super fast CPU is still more

1:08:33.439 --> 1:08:35.320
<v Speaker 1>often than not going to be more effective than a

1:08:35.360 --> 1:08:38.920
<v Speaker 1>multi core processor. So it really just depends upon the application.

1:08:39.720 --> 1:08:43.040
<v Speaker 1>But more and more we're seeing parallel processing problems being

1:08:43.080 --> 1:08:47.799
<v Speaker 1>the type that computers tackle. Now, how long will Intel

1:08:47.840 --> 1:08:52.120
<v Speaker 1>and other microprocessor manufacturers be able to keep Moore's law alive?

1:08:52.520 --> 1:08:55.479
<v Speaker 1>Because people are constantly predicting the end to Moore's law

1:08:55.600 --> 1:08:59.360
<v Speaker 1>has happened numerous times throughout history. From the eighties on.

1:09:00.000 --> 1:09:01.960
<v Speaker 1>People will say, oh, Moore's law is coming to an

1:09:02.040 --> 1:09:04.960
<v Speaker 1>end because it's not physically possible for us to keep

1:09:05.040 --> 1:09:07.840
<v Speaker 1>up with it. But so far, engineers have been able

1:09:07.880 --> 1:09:12.200
<v Speaker 1>to stave that off, partly through innovative architectures that don't

1:09:12.200 --> 1:09:15.799
<v Speaker 1>necessarily increase the number of components by a factor of two,

1:09:16.040 --> 1:09:20.040
<v Speaker 1>but rather increase the output of the processor by a

1:09:20.040 --> 1:09:23.960
<v Speaker 1>factor of two every two years. So it requires some

1:09:24.040 --> 1:09:28.400
<v Speaker 1>reinterpretation of what Moore's law means. It may mean that

1:09:28.479 --> 1:09:31.480
<v Speaker 1>you fudge a bit on the amount of time necessary

1:09:31.520 --> 1:09:34.360
<v Speaker 1>to get to that factor of two. And it might

1:09:34.400 --> 1:09:40.240
<v Speaker 1>mean reinterpreting it as processing power versus number of discrete elements.

1:09:41.120 --> 1:09:44.160
<v Speaker 1>But I think the important thing for us as consumers

1:09:44.439 --> 1:09:48.799
<v Speaker 1>is the performance, not whether the chip actually has twice

1:09:48.800 --> 1:09:51.400
<v Speaker 1>as many transistors as the one from two years ago.

1:09:52.439 --> 1:09:57.520
<v Speaker 1>So that is still a battle that's going on today. Uh.

1:09:57.640 --> 1:10:01.479
<v Speaker 1>It does mean that maybe we'll hit that fundamental limit

1:10:01.640 --> 1:10:03.960
<v Speaker 1>at some point and we will not be able to

1:10:04.000 --> 1:10:09.040
<v Speaker 1>continue More's law using traditional microprocessor designs, and then we

1:10:09.120 --> 1:10:14.519
<v Speaker 1>may need another true revolution in computer processing to create

1:10:14.640 --> 1:10:19.480
<v Speaker 1>a new means of keeping up with that power output.

1:10:20.240 --> 1:10:23.960
<v Speaker 1>But maybe stepping outside of what a processor is supposed

1:10:24.000 --> 1:10:28.840
<v Speaker 1>to look like, that's a possibility today. Intel is doing

1:10:28.880 --> 1:10:31.920
<v Speaker 1>pretty well as of the recording of this podcast. When

1:10:31.960 --> 1:10:34.840
<v Speaker 1>I checked it was its shares were trading at around

1:10:34.840 --> 1:10:38.080
<v Speaker 1>thirty five dollars a share. That puts the market cap

1:10:38.160 --> 1:10:40.960
<v Speaker 1>value of Intel at about a hundred and sixty five

1:10:41.320 --> 1:10:46.479
<v Speaker 1>billion dollars. The company may nearly sixty billion in revenue

1:10:46.560 --> 1:10:49.680
<v Speaker 1>in twenty six, which is not too bad for a

1:10:49.720 --> 1:10:53.639
<v Speaker 1>company that was found by a couple of traders. Well done,

1:10:54.000 --> 1:10:59.840
<v Speaker 1>More and Noise. That wraps up our two part episode

1:11:00.000 --> 1:11:03.120
<v Speaker 1>on the story of Intel. Obviously, there's a lot more

1:11:03.120 --> 1:11:06.800
<v Speaker 1>I could talk about from the various sensors and processors

1:11:06.800 --> 1:11:10.000
<v Speaker 1>Intel has been developing for all sorts of applications to

1:11:10.120 --> 1:11:14.000
<v Speaker 1>their partnerships with various companies throughout its history, and maybe

1:11:14.000 --> 1:11:16.320
<v Speaker 1>in future episodes I'll touch on some of those, but

1:11:16.400 --> 1:11:18.240
<v Speaker 1>I thought that it was really important to just kind

1:11:18.240 --> 1:11:21.720
<v Speaker 1>of hit the high points to understand where Intel came

1:11:21.800 --> 1:11:24.720
<v Speaker 1>from and how it developed over its years. If you

1:11:24.720 --> 1:11:27.960
<v Speaker 1>guys have any suggestions for future episodes of Text Stuff,

1:11:28.200 --> 1:11:31.240
<v Speaker 1>whether it's a topic I should cover, someone I should

1:11:31.280 --> 1:11:34.639
<v Speaker 1>have on to interview, a guest co host who might

1:11:34.640 --> 1:11:37.840
<v Speaker 1>be able to tackle a specific subject with me, let

1:11:37.840 --> 1:11:41.160
<v Speaker 1>me know. Send me an email. The address for the

1:11:41.160 --> 1:11:45.560
<v Speaker 1>show is tech Stuff at how stuff works dot com,

1:11:45.680 --> 1:11:48.720
<v Speaker 1>or you can drop me a line on Twitter or Facebook.

1:11:48.840 --> 1:11:51.640
<v Speaker 1>The handle for both of those is text Stuff h

1:11:51.920 --> 1:11:55.400
<v Speaker 1>s W. Remember you can tune in on Wednesdays and

1:11:55.439 --> 1:12:00.000
<v Speaker 1>Friday's to see me stream this podcast live. You can

1:12:00.000 --> 1:12:03.400
<v Speaker 1>watch me record it live, which includes all the ridiculous

1:12:03.439 --> 1:12:06.200
<v Speaker 1>mistakes I make and when I have to restart, and

1:12:06.280 --> 1:12:08.920
<v Speaker 1>sometimes I'm chatting with the chat room and just answering

1:12:09.000 --> 1:12:12.240
<v Speaker 1>questions or shooting the breeze. Go to twitch dot tv

1:12:12.439 --> 1:12:15.439
<v Speaker 1>slash tech stuff. To see the schedule there and join

1:12:15.520 --> 1:12:19.280
<v Speaker 1>me sometime, won't you. And in the meantime, I hope

1:12:19.280 --> 1:12:21.519
<v Speaker 1>you guys have a great week and I'll talk to

1:12:21.520 --> 1:12:29.799
<v Speaker 1>you again really soon. For more on this and thousands

1:12:29.800 --> 1:12:41.880
<v Speaker 1>of other topics, is it staff works dot com.