WEBVTT - What are virtual machines?

0:00:00.320 --> 0:00:02.880
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.240 --> 0:00:08.880
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:08.960 --> 0:00:14.480
<v Speaker 1>tech Stuff from how stuff works dot com. Hello, everybody,

0:00:14.560 --> 0:00:16.920
<v Speaker 1>welcome to tech stuff. My name is Chris Palette. I'm

0:00:16.960 --> 0:00:19.279
<v Speaker 1>an editor here at how Stuff Works. Sitting next to

0:00:19.280 --> 0:00:22.240
<v Speaker 1>me as usual as senior writer Jonathan Strickland. Hey there,

0:00:22.840 --> 0:00:26.880
<v Speaker 1>and today we're going to talk about virtual machines. Yeah,

0:00:27.080 --> 0:00:29.920
<v Speaker 1>and this is a topic that, uh, that a lot

0:00:29.960 --> 0:00:31.880
<v Speaker 1>of people were kind of curious about. We've got a

0:00:31.880 --> 0:00:35.200
<v Speaker 1>couple of emails about virtual machines and exactly what are

0:00:35.240 --> 0:00:38.360
<v Speaker 1>they and why use them? Um? And it is kind

0:00:38.360 --> 0:00:41.040
<v Speaker 1>of confusing. You think of the word virtual, it means

0:00:41.120 --> 0:00:44.040
<v Speaker 1>it's it's not a physical thing. It just kind of

0:00:44.240 --> 0:00:47.839
<v Speaker 1>virtually exists. So how is that even possible? Well, it

0:00:47.840 --> 0:00:52.280
<v Speaker 1>all has to do with special software, which is fittingly

0:00:52.400 --> 0:00:58.560
<v Speaker 1>called virtualization software. Yeah, I'm guessing that this giant cardboard

0:00:58.640 --> 0:01:00.960
<v Speaker 1>box that I have painted how home and says that

0:01:01.000 --> 0:01:03.840
<v Speaker 1>it's a supercomputer, that's not that doesn't count as a

0:01:03.920 --> 0:01:07.240
<v Speaker 1>virtual machine in the classical sense. In the three year

0:01:07.280 --> 0:01:11.560
<v Speaker 1>old let's play pretend sense you you are aces. It

0:01:11.680 --> 0:01:15.399
<v Speaker 1>was cranking out billions of virtual pedophlops. I'm sure it was,

0:01:16.200 --> 0:01:21.440
<v Speaker 1>but for real quote unquote virtual machines. We're talking about

0:01:21.520 --> 0:01:27.200
<v Speaker 1>special software that essentially partitions of physical machines resources in

0:01:27.240 --> 0:01:30.760
<v Speaker 1>such a way that you can run multiple instances of

0:01:30.880 --> 0:01:34.640
<v Speaker 1>operating systems if you like, or applications that are completely

0:01:34.680 --> 0:01:38.200
<v Speaker 1>independent of one another. There's no there's no real risk

0:01:38.280 --> 0:01:41.880
<v Speaker 1>of them interfering with each other. And um, so you're

0:01:41.959 --> 0:01:45.880
<v Speaker 1>using one physical machine to run multiple instances of some

0:01:45.920 --> 0:01:51.080
<v Speaker 1>sort of application. Uh, that's that's the basic premise. Um,

0:01:51.120 --> 0:01:54.640
<v Speaker 1>why is this important? Well, it's because as the Web

0:01:54.720 --> 0:01:58.520
<v Speaker 1>has evolved, things have gotten really complicated. A lot of

0:01:58.800 --> 0:02:02.680
<v Speaker 1>websites run multi both services, and sometimes these services need

0:02:02.760 --> 0:02:06.560
<v Speaker 1>to use multiple applications. Um, well, it turns out that

0:02:06.640 --> 0:02:09.800
<v Speaker 1>some applications don't work well with others, and if you

0:02:09.880 --> 0:02:13.840
<v Speaker 1>try and run multiple applications on one server, you get crashes.

0:02:14.400 --> 0:02:17.880
<v Speaker 1>Right yeah, I mean so you don't want that to happen. Yeah.

0:02:18.480 --> 0:02:22.320
<v Speaker 1>You also might know this. In another word, you may

0:02:22.320 --> 0:02:27.120
<v Speaker 1>not have known what it was environment. Um, just imagine

0:02:27.160 --> 0:02:31.320
<v Speaker 1>it as a little you know, pretend world on a

0:02:31.919 --> 0:02:36.720
<v Speaker 1>on your web browser might be Java for instance, Right, Yeah,

0:02:36.720 --> 0:02:39.760
<v Speaker 1>that's a good example. Java is as a program pro

0:02:40.160 --> 0:02:48.480
<v Speaker 1>proglamming language. It could be it's very proglam um David, Yeah, exactly. UM.

0:02:48.520 --> 0:02:52.800
<v Speaker 1>That was created by son uh and uh. Basically, you

0:02:52.919 --> 0:02:55.320
<v Speaker 1>when you have Java installed on your computer and you

0:02:55.400 --> 0:02:59.919
<v Speaker 1>go to a, um a website that has Java plug

0:03:00.120 --> 0:03:02.760
<v Speaker 1>in on. It might be, for example, a gaming site.

0:03:02.840 --> 0:03:06.200
<v Speaker 1>You want to play a casual game on your your machine,

0:03:06.200 --> 0:03:07.280
<v Speaker 1>and you go to that thing. You know, all of

0:03:07.320 --> 0:03:09.480
<v Speaker 1>a sudden, you see this thing and it's loading inside

0:03:09.520 --> 0:03:11.360
<v Speaker 1>your window has a little box and it's you know,

0:03:11.720 --> 0:03:14.000
<v Speaker 1>it gives you You might see, especially with Java, the

0:03:14.040 --> 0:03:17.040
<v Speaker 1>orange Java window and it just you know, scrolls open

0:03:17.080 --> 0:03:19.000
<v Speaker 1>and then all of a sudden, whatever it is that

0:03:19.040 --> 0:03:22.200
<v Speaker 1>you're trying to do pops up. Well, that's Java running

0:03:22.200 --> 0:03:25.840
<v Speaker 1>on a virtual machine inside your browser window whatever. You know,

0:03:25.840 --> 0:03:28.760
<v Speaker 1>whether you're using Windows or Linux or or Mac. There

0:03:28.760 --> 0:03:32.320
<v Speaker 1>it is. You know, it's it's a machine inside a machine. Yeah.

0:03:32.400 --> 0:03:35.120
<v Speaker 1>And you might wonder, well, why would you even worry

0:03:35.120 --> 0:03:37.600
<v Speaker 1>about having a machine inside a machine in the first place. Well,

0:03:38.680 --> 0:03:42.360
<v Speaker 1>ideally you would have a single server for every single

0:03:42.400 --> 0:03:47.160
<v Speaker 1>application that you want to run in your service. UM.

0:03:47.200 --> 0:03:49.920
<v Speaker 1>That way you can make sure that one, no, two

0:03:49.960 --> 0:03:52.800
<v Speaker 1>applications are going to interfere with one another. You don't

0:03:52.800 --> 0:03:54.880
<v Speaker 1>have to worry about a server running two of them

0:03:54.960 --> 0:03:58.440
<v Speaker 1>at the same time. Um too, if there's a problem,

0:03:58.600 --> 0:04:01.000
<v Speaker 1>you can actually find out where the problem is very

0:04:01.080 --> 0:04:04.360
<v Speaker 1>quickly because if it's a specific application going down, you

0:04:04.400 --> 0:04:07.160
<v Speaker 1>know which server that belongs to, Like, well, this this

0:04:07.240 --> 0:04:10.400
<v Speaker 1>is the server that runs process A. If Process A

0:04:10.560 --> 0:04:14.120
<v Speaker 1>is going haywire, you know to go to that particular server.

0:04:15.040 --> 0:04:16.960
<v Speaker 1>But here's the problem is that if you've got tons

0:04:16.960 --> 0:04:19.480
<v Speaker 1>and tons and tons of applications, or you have a

0:04:19.520 --> 0:04:22.800
<v Speaker 1>really large operation like let's say I don't know Google,

0:04:23.320 --> 0:04:28.840
<v Speaker 1>that's a good example. Google has thousands of these servers. Well,

0:04:28.880 --> 0:04:33.040
<v Speaker 1>if you do a single server per application in an

0:04:33.400 --> 0:04:38.000
<v Speaker 1>environment like Google, then you would need even more space,

0:04:38.080 --> 0:04:41.320
<v Speaker 1>tons and tons of space and resources physical resources like

0:04:41.800 --> 0:04:44.560
<v Speaker 1>not just the storage facility, but you know, your power

0:04:44.720 --> 0:04:49.279
<v Speaker 1>consumption and uh and cooling systems, things that you need

0:04:49.320 --> 0:04:53.160
<v Speaker 1>to have in order to make servers run properly. Uh.

0:04:53.200 --> 0:04:55.520
<v Speaker 1>But if you were to, you know, look at most

0:04:55.560 --> 0:04:58.120
<v Speaker 1>of these servers running applications, you would notice that the

0:04:58.120 --> 0:05:01.520
<v Speaker 1>servers have become really really power a full, and most

0:05:01.560 --> 0:05:04.599
<v Speaker 1>of them are not running anywhere near capacity like a

0:05:04.640 --> 0:05:08.599
<v Speaker 1>single application takes up only a fraction of the servers

0:05:08.680 --> 0:05:12.160
<v Speaker 1>uh processing power, so you're not really using your physical

0:05:12.440 --> 0:05:15.760
<v Speaker 1>machines to the extent that you need to. The solution

0:05:15.839 --> 0:05:19.440
<v Speaker 1>is virtualization. If you can create a virtual partition within

0:05:19.520 --> 0:05:23.480
<v Speaker 1>that machine so that it can run two different operating systems,

0:05:23.520 --> 0:05:25.680
<v Speaker 1>or even two of the same operating system It doesn't

0:05:25.720 --> 0:05:28.000
<v Speaker 1>have to be different, um, but if it can run

0:05:28.040 --> 0:05:30.560
<v Speaker 1>two of these environments at the same time, you you

0:05:30.600 --> 0:05:34.880
<v Speaker 1>are maximizing that servers resource use. So that way you

0:05:34.920 --> 0:05:37.400
<v Speaker 1>don't have to worry about, Okay, well this servers only

0:05:37.480 --> 0:05:40.680
<v Speaker 1>running at twelve percent capacity. The other great thing about

0:05:40.720 --> 0:05:43.560
<v Speaker 1>it is that, well that means that suddenly you don't

0:05:43.600 --> 0:05:46.600
<v Speaker 1>need all this space anymore. You can run that that

0:05:46.680 --> 0:05:50.240
<v Speaker 1>operation with let's say a thousand servers instead of five

0:05:50.279 --> 0:05:53.240
<v Speaker 1>thousand servers. Now we are talking about huge numbers here,

0:05:53.279 --> 0:05:57.000
<v Speaker 1>but the same thing applies on smaller scales. So operations

0:05:57.040 --> 0:05:59.240
<v Speaker 1>that would only need five or six servers may only

0:05:59.240 --> 0:06:04.080
<v Speaker 1>need two or three. Now there that's the that's the

0:06:04.120 --> 0:06:07.920
<v Speaker 1>broad view of this. But there are some caveats to this. Yeah,

0:06:08.440 --> 0:06:12.839
<v Speaker 1>for instance, you shouldn't max out your server. No, that's

0:06:12.839 --> 0:06:15.240
<v Speaker 1>never a good thing. You're gonna overtax it and it's

0:06:15.240 --> 0:06:18.760
<v Speaker 1>going to make it work even less reliably. Right yeah

0:06:18.760 --> 0:06:23.040
<v Speaker 1>so you so, while it's possible to maybe create multiple

0:06:23.560 --> 0:06:27.000
<v Speaker 1>virtual servers or virtual machines even on a PC, this

0:06:27.080 --> 0:06:28.919
<v Speaker 1>is not just for servers. You can do it with

0:06:29.040 --> 0:06:32.640
<v Speaker 1>PCs two. Um, even though you could do multiple ones,

0:06:32.640 --> 0:06:34.640
<v Speaker 1>you have to remember every single time you do this,

0:06:34.920 --> 0:06:39.440
<v Speaker 1>you're partitioning off part of that computer's resources. So the

0:06:39.480 --> 0:06:42.320
<v Speaker 1>computer as a whole has less you know, each each

0:06:42.360 --> 0:06:46.760
<v Speaker 1>individual instance has has only a fraction of the main

0:06:46.800 --> 0:06:51.359
<v Speaker 1>computers resources. Eventually get to a point where you know

0:06:51.400 --> 0:06:53.480
<v Speaker 1>you have the diminishing law of returns. You know you're

0:06:53.480 --> 0:06:57.119
<v Speaker 1>not or law of diminishing returns, I should say, you don't. Uh,

0:06:57.320 --> 0:07:01.760
<v Speaker 1>you don't get enough output to justified partitioning up the

0:07:01.760 --> 0:07:06.159
<v Speaker 1>server anymore than you already have. Right and um, you

0:07:06.200 --> 0:07:09.880
<v Speaker 1>know that that also applies to desktop computers as well.

0:07:09.920 --> 0:07:11.640
<v Speaker 1>I mean you can you can set up your your

0:07:11.640 --> 0:07:15.000
<v Speaker 1>desktop computer to uh well, depending on what model you have,

0:07:15.520 --> 0:07:18.760
<v Speaker 1>UM to run more than one operating system or multiple

0:07:18.800 --> 0:07:22.520
<v Speaker 1>instances of an operating system. UM. You know, Mac users,

0:07:22.640 --> 0:07:26.240
<v Speaker 1>especially the Intel Mac users, are very familiar with this now,

0:07:26.280 --> 0:07:28.560
<v Speaker 1>or at least a lot of them are because um,

0:07:28.600 --> 0:07:31.920
<v Speaker 1>the Intel Max can run different operating systems, and just

0:07:32.000 --> 0:07:34.280
<v Speaker 1>the mac os that can also run Windows and they

0:07:34.280 --> 0:07:37.160
<v Speaker 1>can run Linux. UM, if you are so inclined, you

0:07:37.240 --> 0:07:40.600
<v Speaker 1>can uh install all three operating systems. Of course, you

0:07:40.600 --> 0:07:42.320
<v Speaker 1>have to partition to hard drive. Was you know what

0:07:42.400 --> 0:07:45.040
<v Speaker 1>Jonathan was saying before. You have to make a separate

0:07:45.040 --> 0:07:47.560
<v Speaker 1>section for each of those. And if you're running software

0:07:47.600 --> 0:07:53.160
<v Speaker 1>like UM against Son's Virtual Box or vm Ware's Fusion

0:07:53.640 --> 0:07:57.640
<v Speaker 1>or Parallels desktop, you can actually access those other operating

0:07:57.680 --> 0:08:01.200
<v Speaker 1>systems at the same time in a virtual environment right

0:08:01.240 --> 0:08:02.960
<v Speaker 1>there on the desktop, and you can you can use

0:08:02.960 --> 0:08:04.560
<v Speaker 1>them at the same time. Now, of course they're all

0:08:04.640 --> 0:08:09.400
<v Speaker 1>using again Jonathan said, the same processor at the same time,

0:08:09.440 --> 0:08:12.320
<v Speaker 1>and after a while it's going to overtax things. But um,

0:08:12.360 --> 0:08:13.960
<v Speaker 1>it is possible to do and you can do this

0:08:14.000 --> 0:08:17.320
<v Speaker 1>on a on a regular Windows box to m vm

0:08:17.360 --> 0:08:21.040
<v Speaker 1>Ware also makes a workstation which I believe allows you

0:08:21.080 --> 0:08:25.480
<v Speaker 1>to run different environments at the same time as well. Sure,

0:08:25.560 --> 0:08:28.720
<v Speaker 1>and there are even businesses that have made an entire

0:08:28.760 --> 0:08:31.800
<v Speaker 1>business model out of this. There's one called in Computing

0:08:31.840 --> 0:08:35.760
<v Speaker 1>in as a name. UM. I went to the Consumer

0:08:35.760 --> 0:08:38.320
<v Speaker 1>Electronics Show this last year two thousand nine, and I

0:08:38.440 --> 0:08:42.800
<v Speaker 1>met with the president of in Computing and it was

0:08:42.840 --> 0:08:45.400
<v Speaker 1>a fascinating tour of the booth. It was one of

0:08:45.400 --> 0:08:47.640
<v Speaker 1>those very small booths all the way, something I probably

0:08:47.640 --> 0:08:49.720
<v Speaker 1>never would have seen. But I received an email and

0:08:49.720 --> 0:08:51.719
<v Speaker 1>I thought, this sounds really interesting. I'm going to take

0:08:51.760 --> 0:08:53.760
<v Speaker 1>some time and go to this, and I'm really glad

0:08:53.800 --> 0:08:57.280
<v Speaker 1>I did. Now in Computing what they've done is they've

0:08:57.280 --> 0:09:00.640
<v Speaker 1>found a system where you can partition up a regular

0:09:00.679 --> 0:09:04.360
<v Speaker 1>PC so that you can create multiple workstations that all

0:09:04.400 --> 0:09:07.800
<v Speaker 1>share that one PCs resources. It's just like the old

0:09:07.920 --> 0:09:12.800
<v Speaker 1>time sharing model on supercomputers. You have to sit there

0:09:12.840 --> 0:09:15.480
<v Speaker 1>and listen to a long winded sales pitch and you know,

0:09:15.520 --> 0:09:19.160
<v Speaker 1>maybe you'll get a free car. I didn't, but then

0:09:19.200 --> 0:09:22.520
<v Speaker 1>I'm pressed, so um no, no, it was. It was

0:09:22.559 --> 0:09:26.640
<v Speaker 1>really a great UH booth tour. But time sharing, for

0:09:26.640 --> 0:09:28.679
<v Speaker 1>those of you who are wondering, that was a system

0:09:28.720 --> 0:09:31.320
<v Speaker 1>where you had a supercomputer. It was a centralized computer,

0:09:31.360 --> 0:09:33.240
<v Speaker 1>and then you had a bunch of dumb terminals, which

0:09:33.280 --> 0:09:36.319
<v Speaker 1>means the terminals didn't have any real native processing power.

0:09:36.880 --> 0:09:39.960
<v Speaker 1>It was just an access point for the user to

0:09:40.440 --> 0:09:43.319
<v Speaker 1>get access to the processing power that was in the supercomputer,

0:09:43.920 --> 0:09:45.800
<v Speaker 1>so you could have multiple people working on this at

0:09:45.800 --> 0:09:48.320
<v Speaker 1>the same time. Now with the supercomputer was a little different.

0:09:48.320 --> 0:09:50.600
<v Speaker 1>It wasn't all partitioned. It was that the computer would

0:09:50.600 --> 0:09:56.800
<v Speaker 1>handle each task separately in time in sequence. So let's

0:09:56.800 --> 0:10:00.199
<v Speaker 1>say Johnny says I need this information, and then he

0:10:00.280 --> 0:10:03.240
<v Speaker 1>says I need this information, while the supercomputer would answer

0:10:03.360 --> 0:10:06.319
<v Speaker 1>Johnny's first and then Susie's. But it was so fast

0:10:06.360 --> 0:10:08.360
<v Speaker 1>that it seemed like it was instantaneous, like it was

0:10:08.400 --> 0:10:12.160
<v Speaker 1>all simultaneously happening at you know, So it seemed like

0:10:12.200 --> 0:10:14.160
<v Speaker 1>the same sort of thing. Now, what in computing does

0:10:14.280 --> 0:10:18.320
<v Speaker 1>is it? It partitions up PCs um and depending on

0:10:18.360 --> 0:10:21.800
<v Speaker 1>which series you have, Like if you have the X series,

0:10:22.200 --> 0:10:24.080
<v Speaker 1>I think it's the five fifty, I think up to

0:10:24.200 --> 0:10:27.320
<v Speaker 1>eleven users can be using the same PC at the

0:10:27.360 --> 0:10:31.160
<v Speaker 1>same time. Now each person has their own monitor, keyboard, mouse,

0:10:31.240 --> 0:10:33.240
<v Speaker 1>that kind of thing. But they attached to a little

0:10:33.280 --> 0:10:37.480
<v Speaker 1>module which in turn attaches to the mother PC. And

0:10:37.520 --> 0:10:41.400
<v Speaker 1>then if you were to get them the L series,

0:10:41.800 --> 0:10:43.640
<v Speaker 1>did I say that? Ll serious? That was the X series.

0:10:43.800 --> 0:10:46.800
<v Speaker 1>The L series is up to thirty users on one

0:10:46.840 --> 0:10:49.920
<v Speaker 1>PC and it runs through Ethernet chords. You you connect

0:10:50.280 --> 0:10:53.719
<v Speaker 1>Ethernet cable to the little module which you know, your

0:10:53.760 --> 0:10:56.240
<v Speaker 1>monitor and your keyboard plug into, connect that to the

0:10:56.240 --> 0:11:00.040
<v Speaker 1>host PC. So in computing's ideas, well, this is a

0:11:00.080 --> 0:11:04.240
<v Speaker 1>good way to uh to bring computers into schools in

0:11:04.800 --> 0:11:08.720
<v Speaker 1>like developing nations where they can't necessarily afford a computer

0:11:08.800 --> 0:11:12.400
<v Speaker 1>for every student, but they can afford one decent computer

0:11:12.559 --> 0:11:15.040
<v Speaker 1>and then this system which will allow up to thirty

0:11:15.040 --> 0:11:18.800
<v Speaker 1>people to access that computer's resources. Um. Now, of course

0:11:18.800 --> 0:11:21.840
<v Speaker 1>it can only run applications that aren't going to over

0:11:21.920 --> 0:11:23.760
<v Speaker 1>tax that computer. You're not gonna see a lot of

0:11:23.760 --> 0:11:29.599
<v Speaker 1>call of duty being played on these terminals. But word processors, spreadsheets,

0:11:29.679 --> 0:11:33.760
<v Speaker 1>that's gonna that's easy. So it's it sounds like between

0:11:34.520 --> 0:11:38.720
<v Speaker 1>you know, virtualization and cloud computing that we're we're we

0:11:38.760 --> 0:11:42.040
<v Speaker 1>may be headed into a world where um, there is

0:11:42.120 --> 0:11:46.960
<v Speaker 1>centralized processing power and centralized applications and people are just

0:11:47.040 --> 0:11:51.040
<v Speaker 1>using uh, dumber and dumber terminals and you know, things

0:11:51.080 --> 0:11:55.960
<v Speaker 1>like netbooks that have slower processors and less RAM and

0:11:56.080 --> 0:11:59.840
<v Speaker 1>basically trusting the the cloud to handle all the application

0:12:00.080 --> 0:12:03.200
<v Speaker 1>than all the heavy lifting. Yeah, do you do you

0:12:03.200 --> 0:12:05.600
<v Speaker 1>really think that that's the way it's all going to go?

0:12:05.840 --> 0:12:08.040
<v Speaker 1>Or I mean, is this just sort of an application

0:12:08.040 --> 0:12:13.079
<v Speaker 1>per application used like the the Third World education? Momow,

0:12:13.160 --> 0:12:15.520
<v Speaker 1>what a great question. It really turned it around on

0:12:15.559 --> 0:12:18.600
<v Speaker 1>either pullet. But no, I have an answer for this. Okay,

0:12:18.640 --> 0:12:20.480
<v Speaker 1>this is one of my favorite topics to talk about,

0:12:20.520 --> 0:12:23.200
<v Speaker 1>so of course I have an answer for this. Um. Now,

0:12:23.600 --> 0:12:26.040
<v Speaker 1>of course, this this is my own personal opinion about

0:12:26.080 --> 0:12:30.319
<v Speaker 1>about how things are going. I think the economic downturn

0:12:31.080 --> 0:12:34.120
<v Speaker 1>was the best thing that could happen to netbooks because

0:12:34.280 --> 0:12:37.640
<v Speaker 1>it meant that consumers were looking at computers and they

0:12:37.640 --> 0:12:39.160
<v Speaker 1>were saying, well, you know, I still need to get

0:12:39.160 --> 0:12:41.240
<v Speaker 1>a computer for my my son or my daughter who's

0:12:41.280 --> 0:12:44.280
<v Speaker 1>going off to college, or I really need a new computer,

0:12:44.440 --> 0:12:46.920
<v Speaker 1>but I can't afford to buy the latest and greatest.

0:12:46.920 --> 0:12:50.760
<v Speaker 1>And yeah, that new I seven processor looks amazing, but

0:12:51.080 --> 0:12:53.559
<v Speaker 1>I just can't afford that kind of computer, or or

0:12:53.600 --> 0:12:58.080
<v Speaker 1>that new Mac that's thirty three hundred dollars. Did you

0:12:58.120 --> 0:13:02.199
<v Speaker 1>see that that came out today and with it yeah

0:13:02.800 --> 0:13:06.839
<v Speaker 1>z on um, Yeah, the Mac Pro. Not everyone can

0:13:06.880 --> 0:13:10.720
<v Speaker 1>spend that much, so they're looking at other options. Now.

0:13:10.840 --> 0:13:13.560
<v Speaker 1>I think if the consumer realizes that the netbooks do

0:13:13.640 --> 0:13:16.720
<v Speaker 1>not have this native processing ability and that they will

0:13:16.880 --> 0:13:19.719
<v Speaker 1>really need to rely upon the cloud to get that

0:13:19.800 --> 0:13:22.360
<v Speaker 1>kind of processing done. If they realize that and they're

0:13:22.360 --> 0:13:24.720
<v Speaker 1>okay with that, Yeah, I think this is the future.

0:13:24.880 --> 0:13:28.240
<v Speaker 1>I think that mass market in general will move to

0:13:28.440 --> 0:13:33.640
<v Speaker 1>netbooks and what we would traditionally call underpowered PCs. UM,

0:13:33.679 --> 0:13:36.280
<v Speaker 1>you will still have niche markets that will not move

0:13:36.360 --> 0:13:40.720
<v Speaker 1>to that. UM. For instance, anyone who's doing massive media editing,

0:13:40.960 --> 0:13:43.559
<v Speaker 1>they can't do that. You can't really poured everything off

0:13:43.559 --> 0:13:46.800
<v Speaker 1>to the cloud. UM. Same thing with gamers. I mean,

0:13:46.840 --> 0:13:50.760
<v Speaker 1>gamers are gonna need to have that super fast processor

0:13:50.880 --> 0:13:54.240
<v Speaker 1>and that the huge hard drive and all of the

0:13:54.240 --> 0:13:57.480
<v Speaker 1>bells and whistles. So that's still going to be there. UM.

0:13:57.520 --> 0:14:00.600
<v Speaker 1>The question is if those markets are large enough to

0:14:00.800 --> 0:14:04.640
<v Speaker 1>keep that development process going at full speed. That question,

0:14:05.160 --> 0:14:07.480
<v Speaker 1>I don't know the answer to that. We're gonna have

0:14:07.520 --> 0:14:10.559
<v Speaker 1>to see. I'm actually kind of worried about that because

0:14:10.559 --> 0:14:14.120
<v Speaker 1>it may mean that we that War's Law suddenly doesn't

0:14:14.120 --> 0:14:18.160
<v Speaker 1>apply because the the incentive to always be developing at

0:14:18.200 --> 0:14:22.200
<v Speaker 1>the fastest space possible is gonna possibly go away, right right,

0:14:22.600 --> 0:14:24.520
<v Speaker 1>But you know it'll all be virtual at that point,

0:14:24.560 --> 0:14:27.640
<v Speaker 1>so yeah, so who will you know? And there's there's

0:14:27.680 --> 0:14:29.600
<v Speaker 1>actually a good point there. I mean, you're kind of

0:14:29.640 --> 0:14:32.360
<v Speaker 1>smirking at me and making a joke, but that's that's

0:14:32.400 --> 0:14:34.440
<v Speaker 1>a good No, It really is a good point because

0:14:34.440 --> 0:14:37.480
<v Speaker 1>when you think about it, these servers that are running

0:14:37.480 --> 0:14:40.200
<v Speaker 1>all the processes, they still have to be fast. So

0:14:40.240 --> 0:14:42.960
<v Speaker 1>there's still a market for fast processors. It's just that

0:14:42.960 --> 0:14:45.280
<v Speaker 1>that market may switch to the business end, not to

0:14:45.360 --> 0:14:48.120
<v Speaker 1>the consumer end. You know, it's possible too that that

0:14:48.200 --> 0:14:48.320
<v Speaker 1>may