WEBVTT - TechStuff Looks at Chrome OS 0:00:00.280 --> 0:00:02.840 Brought to you by the reinvented two thousand twelve camera. 0:00:03.160 --> 0:00:08.920 It's ready. Are you get in touch with technology? With 0:00:09.039 --> 0:00:17.920 tech Stuff from how stuff works dot com. Hello again, everyone, 0:00:17.960 --> 0:00:21.000 Welcome to tech stuff. My name is Chris Pollette. I 0:00:21.040 --> 0:00:24.360 am an editor at how stuff works dot com. Sitting 0:00:24.360 --> 0:00:26.680 across from me as a guy who knows a whole 0:00:26.720 --> 0:00:29.960 lot about tech stuff, that would be senior writer Jonathan Strickland. 0:00:30.120 --> 0:00:34.760 Throughout human history, we've been dependent on machines to survive fate, 0:00:35.040 --> 0:00:39.920 it seems, is not without a sense of irony. Very nice, 0:00:40.000 --> 0:00:46.560 thank you. Okay, So today's topic is an interesting topic, actually, yes, 0:00:47.120 --> 0:00:49.280 because it's so close to so many things and yet 0:00:49.840 --> 0:00:53.479 it's not the same as any one of them. Well, 0:00:53.760 --> 0:00:58.280 I think that came from a Beatles song. No, No, 0:00:58.440 --> 0:01:03.960 it's a it's chromo, yes, And it has ties to 0:01:04.080 --> 0:01:07.600 a great many different other technologies and is sort of 0:01:07.600 --> 0:01:09.640 a standalone thing. And I think that's why so many 0:01:09.680 --> 0:01:13.040 people are confused about it, because it seems like a 0:01:13.080 --> 0:01:15.319 whole bunch of different stuff, but it is its own 0:01:15.360 --> 0:01:19.880 standalone operating system for computers. Yeah, this is um There 0:01:19.880 --> 0:01:22.160 are a lot of reasons why this is a confusing topic. 0:01:22.240 --> 0:01:24.640 For some people. Now, a lot of our listeners have 0:01:24.680 --> 0:01:27.320 probably been following the development of CHROMOS over the last 0:01:27.520 --> 0:01:31.480 uh well more than a year now, because Google initially 0:01:31.520 --> 0:01:35.440 announced CHROMOS back in two thousand nine. Yes, July seven, 0:01:35.600 --> 0:01:38.800 two thousand nine, by my reckoning, Yes, that is that's 0:01:38.840 --> 0:01:41.080 the date I have on this blog post where they 0:01:41.240 --> 0:01:46.080 called it. That was titled introducing the Google Chromos uh 0:01:46.440 --> 0:01:49.520 So Yeah, Google announced this back in two thousand nine, 0:01:50.080 --> 0:01:53.840 and then essentially the message was that this was going 0:01:53.880 --> 0:01:57.520 to be a cloud based operating system, it was meant 0:01:57.640 --> 0:02:02.760 for computers, and that we would start seeing it on 0:02:03.040 --> 0:02:06.960 machines and around the end of Yes, now as we 0:02:07.000 --> 0:02:09.680 record this, it is the very end of and indeed 0:02:09.720 --> 0:02:14.560 we have seen the first computer with this up ring 0:02:14.600 --> 0:02:19.400 system uh loaded in as its native OS. But the 0:02:19.440 --> 0:02:22.880 program itself is still very much in beta mode, which 0:02:23.120 --> 0:02:26.640 to Google, you know, kind of part for the course. Really, 0:02:27.480 --> 0:02:33.120 Google is king of the beta. Yeah, and um, I 0:02:33.120 --> 0:02:36.400 think it's safe to say, um that I still only 0:02:36.800 --> 0:02:40.280 speaking for myself personally, I think there there is uh 0:02:40.320 --> 0:02:43.000 there are some details out there about what chrome os 0:02:43.240 --> 0:02:46.320 is supposed to be, and I think they're pretty accurate 0:02:46.400 --> 0:02:49.520 based on the bets that they've released, but I'm not 0:02:49.560 --> 0:02:52.760 sure that we know all the details enough to be 0:02:52.840 --> 0:02:56.400 definitive about some parts of it. Like, um, I think 0:02:56.440 --> 0:02:58.760 I think a lot of the information that's out there 0:02:59.160 --> 0:03:05.080 still is more marketing material than it is hardened fast numbers. Right. 0:03:05.120 --> 0:03:06.960 And there are people out there right now who are 0:03:07.080 --> 0:03:10.960 using Chromos because as probably the pilot program Google shipped 0:03:11.000 --> 0:03:16.400 out um, they shipped out notebooks, computer notebooks. Uh. The 0:03:16.400 --> 0:03:20.440 the technical name for it is the cr DASH for 0:03:20.720 --> 0:03:24.760 eight UM. And so there are people who applied to 0:03:24.840 --> 0:03:28.120 be in this pilot program and Google sent some of 0:03:28.160 --> 0:03:32.280 them these machines with the intent. You know, they specifically said, 0:03:32.400 --> 0:03:35.640 use these machines as your primary machine. That's the only 0:03:35.680 --> 0:03:37.560 reason we're sending this to you, so that you can 0:03:37.600 --> 0:03:39.920 really give it a test and we can see make 0:03:39.920 --> 0:03:41.720 sure we iron bugs out and that kind of thing. 0:03:42.240 --> 0:03:43.800 So it doesn't do them any good if you just 0:03:43.920 --> 0:03:47.240 you know, use that like once in a while. So 0:03:47.320 --> 0:03:50.520 they wanted testers who could use it as their primary 0:03:50.560 --> 0:03:55.600 machine as much as possible. Um, it's interesting, it's actually Chromos. 0:03:55.720 --> 0:03:57.600 You might hear people talk about how Google it takes 0:03:57.640 --> 0:04:01.680 us sort of open approach too. They're operating systems. Chromo 0:04:01.800 --> 0:04:05.800 S technically is not really an open system. It's based 0:04:05.880 --> 0:04:11.720 upon source code from chromium OS, which is the open system. Yes. 0:04:11.800 --> 0:04:16.440 That actually reminds me of macOS ten, which is based 0:04:16.520 --> 0:04:20.680 upon b s D, but which is an open source system. 0:04:20.720 --> 0:04:24.599 But again macOS ten itself is closed. I mean it's 0:04:24.720 --> 0:04:28.080 it's Apple. You kind of expect that from Apple, but um, yeah, 0:04:28.120 --> 0:04:32.520 it's it's basically a derivative of that is a derivative 0:04:32.560 --> 0:04:34.880 of BSD, or it builds on bs D and is 0:04:34.920 --> 0:04:37.479 its own operating system. And that's similar to what the 0:04:37.720 --> 0:04:43.039 CHROMOS is. Yeah. Um, also it's uh, it's related to Linux. Yes, 0:04:43.080 --> 0:04:47.560 the Chromium o S is UM and uh it's important 0:04:47.600 --> 0:04:50.159 to note too that it is not Android, which is 0:04:50.200 --> 0:04:54.920 Google's operating system for global devices. Yeah. This this is 0:04:55.000 --> 0:04:59.039 another point that becomes really confusing for people who aren't 0:04:59.080 --> 0:05:02.520 really following the store, because you've got the Android platform, 0:05:02.560 --> 0:05:05.440 which is just now really starting to get some some 0:05:05.680 --> 0:05:08.800 identity in the market. Right there are people who know 0:05:08.880 --> 0:05:12.159 what Android is, um, because of all the different commercials 0:05:12.160 --> 0:05:15.520 for various phones as well as the tablet devices like 0:05:15.720 --> 0:05:19.640 the Galaxy Tab. So people know what Android is and 0:05:19.839 --> 0:05:22.560 they think of that as the Google operating system. So 0:05:22.720 --> 0:05:25.600 why would Google come out with the Chrome operating system. 0:05:25.680 --> 0:05:27.760 I've I've actually heard will have tech tournal lests say 0:05:27.800 --> 0:05:30.320 that this is a bad idea to come out with 0:05:30.400 --> 0:05:33.719 a separate operating system just for notebook computers. What I 0:05:33.720 --> 0:05:36.840 think is funny is that that's what other companies are 0:05:36.880 --> 0:05:39.640 doing already. Yes, I guess what they're saying is they 0:05:39.640 --> 0:05:43.080 thought that maybe the era of separate operating systems is 0:05:43.279 --> 0:05:45.039 slowly coming to an end, and we are going to 0:05:45.080 --> 0:05:50.160 see a get ready for you, guys, convergence emerge where 0:05:50.200 --> 0:05:52.880 we see the same operating system used across an entire 0:05:52.960 --> 0:05:56.240 variety of gadgets, from computers all the way down to 0:05:56.480 --> 0:06:00.479 cell phones. Yes, we're not there yet. So perhaps what 0:06:00.520 --> 0:06:03.840 people thought was that Google would just lead the way 0:06:04.160 --> 0:06:07.400 and create an operating system that would go across this 0:06:07.560 --> 0:06:11.159 entire range of hardware, and that way you didn't have 0:06:11.200 --> 0:06:13.840 to wait for things to converge. Google would just kind 0:06:13.839 --> 0:06:16.480 of lead the way. That would like like some generation 0:06:16.520 --> 0:06:18.839 of Android, maybe two or three generations down the line, 0:06:19.400 --> 0:06:22.159 would be robust enough to be a cloud based operating 0:06:22.200 --> 0:06:26.640 system for a computer. That's not what's happened, and Google 0:06:26.680 --> 0:06:29.440 has essentially said the same thing that other companies have said, 0:06:29.480 --> 0:06:33.440 which is that mobile devices and computers are two separate 0:06:33.480 --> 0:06:37.440 things right now, and while we may be heading towards convergence, 0:06:37.480 --> 0:06:40.680 we're not there yet. So it's it's weird for me 0:06:40.720 --> 0:06:43.800 to hear people criticize Google for making this decision when 0:06:43.839 --> 0:06:46.479 other companies have been doing this. I mean, you brought 0:06:46.560 --> 0:06:50.160 up Apple. Apple has the Mac os that's for their 0:06:50.200 --> 0:06:53.560 computer systems, then it has iOS, which is for their 0:06:54.120 --> 0:06:58.160 mobile systems, which includes the iPad, And of course Microsoft 0:06:58.279 --> 0:07:03.040 has Windows seven, Windows Mobile seven, which I'm sorry, I'm sorry, 0:07:03.080 --> 0:07:05.520 You're right, well, it was at one point Windows Mobile 0:07:05.520 --> 0:07:07.239 I think I think they only got up to six 0:07:07.279 --> 0:07:09.560 for Windows Mobile, Yes, but then they went to Windows 0:07:09.600 --> 0:07:12.360 Phone seven, so I'm sorry, Yes, Windows Phone seven, which 0:07:12.560 --> 0:07:16.720 again the seven makes it confusing to some people because 0:07:17.320 --> 0:07:20.040 you know, people are thinking, you know, Windows seven, I 0:07:20.080 --> 0:07:23.400 know what that is, but Windows Phone seven is different. Now, 0:07:24.160 --> 0:07:26.200 I would say that all three of them have done 0:07:26.200 --> 0:07:29.400 a pretty good job making their mobile operating system in 0:07:29.440 --> 0:07:33.520 their computer operating system look pretty similar. I should say 0:07:33.520 --> 0:07:36.720 that the Chromos I haven't really seen, but the Chromos 0:07:36.840 --> 0:07:41.400 does use the Chrome web browser that is out for Windows, 0:07:41.440 --> 0:07:45.119 Mac and Linux um as it's one of its major 0:07:45.200 --> 0:07:47.600 underpinnings because so much of what you do with the 0:07:47.680 --> 0:07:50.760 chromos or will do with the chromos, is done and 0:07:50.800 --> 0:07:54.640 the cloud, and we should probably talk about Yeah. So 0:07:54.720 --> 0:07:57.360 the idea here is it's actually a pretty simple one, 0:07:57.400 --> 0:08:00.920 and we've talked about it in the past about cloud computing. Chromos. 0:08:01.280 --> 0:08:05.120 Chromos is a specific approach to cloud computing. The idea 0:08:05.160 --> 0:08:09.280 here is that your computer would be a very thin client. 0:08:09.440 --> 0:08:12.400 It would not need to be particularly powerful in any way, 0:08:13.080 --> 0:08:15.080 because all it would really need to do is run 0:08:15.120 --> 0:08:18.200 this operating system, and then the applications would really just 0:08:18.280 --> 0:08:22.880 be kind of links to online services. So let's say 0:08:22.880 --> 0:08:25.040 that you want to use a word processing program. You 0:08:25.040 --> 0:08:28.320 could use something like Google Docs, where the you know, 0:08:28.440 --> 0:08:31.920 you, you you have an interface that you use on your computer, 0:08:32.360 --> 0:08:36.280 but the documents, the word processing, the actual the actual 0:08:36.360 --> 0:08:42.240 program exists on another computer a server. Um technically actually will. 0:08:42.600 --> 0:08:46.679 It will exist on several because of redundancy issues. Redundancy 0:08:46.760 --> 0:08:49.400 is very important in cloud computing because, of course, if 0:08:49.480 --> 0:08:53.400 one server goes down and there's no redundancy, you've just 0:08:53.520 --> 0:08:57.320 lost lots of customer data and customers don't tend to 0:08:57.360 --> 0:09:00.000 like that very much. No, not really. They seem to 0:09:00.080 --> 0:09:04.160 be um down on the whole. You just lost all 0:09:04.160 --> 0:09:07.520 my stuff, you know. Angle They don't like that. So 0:09:07.720 --> 0:09:11.400 the idea here is that you would have these applications 0:09:12.000 --> 0:09:14.520 that you would really just have kind of a window 0:09:14.640 --> 0:09:17.080 to those by you know, clicking on a little icon 0:09:17.480 --> 0:09:19.480 and it would open up the interface, but the application 0:09:19.520 --> 0:09:22.200 itself and all the data there and would exist on 0:09:22.640 --> 0:09:28.160 other machines. And there's some kind of great applications for 0:09:28.240 --> 0:09:31.120 this because that means that you aren't tied to a 0:09:31.120 --> 0:09:35.520 specific machine. Your information would all be tied to your account, 0:09:35.720 --> 0:09:39.720 your Google account in this case. So theoretically you could 0:09:40.000 --> 0:09:43.280 go to any other device that's running the Chrome os, 0:09:43.920 --> 0:09:47.959 log in as yourself using your Google profile, and then 0:09:48.000 --> 0:09:51.560 have access to all your information, and then when you 0:09:51.640 --> 0:09:54.760 logged out, you wouldn't have to worry about that information 0:09:54.840 --> 0:09:57.120 sticking around the computer because it's not living in that 0:09:57.160 --> 0:10:03.840 computer anyway. It's living on computer potentially thousands of miles away. Yeah, 0:10:03.840 --> 0:10:07.560 there's one of the reasons Google is doing this, at 0:10:07.600 --> 0:10:11.280 least according to uh the Google Chromos website, which I 0:10:11.320 --> 0:10:14.120 would encourage you to to go to it's it's Um. 0:10:14.120 --> 0:10:17.440 They do a lot of explaining in very simple terms. Uh, 0:10:17.480 --> 0:10:19.760 you know for the non techie related person, which is 0:10:19.760 --> 0:10:21.920 good because you know that pretty much describes me in 0:10:21.960 --> 0:10:26.640 some ways. Um. You know it's it's very user friendly 0:10:27.520 --> 0:10:32.200 information about what the chromos it's supposed to be. And Uh. 0:10:32.320 --> 0:10:35.199 One of the things they want to achieve is they 0:10:35.200 --> 0:10:39.160 want to be very very thin. They don't when they 0:10:39.320 --> 0:10:42.320 boot up a laptop that has chromos on it. They 0:10:42.360 --> 0:10:44.760 said they wanted to be something along the lines of 0:10:45.040 --> 0:10:48.240 seven seconds. Uh. There you're not loading a lot of 0:10:48.280 --> 0:10:52.880 information uh in the computer like you would with other 0:10:52.960 --> 0:10:56.960 operating systems. They wanted to be basically the Internet and 0:10:57.000 --> 0:10:58.599 everything else is there. They don't want you to have 0:10:58.640 --> 0:11:01.880 a lot have to worry about things like updates where 0:11:01.880 --> 0:11:06.200 you have to deal with regular updates. This all happens automatically, 0:11:06.880 --> 0:11:10.280 uh theoretically without you knowing that it's going on. Again, 0:11:10.360 --> 0:11:13.400 haven't had the opportunity to try it myself. Another thing 0:11:13.480 --> 0:11:16.000 they don't want you to have to mess with his drivers. Um. 0:11:16.160 --> 0:11:19.439 Google print uh is supposed or cloud print as supposed 0:11:19.440 --> 0:11:21.920 to take care of printing for you. But you know, 0:11:22.120 --> 0:11:25.040 if if you have a if you have a particular 0:11:25.120 --> 0:11:27.760 type of printer, you might have to download a driver 0:11:27.880 --> 0:11:31.240 for your Windows or Mac or Lenox computer in order 0:11:31.320 --> 0:11:34.160 to have it, you know, be able to communicate with 0:11:34.240 --> 0:11:37.040 that device. Um and if you buy a new printer, 0:11:37.240 --> 0:11:39.920 or if you take your laptop to work and you 0:11:39.920 --> 0:11:41.599 want to print on the office printer, which is a 0:11:41.600 --> 0:11:45.920 completely different kind of printer, you have to deal with that. Well, theoretically, 0:11:45.920 --> 0:11:49.000 the cloud Print service is supposed to help you take 0:11:49.000 --> 0:11:50.720 care of that, and they want they don't want you 0:11:50.760 --> 0:11:52.960 to have to deal with all the little bits and 0:11:53.000 --> 0:11:57.320 pieces of a traditional operating system. And indeed, um, you know, 0:11:57.360 --> 0:12:00.200 we actually have an article about about this on the 0:12:00.200 --> 0:12:04.080 side written by Nathan Chandler, one of my other writers. 0:12:04.960 --> 0:12:08.720 Um and uh you know, based on his research, he 0:12:08.800 --> 0:12:12.600 found that Windows seven takes up to sixty times the 0:12:12.679 --> 0:12:18.400 disk space of Google's Chromos. That's huge and millions of 0:12:18.480 --> 0:12:22.800 lines of code. Now, of course, Windows seven will also 0:12:23.040 --> 0:12:27.080 let you use Windows programs, uh, you know, current Windows 0:12:27.120 --> 0:12:30.000 programs as well as software developed in the past, and 0:12:30.080 --> 0:12:32.360 a lot of instances. I mean, it can do a 0:12:32.360 --> 0:12:36.000 whole lot of things, but it's it's designed for a 0:12:36.080 --> 0:12:39.200 desktop or a laptop with a robust processor and a 0:12:39.240 --> 0:12:42.400 hard drive and possibly disc drives and things. The Google 0:12:42.400 --> 0:12:45.160 OS isn't really supposed to support all of that. They 0:12:45.400 --> 0:12:50.400 Google seems to intend it specifically for UH mobile computers, 0:12:50.520 --> 0:12:54.840 UH laptops and netbooks primarily. And they only are this 0:12:54.920 --> 0:12:57.640 is another departure I thought was fascinating. They only are 0:12:57.679 --> 0:13:01.160 installing it in an O e M basis original original 0:13:01.160 --> 0:13:03.960 equipment manufacturer. If you hear computer people talk about that, 0:13:03.960 --> 0:13:07.040 that's what they mean. It's installed at the factory. You 0:13:07.080 --> 0:13:09.000 don't download it if you want. If you have a 0:13:09.000 --> 0:13:11.720 computer now and are waiting for Google Cloud or the 0:13:11.840 --> 0:13:15.000 Chromos to come out, and because you wanted to download 0:13:15.000 --> 0:13:16.960 it and try it out, they say they're not going 0:13:17.000 --> 0:13:19.640 to do that. They're only going to pre install it 0:13:19.679 --> 0:13:23.520 on machines before they leave the factor. Yeah, and uh, 0:13:23.679 --> 0:13:26.800 I mean in a way you can kind of understand 0:13:27.240 --> 0:13:31.280 that approach. I mean, for one thing, we're we're talking 0:13:31.280 --> 0:13:34.439 about an approach to computing that not everyone's going to 0:13:34.480 --> 0:13:39.160 be comfortable with. UM. For one thing, gaming is a 0:13:39.200 --> 0:13:41.400 big issue for some people. They say, well, if I 0:13:41.440 --> 0:13:44.920 have a cloud based computer, then that really limits what 0:13:45.000 --> 0:13:48.360 I can do as far as gaming is concerned. And um, 0:13:48.400 --> 0:13:51.280 I'm sure Google would say, yeah, this really wasn't intended 0:13:51.520 --> 0:13:53.080 for that. I mean, you could still play all the 0:13:53.120 --> 0:13:56.520 casual games that you find online, um, you know, like 0:13:56.559 --> 0:13:59.120 the flash based games and stuff, and you could use 0:13:59.160 --> 0:14:03.120 other services is to uh stream games to your your 0:14:03.160 --> 0:14:07.240 device potentially. Um, but that's you know, it's it's it 0:14:07.320 --> 0:14:09.240 does limit you as far as that goes. It also 0:14:09.280 --> 0:14:11.640 limits you, like you were saying, the kind of software 0:14:11.640 --> 0:14:15.600 you can use. Now again, Google could argue that using 0:14:15.600 --> 0:14:21.720 web based applications, ultimately the the opportunities are limitless, right 0:14:22.160 --> 0:14:25.720 that you you would have way more choice and uh 0:14:25.760 --> 0:14:30.080 and at a variety of price levels of various applications 0:14:30.120 --> 0:14:32.280 to do the things you need to do, and you 0:14:32.320 --> 0:14:35.640 wouldn't have to you know, download anything. You would essentially 0:14:35.720 --> 0:14:38.000 purchase it. The little icon would pop up on your 0:14:38.000 --> 0:14:39.680 screen and then just by clicking it, you would go 0:14:39.720 --> 0:14:44.760 to the cloud based service. Um. That's uh, that's pretty 0:14:44.880 --> 0:14:48.920 enticing to me, at least for at least for a 0:14:48.960 --> 0:14:51.440 secondary computer. And I don't know that I could use 0:14:51.480 --> 0:14:54.520 it as my primary machine. Um well, first of all, 0:14:54.720 --> 0:14:58.480 it would have to have applications that were there were 0:14:58.520 --> 0:15:02.560 compatible with the stuff that we you here in the office. UM. 0:15:02.600 --> 0:15:05.240 And in some cases that's just not gonna happen. I'd 0:15:05.280 --> 0:15:06.800 have to have I'd have to have a machine with 0:15:06.840 --> 0:15:10.680 a more powerful native capabilities and operating system that was 0:15:10.760 --> 0:15:16.160 computer based, not cloud based. Um. They also uh, but 0:15:16.440 --> 0:15:18.960 I should point out I feel compelled to point out. Um, 0:15:19.000 --> 0:15:21.440 you might think that you know it isn't with a 0:15:21.480 --> 0:15:24.320 new OS. Uh. Well, it's Linux based, so of course 0:15:24.360 --> 0:15:27.880 there are there are many, many, many Linux based apps, 0:15:27.920 --> 0:15:33.200 open source, UM and otherwise. But Google also has its 0:15:33.240 --> 0:15:37.280 own web store two for uh applications that you might 0:15:37.320 --> 0:15:40.120 run on the Google OS. So don't think that uh, 0:15:40.160 --> 0:15:44.200 it would be um uh you know, less likely to 0:15:44.320 --> 0:15:47.320 have a breadth of software. And of course if it succeeds, 0:15:47.360 --> 0:15:49.600 more people will develop for it. There will be people 0:15:49.600 --> 0:15:52.800 who are willing to give it a try. Certainly, UM, 0:15:52.960 --> 0:15:56.880 I don't know how compatible it is with traditional Linux applications. 0:15:56.880 --> 0:15:58.960 There may be a lot of them again, things like 0:15:59.360 --> 0:16:03.680 images probasit, thing like GEMP or Inkscape. Uh might be 0:16:03.760 --> 0:16:06.080 too much for an operating system like this, and it 0:16:06.120 --> 0:16:10.280 would have to be stored in the cloud. Again. UM, 0:16:10.280 --> 0:16:12.840 but you know, we'll kind of have to see how 0:16:12.880 --> 0:16:16.120 that goes. But it does. It doesn't seem like hardcore 0:16:16.160 --> 0:16:19.040 gamers or people who are doing a lot of high 0:16:19.160 --> 0:16:22.840 end digital editing, video editing, audio editing, people like that. 0:16:23.120 --> 0:16:26.320 It's not it's not really going to be useful for them, 0:16:26.360 --> 0:16:29.680 but for people who are doing day to day productivity stuff, 0:16:29.760 --> 0:16:32.240 especially stuff that you can do online. It is intended 0:16:32.280 --> 0:16:35.320 to be an online operating system after it, um, I 0:16:35.360 --> 0:16:38.080 think I think it may end up being useful and 0:16:38.120 --> 0:16:41.760 certainly affordable. Yeah, the online operating system is another really 0:16:41.800 --> 0:16:44.760 important part. We we kind of just assumed that when 0:16:44.760 --> 0:16:46.720 we started talking about this, but that that's something we 0:16:46.720 --> 0:16:49.720 should mention. Since this is cloud based and all these 0:16:49.720 --> 0:16:53.920 applications are essentially tied to the web. You have to 0:16:54.000 --> 0:16:56.120 have an Internet connection in order for this computer to 0:16:56.120 --> 0:16:59.080 actually be useful. It's funny you would mention that I 0:16:59.080 --> 0:17:01.440 found out something I did not know about the chromos. 0:17:01.560 --> 0:17:03.840 What's in doing research for this because I had heard 0:17:03.840 --> 0:17:09.240 some of this material. But uh, Chrome notebooks are actually 0:17:09.320 --> 0:17:13.600 going to have data plans from Verizon Wireless up to 0:17:13.720 --> 0:17:17.760 a hundred megabytes of free three G data every month 0:17:18.080 --> 0:17:23.520 for two years. Megas free that much. Um. But but 0:17:23.560 --> 0:17:26.280 then again, these these computers are supposed to have both 0:17:26.359 --> 0:17:28.520 WiFi and three G. So it's not like three G 0:17:28.720 --> 0:17:32.359 is the only way you get data. Like for most people, 0:17:32.359 --> 0:17:35.040 I think WiFi would be the primary way they would 0:17:35.040 --> 0:17:37.399 get data. So as long as you were in someplace 0:17:37.400 --> 0:17:39.119 where there was a WiFi hot spot, you'd be good 0:17:39.200 --> 0:17:41.159 to go. And when you're somewhere where there's not a 0:17:41.200 --> 0:17:43.919 WiFi hot spot, then hopefully you'd be able to access 0:17:43.920 --> 0:17:47.120 a three G data network. Yeah. Plus well, I mean 0:17:47.280 --> 0:17:51.399 WiFi is faster even three G UM. But yes, if 0:17:51.440 --> 0:17:54.560 you want to a limitless day pass, uh, you'd be 0:17:54.560 --> 0:17:59.200 paying per day for three G access or Verizon access. 0:17:59.200 --> 0:18:01.639 I don't know, Maybe it's orgy by next year, and 0:18:01.960 --> 0:18:05.400 depending on when this law launches. Um, if you want 0:18:05.400 --> 0:18:10.040 an additional one gigabyte of information per month, it's twenty dollars. 0:18:10.400 --> 0:18:13.960 Three gigabytes would be thirty five dollars, and five gigabytes 0:18:14.000 --> 0:18:18.960 additional would be fifty dollars per month. So that's pretty hefty. 0:18:19.000 --> 0:18:20.879 If you're planning on doing a lot of computing on 0:18:20.880 --> 0:18:23.800 the road, maybe for business that would be worth it 0:18:24.000 --> 0:18:26.080 because you could probably get reimbursed for that, But if 0:18:26.080 --> 0:18:28.560 this is for personal use, that may not be Uh, 0:18:28.880 --> 0:18:31.200 that may not be the best option for you. Yeah, 0:18:31.359 --> 0:18:34.280 but I mean if you if you're able to click 0:18:34.320 --> 0:18:37.639 in on WiFi networks, like if you've got WiFi hotspots 0:18:37.760 --> 0:18:40.600 or you know, you're mainly using this around your home 0:18:40.720 --> 0:18:43.359 or office, it's not that's not going to be an issue. 0:18:43.400 --> 0:18:45.320 You can just use the WiFi to get access to 0:18:45.320 --> 0:18:48.040 the data and you don't have to worry about incurring fees, 0:18:48.440 --> 0:18:50.640 you know, going over your cap, unless, of course, your 0:18:50.840 --> 0:18:54.560 I s P has a cap for your just your 0:18:54.560 --> 0:18:58.520 regular Internet usage. Some some peas do, and some of 0:18:58.560 --> 0:19:01.919 the caps are I don't know. Relatively, it depends on 0:19:01.960 --> 0:19:05.440 who upon whom you ask. Um. I've heard one person 0:19:05.560 --> 0:19:13.000 sayifty gigabyte cap per month is low, yeah, and for me, 0:19:13.080 --> 0:19:17.600 two gigabytes is more than enough. But then she was 0:19:17.640 --> 0:19:20.920 specifically talking about being able to back up a full 0:19:21.359 --> 0:19:24.639 computer hard drive to the cloud. I think you wouldn't 0:19:24.640 --> 0:19:26.720 be able to do that more than once a month. 0:19:26.760 --> 0:19:28.680 If it were, you know, a really big hard drive 0:19:28.720 --> 0:19:32.240 and you were using a cloud based backup system, then 0:19:32.400 --> 0:19:34.680 you could only do it once or maybe not even once, 0:19:34.680 --> 0:19:36.119 depending on the size of your hard drive. Now I 0:19:36.160 --> 0:19:39.639 can't imagine doing that, um, But then it's because I 0:19:39.640 --> 0:19:43.200 don't tend to use the online data services for backing 0:19:43.280 --> 0:19:45.960 up my hard drive. It's funny you would say that, 0:19:46.920 --> 0:19:50.119 because I would think with the with Google's reputation of 0:19:51.280 --> 0:19:54.720 massive redundancy, and by redundancy if you're not familiar with 0:19:54.720 --> 0:19:59.000 that term, we mean Google servers have lots and lots 0:19:59.000 --> 0:20:01.639 of other servers with the same information on them. So 0:20:01.720 --> 0:20:05.879 if one of them breaks, basically Google is losing nothing 0:20:06.040 --> 0:20:08.880 because it's been the company backs up its own equipment. 0:20:08.880 --> 0:20:10.880 So I would imagine that if you had an account 0:20:11.320 --> 0:20:15.119 and had Google Chromos on your operating system, your information 0:20:15.280 --> 0:20:18.520 would all be backed up automatically by Google. And that 0:20:18.680 --> 0:20:22.119 is one of the things that they have have said that. Um, 0:20:22.160 --> 0:20:26.000 they're they're very strong on privacy. UM, they're very concerned 0:20:26.040 --> 0:20:30.840 with encrypting your information while it's on their servers. UM 0:20:30.920 --> 0:20:37.120 and sand boxing basically keeping viruses at in in a 0:20:37.320 --> 0:20:43.080 h quarantine quarantined environment, uh in order to prevent them 0:20:43.119 --> 0:20:47.879 from infecting the machines and infecting your information, um, you know, 0:20:47.920 --> 0:20:52.280 to the point where it becomes uh um corrupted, prevent 0:20:52.320 --> 0:20:55.360 anything from happening to it. Um you know they're they're 0:20:55.400 --> 0:20:57.720 they're talking those points up, So I would imagine it 0:20:57.800 --> 0:21:00.880 would be pretty safe. That the thing is cloud computing 0:21:01.000 --> 0:21:04.560 has a long running stigma for a lot of people 0:21:04.600 --> 0:21:08.440 that because that information is on you know, a computer 0:21:08.600 --> 0:21:11.880 or even multiple computers out there somewhere where they don't 0:21:11.880 --> 0:21:14.280 know where it is, it concerns them that someone could 0:21:14.320 --> 0:21:17.360 break in and and gain access to that information, possibly 0:21:17.440 --> 0:21:21.119 copy it, uh, sell it to people for for money, 0:21:21.160 --> 0:21:23.919 and who knows what all else. And you've got your 0:21:23.920 --> 0:21:27.920 sensitive information on there. Um Yes, the company, I'm sure 0:21:27.960 --> 0:21:30.560 we'll do its best to protect that information, but it's 0:21:30.600 --> 0:21:33.240 still causes people concerned. And I think that's why you 0:21:33.280 --> 0:21:37.320 see Google saying, hey, look it's all encrypted, it's all safe, 0:21:37.359 --> 0:21:39.760 it's all backed up. You know, no, nothing to worry 0:21:39.760 --> 0:21:43.480 about here. It's a it's a There two sides to 0:21:43.560 --> 0:21:47.679 that story. One side is that companies, big companies like Google, 0:21:48.240 --> 0:21:52.040 we'll be able to afford and design much tighter security 0:21:52.040 --> 0:21:55.080 measures than your average user is going to have access to. 0:21:55.160 --> 0:21:58.760 And most I'm gonna say most users don't aren't nearly 0:21:58.800 --> 0:22:01.040 as secure as they need to be. You know, they 0:22:01.280 --> 0:22:04.040 they have poor password protection. A lot of them are 0:22:04.080 --> 0:22:07.439 using open networks, although I'm seeing fewer cases of that. 0:22:07.520 --> 0:22:10.719 Now I'm seeing more people actually secure their wireless networks, 0:22:10.720 --> 0:22:14.080 which is nice, um, But I mean, it's just that 0:22:14.160 --> 0:22:17.119 people don't tend to practice very strong security measures. So 0:22:17.160 --> 0:22:19.720 you can say, well, Google is going to use state 0:22:19.720 --> 0:22:22.320 of the art security, so that's a good thing. However, 0:22:22.400 --> 0:22:26.000 Google is also a huge company and therefore, by virtue 0:22:26.040 --> 0:22:29.680 of being a big company is a big target. Each 0:22:29.760 --> 0:22:33.960 individual user out there using the Internet is not a 0:22:34.040 --> 0:22:36.639 huge target. Now that that you could still fall prey 0:22:36.680 --> 0:22:40.320 to scams or phishing attempts, that kind of thing, but 0:22:40.440 --> 0:22:43.199 it's not Most of us don't have a target on 0:22:43.200 --> 0:22:45.760 our backs. You know, we aren't walking around with with 0:22:45.840 --> 0:22:50.879 hackers looking to get access specifically to our machine. They 0:22:50.920 --> 0:22:54.040 want access to machines. They don't care who it happens 0:22:54.080 --> 0:22:58.600 to be, right, So you could argue, well, Google's better protected, 0:22:58.640 --> 0:23:01.320 but it's also a more empting targets. So you got 0:23:01.400 --> 0:23:04.119 to weigh both of those things against one another, and 0:23:04.160 --> 0:23:07.560 then you say, well, our Google security measure is going 0:23:07.600 --> 0:23:10.240 to be strong enough so that it doesn't matter that 0:23:10.280 --> 0:23:14.080