1 00:00:00,280 --> 00:00:02,840 Speaker 1: Brought to you by the reinvented two thousand twelve camera. 2 00:00:03,160 --> 00:00:08,920 Speaker 1: It's ready. Are you get in touch with technology? With 3 00:00:09,039 --> 00:00:17,920 Speaker 1: tech Stuff from how stuff works dot com. Hello again, everyone, 4 00:00:17,960 --> 00:00:21,000 Speaker 1: Welcome to tech stuff. My name is Chris Pollette. I 5 00:00:21,040 --> 00:00:24,360 Speaker 1: am an editor at how stuff works dot com. Sitting 6 00:00:24,360 --> 00:00:26,680 Speaker 1: across from me as a guy who knows a whole 7 00:00:26,720 --> 00:00:29,960 Speaker 1: lot about tech stuff, that would be senior writer Jonathan Strickland. 8 00:00:30,120 --> 00:00:34,760 Speaker 1: Throughout human history, we've been dependent on machines to survive fate, 9 00:00:35,040 --> 00:00:39,920 Speaker 1: it seems, is not without a sense of irony. Very nice, 10 00:00:40,000 --> 00:00:46,560 Speaker 1: thank you. Okay, So today's topic is an interesting topic, actually, yes, 11 00:00:47,120 --> 00:00:49,280 Speaker 1: because it's so close to so many things and yet 12 00:00:49,840 --> 00:00:53,479 Speaker 1: it's not the same as any one of them. Well, 13 00:00:53,760 --> 00:00:58,280 Speaker 1: I think that came from a Beatles song. No, No, 14 00:00:58,440 --> 00:01:03,960 Speaker 1: it's a it's chromo, yes, And it has ties to 15 00:01:04,080 --> 00:01:07,600 Speaker 1: a great many different other technologies and is sort of 16 00:01:07,600 --> 00:01:09,640 Speaker 1: a standalone thing. And I think that's why so many 17 00:01:09,680 --> 00:01:13,040 Speaker 1: people are confused about it, because it seems like a 18 00:01:13,080 --> 00:01:15,319 Speaker 1: whole bunch of different stuff, but it is its own 19 00:01:15,360 --> 00:01:19,880 Speaker 1: standalone operating system for computers. Yeah, this is um There 20 00:01:19,880 --> 00:01:22,160 Speaker 1: are a lot of reasons why this is a confusing topic. 21 00:01:22,240 --> 00:01:24,640 Speaker 1: For some people. Now, a lot of our listeners have 22 00:01:24,680 --> 00:01:27,320 Speaker 1: probably been following the development of CHROMOS over the last 23 00:01:27,520 --> 00:01:31,480 Speaker 1: uh well more than a year now, because Google initially 24 00:01:31,520 --> 00:01:35,440 Speaker 1: announced CHROMOS back in two thousand nine. Yes, July seven, 25 00:01:35,600 --> 00:01:38,800 Speaker 1: two thousand nine, by my reckoning, Yes, that is that's 26 00:01:38,840 --> 00:01:41,080 Speaker 1: the date I have on this blog post where they 27 00:01:41,240 --> 00:01:46,080 Speaker 1: called it. That was titled introducing the Google Chromos uh 28 00:01:46,440 --> 00:01:49,520 Speaker 1: So Yeah, Google announced this back in two thousand nine, 29 00:01:50,080 --> 00:01:53,840 Speaker 1: and then essentially the message was that this was going 30 00:01:53,880 --> 00:01:57,520 Speaker 1: to be a cloud based operating system, it was meant 31 00:01:57,640 --> 00:02:02,760 Speaker 1: for computers, and that we would start seeing it on 32 00:02:03,040 --> 00:02:06,960 Speaker 1: machines and around the end of Yes, now as we 33 00:02:07,000 --> 00:02:09,680 Speaker 1: record this, it is the very end of and indeed 34 00:02:09,720 --> 00:02:14,560 Speaker 1: we have seen the first computer with this up ring 35 00:02:14,600 --> 00:02:19,400 Speaker 1: system uh loaded in as its native OS. But the 36 00:02:19,440 --> 00:02:22,880 Speaker 1: program itself is still very much in beta mode, which 37 00:02:23,120 --> 00:02:26,640 Speaker 1: to Google, you know, kind of part for the course. Really, 38 00:02:27,480 --> 00:02:33,120 Speaker 1: Google is king of the beta. Yeah, and um, I 39 00:02:33,120 --> 00:02:36,400 Speaker 1: think it's safe to say, um that I still only 40 00:02:36,800 --> 00:02:40,280 Speaker 1: speaking for myself personally, I think there there is uh 41 00:02:40,320 --> 00:02:43,000 Speaker 1: there are some details out there about what chrome os 42 00:02:43,240 --> 00:02:46,320 Speaker 1: is supposed to be, and I think they're pretty accurate 43 00:02:46,400 --> 00:02:49,520 Speaker 1: based on the bets that they've released, but I'm not 44 00:02:49,560 --> 00:02:52,760 Speaker 1: sure that we know all the details enough to be 45 00:02:52,840 --> 00:02:56,400 Speaker 1: definitive about some parts of it. Like, um, I think 46 00:02:56,440 --> 00:02:58,760 Speaker 1: I think a lot of the information that's out there 47 00:02:59,160 --> 00:03:05,080 Speaker 1: still is more marketing material than it is hardened fast numbers. Right. 48 00:03:05,120 --> 00:03:06,960 Speaker 1: And there are people out there right now who are 49 00:03:07,080 --> 00:03:10,960 Speaker 1: using Chromos because as probably the pilot program Google shipped 50 00:03:11,000 --> 00:03:16,400 Speaker 1: out um, they shipped out notebooks, computer notebooks. Uh. The 51 00:03:16,400 --> 00:03:20,440 Speaker 1: the technical name for it is the cr DASH for 52 00:03:20,720 --> 00:03:24,760 Speaker 1: eight UM. And so there are people who applied to 53 00:03:24,840 --> 00:03:28,120 Speaker 1: be in this pilot program and Google sent some of 54 00:03:28,160 --> 00:03:32,280 Speaker 1: them these machines with the intent. You know, they specifically said, 55 00:03:32,400 --> 00:03:35,640 Speaker 1: use these machines as your primary machine. That's the only 56 00:03:35,680 --> 00:03:37,560 Speaker 1: reason we're sending this to you, so that you can 57 00:03:37,600 --> 00:03:39,920 Speaker 1: really give it a test and we can see make 58 00:03:39,920 --> 00:03:41,720 Speaker 1: sure we iron bugs out and that kind of thing. 59 00:03:42,240 --> 00:03:43,800 Speaker 1: So it doesn't do them any good if you just 60 00:03:43,920 --> 00:03:47,240 Speaker 1: you know, use that like once in a while. So 61 00:03:47,320 --> 00:03:50,520 Speaker 1: they wanted testers who could use it as their primary 62 00:03:50,560 --> 00:03:55,600 Speaker 1: machine as much as possible. Um, it's interesting, it's actually Chromos. 63 00:03:55,720 --> 00:03:57,600 Speaker 1: You might hear people talk about how Google it takes 64 00:03:57,640 --> 00:04:01,680 Speaker 1: us sort of open approach too. They're operating systems. Chromo 65 00:04:01,800 --> 00:04:05,800 Speaker 1: S technically is not really an open system. It's based 66 00:04:05,880 --> 00:04:11,720 Speaker 1: upon source code from chromium OS, which is the open system. Yes. 67 00:04:11,800 --> 00:04:16,440 Speaker 1: That actually reminds me of macOS ten, which is based 68 00:04:16,520 --> 00:04:20,680 Speaker 1: upon b s D, but which is an open source system. 69 00:04:20,720 --> 00:04:24,599 Speaker 1: But again macOS ten itself is closed. I mean it's 70 00:04:24,720 --> 00:04:28,080 Speaker 1: it's Apple. You kind of expect that from Apple, but um, yeah, 71 00:04:28,120 --> 00:04:32,520 Speaker 1: it's it's basically a derivative of that is a derivative 72 00:04:32,560 --> 00:04:34,880 Speaker 1: of BSD, or it builds on bs D and is 73 00:04:34,920 --> 00:04:37,479 Speaker 1: its own operating system. And that's similar to what the 74 00:04:37,720 --> 00:04:43,039 Speaker 1: CHROMOS is. Yeah. Um, also it's uh, it's related to Linux. Yes, 75 00:04:43,080 --> 00:04:47,560 Speaker 1: the Chromium o S is UM and uh it's important 76 00:04:47,600 --> 00:04:50,159 Speaker 1: to note too that it is not Android, which is 77 00:04:50,200 --> 00:04:54,920 Speaker 1: Google's operating system for global devices. Yeah. This this is 78 00:04:55,000 --> 00:04:59,039 Speaker 1: another point that becomes really confusing for people who aren't 79 00:04:59,080 --> 00:05:02,520 Speaker 1: really following the store, because you've got the Android platform, 80 00:05:02,560 --> 00:05:05,440 Speaker 1: which is just now really starting to get some some 81 00:05:05,680 --> 00:05:08,800 Speaker 1: identity in the market. Right there are people who know 82 00:05:08,880 --> 00:05:12,159 Speaker 1: what Android is, um, because of all the different commercials 83 00:05:12,160 --> 00:05:15,520 Speaker 1: for various phones as well as the tablet devices like 84 00:05:15,720 --> 00:05:19,640 Speaker 1: the Galaxy Tab. So people know what Android is and 85 00:05:19,839 --> 00:05:22,560 Speaker 1: they think of that as the Google operating system. So 86 00:05:22,720 --> 00:05:25,600 Speaker 1: why would Google come out with the Chrome operating system. 87 00:05:25,680 --> 00:05:27,760 Speaker 1: I've I've actually heard will have tech tournal lests say 88 00:05:27,800 --> 00:05:30,320 Speaker 1: that this is a bad idea to come out with 89 00:05:30,400 --> 00:05:33,719 Speaker 1: a separate operating system just for notebook computers. What I 90 00:05:33,720 --> 00:05:36,840 Speaker 1: think is funny is that that's what other companies are 91 00:05:36,880 --> 00:05:39,640 Speaker 1: doing already. Yes, I guess what they're saying is they 92 00:05:39,640 --> 00:05:43,080 Speaker 1: thought that maybe the era of separate operating systems is 93 00:05:43,279 --> 00:05:45,039 Speaker 1: slowly coming to an end, and we are going to 94 00:05:45,080 --> 00:05:50,160 Speaker 1: see a get ready for you, guys, convergence emerge where 95 00:05:50,200 --> 00:05:52,880 Speaker 1: we see the same operating system used across an entire 96 00:05:52,960 --> 00:05:56,240 Speaker 1: variety of gadgets, from computers all the way down to 97 00:05:56,480 --> 00:06:00,479 Speaker 1: cell phones. Yes, we're not there yet. So perhaps what 98 00:06:00,520 --> 00:06:03,840 Speaker 1: people thought was that Google would just lead the way 99 00:06:04,160 --> 00:06:07,400 Speaker 1: and create an operating system that would go across this 100 00:06:07,560 --> 00:06:11,159 Speaker 1: entire range of hardware, and that way you didn't have 101 00:06:11,200 --> 00:06:13,840 Speaker 1: to wait for things to converge. Google would just kind 102 00:06:13,839 --> 00:06:16,480 Speaker 1: of lead the way. That would like like some generation 103 00:06:16,520 --> 00:06:18,839 Speaker 1: of Android, maybe two or three generations down the line, 104 00:06:19,400 --> 00:06:22,159 Speaker 1: would be robust enough to be a cloud based operating 105 00:06:22,200 --> 00:06:26,640 Speaker 1: system for a computer. That's not what's happened, and Google 106 00:06:26,680 --> 00:06:29,440 Speaker 1: has essentially said the same thing that other companies have said, 107 00:06:29,480 --> 00:06:33,440 Speaker 1: which is that mobile devices and computers are two separate 108 00:06:33,480 --> 00:06:37,440 Speaker 1: things right now, and while we may be heading towards convergence, 109 00:06:37,480 --> 00:06:40,680 Speaker 1: we're not there yet. So it's it's weird for me 110 00:06:40,720 --> 00:06:43,800 Speaker 1: to hear people criticize Google for making this decision when 111 00:06:43,839 --> 00:06:46,479 Speaker 1: other companies have been doing this. I mean, you brought 112 00:06:46,560 --> 00:06:50,160 Speaker 1: up Apple. Apple has the Mac os that's for their 113 00:06:50,200 --> 00:06:53,560 Speaker 1: computer systems, then it has iOS, which is for their 114 00:06:54,120 --> 00:06:58,160 Speaker 1: mobile systems, which includes the iPad, And of course Microsoft 115 00:06:58,279 --> 00:07:03,040 Speaker 1: has Windows seven, Windows Mobile seven, which I'm sorry, I'm sorry, 116 00:07:03,080 --> 00:07:05,520 Speaker 1: You're right, well, it was at one point Windows Mobile 117 00:07:05,520 --> 00:07:07,239 Speaker 1: I think I think they only got up to six 118 00:07:07,279 --> 00:07:09,560 Speaker 1: for Windows Mobile, Yes, but then they went to Windows 119 00:07:09,600 --> 00:07:12,360 Speaker 1: Phone seven, so I'm sorry, Yes, Windows Phone seven, which 120 00:07:12,560 --> 00:07:16,720 Speaker 1: again the seven makes it confusing to some people because 121 00:07:17,320 --> 00:07:20,040 Speaker 1: you know, people are thinking, you know, Windows seven, I 122 00:07:20,080 --> 00:07:23,400 Speaker 1: know what that is, but Windows Phone seven is different. Now, 123 00:07:24,160 --> 00:07:26,200 Speaker 1: I would say that all three of them have done 124 00:07:26,200 --> 00:07:29,400 Speaker 1: a pretty good job making their mobile operating system in 125 00:07:29,440 --> 00:07:33,520 Speaker 1: their computer operating system look pretty similar. I should say 126 00:07:33,520 --> 00:07:36,720 Speaker 1: that the Chromos I haven't really seen, but the Chromos 127 00:07:36,840 --> 00:07:41,400 Speaker 1: does use the Chrome web browser that is out for Windows, 128 00:07:41,440 --> 00:07:45,119 Speaker 1: Mac and Linux um as it's one of its major 129 00:07:45,200 --> 00:07:47,600 Speaker 1: underpinnings because so much of what you do with the 130 00:07:47,680 --> 00:07:50,760 Speaker 1: chromos or will do with the chromos, is done and 131 00:07:50,800 --> 00:07:54,640 Speaker 1: the cloud, and we should probably talk about Yeah. So 132 00:07:54,720 --> 00:07:57,360 Speaker 1: the idea here is it's actually a pretty simple one, 133 00:07:57,400 --> 00:08:00,920 Speaker 1: and we've talked about it in the past about cloud computing. Chromos. 134 00:08:01,280 --> 00:08:05,120 Speaker 1: Chromos is a specific approach to cloud computing. The idea 135 00:08:05,160 --> 00:08:09,280 Speaker 1: here is that your computer would be a very thin client. 136 00:08:09,440 --> 00:08:12,400 Speaker 1: It would not need to be particularly powerful in any way, 137 00:08:13,080 --> 00:08:15,080 Speaker 1: because all it would really need to do is run 138 00:08:15,120 --> 00:08:18,200 Speaker 1: this operating system, and then the applications would really just 139 00:08:18,280 --> 00:08:22,880 Speaker 1: be kind of links to online services. So let's say 140 00:08:22,880 --> 00:08:25,040 Speaker 1: that you want to use a word processing program. You 141 00:08:25,040 --> 00:08:28,320 Speaker 1: could use something like Google Docs, where the you know, 142 00:08:28,440 --> 00:08:31,920 Speaker 1: you, you you have an interface that you use on your computer, 143 00:08:32,360 --> 00:08:36,280 Speaker 1: but the documents, the word processing, the actual the actual 144 00:08:36,360 --> 00:08:42,240 Speaker 1: program exists on another computer a server. Um technically actually will. 145 00:08:42,600 --> 00:08:46,679 Speaker 1: It will exist on several because of redundancy issues. Redundancy 146 00:08:46,760 --> 00:08:49,400 Speaker 1: is very important in cloud computing because, of course, if 147 00:08:49,480 --> 00:08:53,400 Speaker 1: one server goes down and there's no redundancy, you've just 148 00:08:53,520 --> 00:08:57,320 Speaker 1: lost lots of customer data and customers don't tend to 149 00:08:57,360 --> 00:09:00,000 Speaker 1: like that very much. No, not really. They seem to 150 00:09:00,080 --> 00:09:04,160 Speaker 1: be um down on the whole. You just lost all 151 00:09:04,160 --> 00:09:07,520 Speaker 1: my stuff, you know. Angle They don't like that. So 152 00:09:07,720 --> 00:09:11,400 Speaker 1: the idea here is that you would have these applications 153 00:09:12,000 --> 00:09:14,520 Speaker 1: that you would really just have kind of a window 154 00:09:14,640 --> 00:09:17,080 Speaker 1: to those by you know, clicking on a little icon 155 00:09:17,480 --> 00:09:19,480 Speaker 1: and it would open up the interface, but the application 156 00:09:19,520 --> 00:09:22,200 Speaker 1: itself and all the data there and would exist on 157 00:09:22,640 --> 00:09:28,160 Speaker 1: other machines. And there's some kind of great applications for 158 00:09:28,240 --> 00:09:31,120 Speaker 1: this because that means that you aren't tied to a 159 00:09:31,120 --> 00:09:35,520 Speaker 1: specific machine. Your information would all be tied to your account, 160 00:09:35,720 --> 00:09:39,720 Speaker 1: your Google account in this case. So theoretically you could 161 00:09:40,000 --> 00:09:43,280 Speaker 1: go to any other device that's running the Chrome os, 162 00:09:43,920 --> 00:09:47,959 Speaker 1: log in as yourself using your Google profile, and then 163 00:09:48,000 --> 00:09:51,560 Speaker 1: have access to all your information, and then when you 164 00:09:51,640 --> 00:09:54,760 Speaker 1: logged out, you wouldn't have to worry about that information 165 00:09:54,840 --> 00:09:57,120 Speaker 1: sticking around the computer because it's not living in that 166 00:09:57,160 --> 00:10:03,840 Speaker 1: computer anyway. It's living on computer potentially thousands of miles away. Yeah, 167 00:10:03,840 --> 00:10:07,560 Speaker 1: there's one of the reasons Google is doing this, at 168 00:10:07,600 --> 00:10:11,280 Speaker 1: least according to uh the Google Chromos website, which I 169 00:10:11,320 --> 00:10:14,120 Speaker 1: would encourage you to to go to it's it's Um. 170 00:10:14,120 --> 00:10:17,440 Speaker 1: They do a lot of explaining in very simple terms. Uh, 171 00:10:17,480 --> 00:10:19,760 Speaker 1: you know for the non techie related person, which is 172 00:10:19,760 --> 00:10:21,920 Speaker 1: good because you know that pretty much describes me in 173 00:10:21,960 --> 00:10:26,640 Speaker 1: some ways. Um. You know it's it's very user friendly 174 00:10:27,520 --> 00:10:32,200 Speaker 1: information about what the chromos it's supposed to be. And Uh. 175 00:10:32,320 --> 00:10:35,199 Speaker 1: One of the things they want to achieve is they 176 00:10:35,200 --> 00:10:39,160 Speaker 1: want to be very very thin. They don't when they 177 00:10:39,320 --> 00:10:42,320 Speaker 1: boot up a laptop that has chromos on it. They 178 00:10:42,360 --> 00:10:44,760 Speaker 1: said they wanted to be something along the lines of 179 00:10:45,040 --> 00:10:48,240 Speaker 1: seven seconds. Uh. There you're not loading a lot of 180 00:10:48,280 --> 00:10:52,880 Speaker 1: information uh in the computer like you would with other 181 00:10:52,960 --> 00:10:56,960 Speaker 1: operating systems. They wanted to be basically the Internet and 182 00:10:57,000 --> 00:10:58,599 Speaker 1: everything else is there. They don't want you to have 183 00:10:58,640 --> 00:11:01,880 Speaker 1: a lot have to worry about things like updates where 184 00:11:01,880 --> 00:11:06,200 Speaker 1: you have to deal with regular updates. This all happens automatically, 185 00:11:06,880 --> 00:11:10,280 Speaker 1: uh theoretically without you knowing that it's going on. Again, 186 00:11:10,360 --> 00:11:13,400 Speaker 1: haven't had the opportunity to try it myself. Another thing 187 00:11:13,480 --> 00:11:16,000 Speaker 1: they don't want you to have to mess with his drivers. Um. 188 00:11:16,160 --> 00:11:19,439 Speaker 1: Google print uh is supposed or cloud print as supposed 189 00:11:19,440 --> 00:11:21,920 Speaker 1: to take care of printing for you. But you know, 190 00:11:22,120 --> 00:11:25,040 Speaker 1: if if you have a if you have a particular 191 00:11:25,120 --> 00:11:27,760 Speaker 1: type of printer, you might have to download a driver 192 00:11:27,880 --> 00:11:31,240 Speaker 1: for your Windows or Mac or Lenox computer in order 193 00:11:31,320 --> 00:11:34,160 Speaker 1: to have it, you know, be able to communicate with 194 00:11:34,240 --> 00:11:37,040 Speaker 1: that device. Um and if you buy a new printer, 195 00:11:37,240 --> 00:11:39,920 Speaker 1: or if you take your laptop to work and you 196 00:11:39,920 --> 00:11:41,599 Speaker 1: want to print on the office printer, which is a 197 00:11:41,600 --> 00:11:45,920 Speaker 1: completely different kind of printer, you have to deal with that. Well, theoretically, 198 00:11:45,920 --> 00:11:49,000 Speaker 1: the cloud Print service is supposed to help you take 199 00:11:49,000 --> 00:11:50,720 Speaker 1: care of that, and they want they don't want you 200 00:11:50,760 --> 00:11:52,960 Speaker 1: to have to deal with all the little bits and 201 00:11:53,000 --> 00:11:57,320 Speaker 1: pieces of a traditional operating system. And indeed, um, you know, 202 00:11:57,360 --> 00:12:00,200 Speaker 1: we actually have an article about about this on the 203 00:12:00,200 --> 00:12:04,080 Speaker 1: side written by Nathan Chandler, one of my other writers. 204 00:12:04,960 --> 00:12:08,720 Speaker 1: Um and uh you know, based on his research, he 205 00:12:08,800 --> 00:12:12,600 Speaker 1: found that Windows seven takes up to sixty times the 206 00:12:12,679 --> 00:12:18,400 Speaker 1: disk space of Google's Chromos. That's huge and millions of 207 00:12:18,480 --> 00:12:22,800 Speaker 1: lines of code. Now, of course, Windows seven will also 208 00:12:23,040 --> 00:12:27,080 Speaker 1: let you use Windows programs, uh, you know, current Windows 209 00:12:27,120 --> 00:12:30,000 Speaker 1: programs as well as software developed in the past, and 210 00:12:30,080 --> 00:12:32,360 Speaker 1: a lot of instances. I mean, it can do a 211 00:12:32,360 --> 00:12:36,000 Speaker 1: whole lot of things, but it's it's designed for a 212 00:12:36,080 --> 00:12:39,200 Speaker 1: desktop or a laptop with a robust processor and a 213 00:12:39,240 --> 00:12:42,400 Speaker 1: hard drive and possibly disc drives and things. The Google 214 00:12:42,400 --> 00:12:45,160 Speaker 1: OS isn't really supposed to support all of that. They 215 00:12:45,400 --> 00:12:50,400 Speaker 1: Google seems to intend it specifically for UH mobile computers, 216 00:12:50,520 --> 00:12:54,840 Speaker 1: UH laptops and netbooks primarily. And they only are this 217 00:12:54,920 --> 00:12:57,640 Speaker 1: is another departure I thought was fascinating. They only are 218 00:12:57,679 --> 00:13:01,160 Speaker 1: installing it in an O e M basis original original 219 00:13:01,160 --> 00:13:03,960 Speaker 1: equipment manufacturer. If you hear computer people talk about that, 220 00:13:03,960 --> 00:13:07,040 Speaker 1: that's what they mean. It's installed at the factory. You 221 00:13:07,080 --> 00:13:09,000 Speaker 1: don't download it if you want. If you have a 222 00:13:09,000 --> 00:13:11,720 Speaker 1: computer now and are waiting for Google Cloud or the 223 00:13:11,840 --> 00:13:15,000 Speaker 1: Chromos to come out, and because you wanted to download 224 00:13:15,000 --> 00:13:16,960 Speaker 1: it and try it out, they say they're not going 225 00:13:17,000 --> 00:13:19,640 Speaker 1: to do that. They're only going to pre install it 226 00:13:19,679 --> 00:13:23,520 Speaker 1: on machines before they leave the factor. Yeah, and uh, 227 00:13:23,679 --> 00:13:26,800 Speaker 1: I mean in a way you can kind of understand 228 00:13:27,240 --> 00:13:31,280 Speaker 1: that approach. I mean, for one thing, we're we're talking 229 00:13:31,280 --> 00:13:34,439 Speaker 1: about an approach to computing that not everyone's going to 230 00:13:34,480 --> 00:13:39,160 Speaker 1: be comfortable with. UM. For one thing, gaming is a 231 00:13:39,200 --> 00:13:41,400 Speaker 1: big issue for some people. They say, well, if I 232 00:13:41,440 --> 00:13:44,920 Speaker 1: have a cloud based computer, then that really limits what 233 00:13:45,000 --> 00:13:48,360 Speaker 1: I can do as far as gaming is concerned. And um, 234 00:13:48,400 --> 00:13:51,280 Speaker 1: I'm sure Google would say, yeah, this really wasn't intended 235 00:13:51,520 --> 00:13:53,080 Speaker 1: for that. I mean, you could still play all the 236 00:13:53,120 --> 00:13:56,520 Speaker 1: casual games that you find online, um, you know, like 237 00:13:56,559 --> 00:13:59,120 Speaker 1: the flash based games and stuff, and you could use 238 00:13:59,160 --> 00:14:03,120 Speaker 1: other services is to uh stream games to your your 239 00:14:03,160 --> 00:14:07,240 Speaker 1: device potentially. Um, but that's you know, it's it's it 240 00:14:07,320 --> 00:14:09,240 Speaker 1: does limit you as far as that goes. It also 241 00:14:09,280 --> 00:14:11,640 Speaker 1: limits you, like you were saying, the kind of software 242 00:14:11,640 --> 00:14:15,600 Speaker 1: you can use. Now again, Google could argue that using 243 00:14:15,600 --> 00:14:21,720 Speaker 1: web based applications, ultimately the the opportunities are limitless, right 244 00:14:22,160 --> 00:14:25,720 Speaker 1: that you you would have way more choice and uh 245 00:14:25,760 --> 00:14:30,080 Speaker 1: and at a variety of price levels of various applications 246 00:14:30,120 --> 00:14:32,280 Speaker 1: to do the things you need to do, and you 247 00:14:32,320 --> 00:14:35,640 Speaker 1: wouldn't have to you know, download anything. You would essentially 248 00:14:35,720 --> 00:14:38,000 Speaker 1: purchase it. The little icon would pop up on your 249 00:14:38,000 --> 00:14:39,680 Speaker 1: screen and then just by clicking it, you would go 250 00:14:39,720 --> 00:14:44,760 Speaker 1: to the cloud based service. Um. That's uh, that's pretty 251 00:14:44,880 --> 00:14:48,920 Speaker 1: enticing to me, at least for at least for a 252 00:14:48,960 --> 00:14:51,440 Speaker 1: secondary computer. And I don't know that I could use 253 00:14:51,480 --> 00:14:54,520 Speaker 1: it as my primary machine. Um well, first of all, 254 00:14:54,720 --> 00:14:58,480 Speaker 1: it would have to have applications that were there were 255 00:14:58,520 --> 00:15:02,560 Speaker 1: compatible with the stuff that we you here in the office. UM. 256 00:15:02,600 --> 00:15:05,240 Speaker 1: And in some cases that's just not gonna happen. I'd 257 00:15:05,280 --> 00:15:06,800 Speaker 1: have to have I'd have to have a machine with 258 00:15:06,840 --> 00:15:10,680 Speaker 1: a more powerful native capabilities and operating system that was 259 00:15:10,760 --> 00:15:16,160 Speaker 1: computer based, not cloud based. Um. They also uh, but 260 00:15:16,440 --> 00:15:18,960 Speaker 1: I should point out I feel compelled to point out. Um, 261 00:15:19,000 --> 00:15:21,440 Speaker 1: you might think that you know it isn't with a 262 00:15:21,480 --> 00:15:24,320 Speaker 1: new OS. Uh. Well, it's Linux based, so of course 263 00:15:24,360 --> 00:15:27,880 Speaker 1: there are there are many, many, many Linux based apps, 264 00:15:27,920 --> 00:15:33,200 Speaker 1: open source, UM and otherwise. But Google also has its 265 00:15:33,240 --> 00:15:37,280 Speaker 1: own web store two for uh applications that you might 266 00:15:37,320 --> 00:15:40,120 Speaker 1: run on the Google OS. So don't think that uh, 267 00:15:40,160 --> 00:15:44,200 Speaker 1: it would be um uh you know, less likely to 268 00:15:44,320 --> 00:15:47,320 Speaker 1: have a breadth of software. And of course if it succeeds, 269 00:15:47,360 --> 00:15:49,600 Speaker 1: more people will develop for it. There will be people 270 00:15:49,600 --> 00:15:52,800 Speaker 1: who are willing to give it a try. Certainly, UM, 271 00:15:52,960 --> 00:15:56,880 Speaker 1: I don't know how compatible it is with traditional Linux applications. 272 00:15:56,880 --> 00:15:58,960 Speaker 1: There may be a lot of them again, things like 273 00:15:59,360 --> 00:16:03,680 Speaker 1: images probasit, thing like GEMP or Inkscape. Uh might be 274 00:16:03,760 --> 00:16:06,080 Speaker 1: too much for an operating system like this, and it 275 00:16:06,120 --> 00:16:10,280 Speaker 1: would have to be stored in the cloud. Again. UM, 276 00:16:10,280 --> 00:16:12,840 Speaker 1: but you know, we'll kind of have to see how 277 00:16:12,880 --> 00:16:16,120 Speaker 1: that goes. But it does. It doesn't seem like hardcore 278 00:16:16,160 --> 00:16:19,040 Speaker 1: gamers or people who are doing a lot of high 279 00:16:19,160 --> 00:16:22,840 Speaker 1: end digital editing, video editing, audio editing, people like that. 280 00:16:23,120 --> 00:16:26,320 Speaker 1: It's not it's not really going to be useful for them, 281 00:16:26,360 --> 00:16:29,680 Speaker 1: but for people who are doing day to day productivity stuff, 282 00:16:29,760 --> 00:16:32,240 Speaker 1: especially stuff that you can do online. It is intended 283 00:16:32,280 --> 00:16:35,320 Speaker 1: to be an online operating system after it, um, I 284 00:16:35,360 --> 00:16:38,080 Speaker 1: think I think it may end up being useful and 285 00:16:38,120 --> 00:16:41,760 Speaker 1: certainly affordable. Yeah, the online operating system is another really 286 00:16:41,800 --> 00:16:44,760 Speaker 1: important part. We we kind of just assumed that when 287 00:16:44,760 --> 00:16:46,720 Speaker 1: we started talking about this, but that that's something we 288 00:16:46,720 --> 00:16:49,720 Speaker 1: should mention. Since this is cloud based and all these 289 00:16:49,720 --> 00:16:53,920 Speaker 1: applications are essentially tied to the web. You have to 290 00:16:54,000 --> 00:16:56,120 Speaker 1: have an Internet connection in order for this computer to 291 00:16:56,120 --> 00:16:59,080 Speaker 1: actually be useful. It's funny you would mention that I 292 00:16:59,080 --> 00:17:01,440 Speaker 1: found out something I did not know about the chromos. 293 00:17:01,560 --> 00:17:03,840 Speaker 1: What's in doing research for this because I had heard 294 00:17:03,840 --> 00:17:09,240 Speaker 1: some of this material. But uh, Chrome notebooks are actually 295 00:17:09,320 --> 00:17:13,600 Speaker 1: going to have data plans from Verizon Wireless up to 296 00:17:13,720 --> 00:17:17,760 Speaker 1: a hundred megabytes of free three G data every month 297 00:17:18,080 --> 00:17:23,520 Speaker 1: for two years. Megas free that much. Um. But but 298 00:17:23,560 --> 00:17:26,280 Speaker 1: then again, these these computers are supposed to have both 299 00:17:26,359 --> 00:17:28,520 Speaker 1: WiFi and three G. So it's not like three G 300 00:17:28,720 --> 00:17:32,359 Speaker 1: is the only way you get data. Like for most people, 301 00:17:32,359 --> 00:17:35,040 Speaker 1: I think WiFi would be the primary way they would 302 00:17:35,040 --> 00:17:37,399 Speaker 1: get data. So as long as you were in someplace 303 00:17:37,400 --> 00:17:39,119 Speaker 1: where there was a WiFi hot spot, you'd be good 304 00:17:39,200 --> 00:17:41,159 Speaker 1: to go. And when you're somewhere where there's not a 305 00:17:41,200 --> 00:17:43,919 Speaker 1: WiFi hot spot, then hopefully you'd be able to access 306 00:17:43,920 --> 00:17:47,120 Speaker 1: a three G data network. Yeah. Plus well, I mean 307 00:17:47,280 --> 00:17:51,399 Speaker 1: WiFi is faster even three G UM. But yes, if 308 00:17:51,440 --> 00:17:54,560 Speaker 1: you want to a limitless day pass, uh, you'd be 309 00:17:54,560 --> 00:17:59,200 Speaker 1: paying per day for three G access or Verizon access. 310 00:17:59,200 --> 00:18:01,639 Speaker 1: I don't know, Maybe it's orgy by next year, and 311 00:18:01,960 --> 00:18:05,400 Speaker 1: depending on when this law launches. Um, if you want 312 00:18:05,400 --> 00:18:10,040 Speaker 1: an additional one gigabyte of information per month, it's twenty dollars. 313 00:18:10,400 --> 00:18:13,960 Speaker 1: Three gigabytes would be thirty five dollars, and five gigabytes 314 00:18:14,000 --> 00:18:18,960 Speaker 1: additional would be fifty dollars per month. So that's pretty hefty. 315 00:18:19,000 --> 00:18:20,879 Speaker 1: If you're planning on doing a lot of computing on 316 00:18:20,880 --> 00:18:23,800 Speaker 1: the road, maybe for business that would be worth it 317 00:18:24,000 --> 00:18:26,080 Speaker 1: because you could probably get reimbursed for that, But if 318 00:18:26,080 --> 00:18:28,560 Speaker 1: this is for personal use, that may not be Uh, 319 00:18:28,880 --> 00:18:31,200 Speaker 1: that may not be the best option for you. Yeah, 320 00:18:31,359 --> 00:18:34,280 Speaker 1: but I mean if you if you're able to click 321 00:18:34,320 --> 00:18:37,639 Speaker 1: in on WiFi networks, like if you've got WiFi hotspots 322 00:18:37,760 --> 00:18:40,600 Speaker 1: or you know, you're mainly using this around your home 323 00:18:40,720 --> 00:18:43,359 Speaker 1: or office, it's not that's not going to be an issue. 324 00:18:43,400 --> 00:18:45,320 Speaker 1: You can just use the WiFi to get access to 325 00:18:45,320 --> 00:18:48,040 Speaker 1: the data and you don't have to worry about incurring fees, 326 00:18:48,440 --> 00:18:50,640 Speaker 1: you know, going over your cap, unless, of course, your 327 00:18:50,840 --> 00:18:54,560 Speaker 1: I s P has a cap for your just your 328 00:18:54,560 --> 00:18:58,520 Speaker 1: regular Internet usage. Some some peas do, and some of 329 00:18:58,560 --> 00:19:01,919 Speaker 1: the caps are I don't know. Relatively, it depends on 330 00:19:01,960 --> 00:19:05,440 Speaker 1: who upon whom you ask. Um. I've heard one person 331 00:19:05,560 --> 00:19:13,000 Speaker 1: sayifty gigabyte cap per month is low, yeah, and for me, 332 00:19:13,080 --> 00:19:17,600 Speaker 1: two gigabytes is more than enough. But then she was 333 00:19:17,640 --> 00:19:20,920 Speaker 1: specifically talking about being able to back up a full 334 00:19:21,359 --> 00:19:24,639 Speaker 1: computer hard drive to the cloud. I think you wouldn't 335 00:19:24,640 --> 00:19:26,720 Speaker 1: be able to do that more than once a month. 336 00:19:26,760 --> 00:19:28,680 Speaker 1: If it were, you know, a really big hard drive 337 00:19:28,720 --> 00:19:32,240 Speaker 1: and you were using a cloud based backup system, then 338 00:19:32,400 --> 00:19:34,680 Speaker 1: you could only do it once or maybe not even once, 339 00:19:34,680 --> 00:19:36,119 Speaker 1: depending on the size of your hard drive. Now I 340 00:19:36,160 --> 00:19:39,639 Speaker 1: can't imagine doing that, um, But then it's because I 341 00:19:39,640 --> 00:19:43,200 Speaker 1: don't tend to use the online data services for backing 342 00:19:43,280 --> 00:19:45,960 Speaker 1: up my hard drive. It's funny you would say that, 343 00:19:46,920 --> 00:19:50,119 Speaker 1: because I would think with the with Google's reputation of 344 00:19:51,280 --> 00:19:54,720 Speaker 1: massive redundancy, and by redundancy if you're not familiar with 345 00:19:54,720 --> 00:19:59,000 Speaker 1: that term, we mean Google servers have lots and lots 346 00:19:59,000 --> 00:20:01,639 Speaker 1: of other servers with the same information on them. So 347 00:20:01,720 --> 00:20:05,879 Speaker 1: if one of them breaks, basically Google is losing nothing 348 00:20:06,040 --> 00:20:08,880 Speaker 1: because it's been the company backs up its own equipment. 349 00:20:08,880 --> 00:20:10,880 Speaker 1: So I would imagine that if you had an account 350 00:20:11,320 --> 00:20:15,119 Speaker 1: and had Google Chromos on your operating system, your information 351 00:20:15,280 --> 00:20:18,520 Speaker 1: would all be backed up automatically by Google. And that 352 00:20:18,680 --> 00:20:22,119 Speaker 1: is one of the things that they have have said that. Um, 353 00:20:22,160 --> 00:20:26,000 Speaker 1: they're they're very strong on privacy. UM, they're very concerned 354 00:20:26,040 --> 00:20:30,840 Speaker 1: with encrypting your information while it's on their servers. UM 355 00:20:30,920 --> 00:20:37,120 Speaker 1: and sand boxing basically keeping viruses at in in a 356 00:20:37,320 --> 00:20:43,080 Speaker 1: h quarantine quarantined environment, uh in order to prevent them 357 00:20:43,119 --> 00:20:47,879 Speaker 1: from infecting the machines and infecting your information, um, you know, 358 00:20:47,920 --> 00:20:52,280 Speaker 1: to the point where it becomes uh um corrupted, prevent 359 00:20:52,320 --> 00:20:55,360 Speaker 1: anything from happening to it. Um you know they're they're 360 00:20:55,400 --> 00:20:57,720 Speaker 1: they're talking those points up, So I would imagine it 361 00:20:57,800 --> 00:21:00,880 Speaker 1: would be pretty safe. That the thing is cloud computing 362 00:21:01,000 --> 00:21:04,560 Speaker 1: has a long running stigma for a lot of people 363 00:21:04,600 --> 00:21:08,440 Speaker 1: that because that information is on you know, a computer 364 00:21:08,600 --> 00:21:11,880 Speaker 1: or even multiple computers out there somewhere where they don't 365 00:21:11,880 --> 00:21:14,280 Speaker 1: know where it is, it concerns them that someone could 366 00:21:14,320 --> 00:21:17,360 Speaker 1: break in and and gain access to that information, possibly 367 00:21:17,440 --> 00:21:21,119 Speaker 1: copy it, uh, sell it to people for for money, 368 00:21:21,160 --> 00:21:23,919 Speaker 1: and who knows what all else. And you've got your 369 00:21:23,920 --> 00:21:27,920 Speaker 1: sensitive information on there. Um Yes, the company, I'm sure 370 00:21:27,960 --> 00:21:30,560 Speaker 1: we'll do its best to protect that information, but it's 371 00:21:30,600 --> 00:21:33,240 Speaker 1: still causes people concerned. And I think that's why you 372 00:21:33,280 --> 00:21:37,320 Speaker 1: see Google saying, hey, look it's all encrypted, it's all safe, 373 00:21:37,359 --> 00:21:39,760 Speaker 1: it's all backed up. You know, no, nothing to worry 374 00:21:39,760 --> 00:21:43,480 Speaker 1: about here. It's a it's a There two sides to 375 00:21:43,560 --> 00:21:47,679 Speaker 1: that story. One side is that companies, big companies like Google, 376 00:21:48,240 --> 00:21:52,040 Speaker 1: we'll be able to afford and design much tighter security 377 00:21:52,040 --> 00:21:55,080 Speaker 1: measures than your average user is going to have access to. 378 00:21:55,160 --> 00:21:58,760 Speaker 1: And most I'm gonna say most users don't aren't nearly 379 00:21:58,800 --> 00:22:01,040 Speaker 1: as secure as they need to be. You know, they 380 00:22:01,280 --> 00:22:04,040 Speaker 1: they have poor password protection. A lot of them are 381 00:22:04,080 --> 00:22:07,439 Speaker 1: using open networks, although I'm seeing fewer cases of that. 382 00:22:07,520 --> 00:22:10,719 Speaker 1: Now I'm seeing more people actually secure their wireless networks, 383 00:22:10,720 --> 00:22:14,080 Speaker 1: which is nice, um, But I mean, it's just that 384 00:22:14,160 --> 00:22:17,119 Speaker 1: people don't tend to practice very strong security measures. So 385 00:22:17,160 --> 00:22:19,720 Speaker 1: you can say, well, Google is going to use state 386 00:22:19,720 --> 00:22:22,320 Speaker 1: of the art security, so that's a good thing. However, 387 00:22:22,400 --> 00:22:26,000 Speaker 1: Google is also a huge company and therefore, by virtue 388 00:22:26,040 --> 00:22:29,680 Speaker 1: of being a big company is a big target. Each 389 00:22:29,760 --> 00:22:33,960 Speaker 1: individual user out there using the Internet is not a 390 00:22:34,040 --> 00:22:36,639 Speaker 1: huge target. Now that that you could still fall prey 391 00:22:36,680 --> 00:22:40,320 Speaker 1: to scams or phishing attempts, that kind of thing, but 392 00:22:40,440 --> 00:22:43,199 Speaker 1: it's not Most of us don't have a target on 393 00:22:43,200 --> 00:22:45,760 Speaker 1: our backs. You know, we aren't walking around with with 394 00:22:45,840 --> 00:22:50,879 Speaker 1: hackers looking to get access specifically to our machine. They 395 00:22:50,920 --> 00:22:54,040 Speaker 1: want access to machines. They don't care who it happens 396 00:22:54,080 --> 00:22:58,600 Speaker 1: to be, right, So you could argue, well, Google's better protected, 397 00:22:58,640 --> 00:23:01,320 Speaker 1: but it's also a more empting targets. So you got 398 00:23:01,400 --> 00:23:04,119 Speaker 1: to weigh both of those things against one another, and 399 00:23:04,160 --> 00:23:07,560 Speaker 1: then you say, well, our Google security measure is going 400 00:23:07,600 --> 00:23:10,240 Speaker 1: to be strong enough so that it doesn't matter that 401 00:23:10,280 --> 00:23:14,080 Speaker 1: Google is a bigger target um or you know, it 402 00:23:14,119 --> 00:23:16,600 Speaker 1: also depends on what you use your computer for. If 403 00:23:16,640 --> 00:23:18,879 Speaker 1: you're not using your computer to do a lot of 404 00:23:18,920 --> 00:23:22,320 Speaker 1: sensitive information kind of stuff. Like if you're not doing 405 00:23:22,359 --> 00:23:25,560 Speaker 1: a lot of online shopping or online banking. Um, if 406 00:23:25,600 --> 00:23:30,080 Speaker 1: you're not, you know, posting secret messages to that gal 407 00:23:30,440 --> 00:23:33,399 Speaker 1: you like who happens to be dating the really huge 408 00:23:33,440 --> 00:23:36,359 Speaker 1: football player and you don't want the football player finding 409 00:23:36,359 --> 00:23:38,360 Speaker 1: out about it, that kind of stuff. Um, if you're 410 00:23:38,359 --> 00:23:40,760 Speaker 1: not doing any of that, then maybe these aren't even 411 00:23:40,760 --> 00:23:45,000 Speaker 1: concerns for you. But if you do tend to put uh, 412 00:23:45,160 --> 00:23:47,119 Speaker 1: like if you do tend to shop online, or you 413 00:23:47,160 --> 00:23:50,880 Speaker 1: do online banking, or you do you know, you you 414 00:23:50,880 --> 00:23:53,840 Speaker 1: you do things like you manage benefits or medical records 415 00:23:53,920 --> 00:23:58,880 Speaker 1: or anything like that online, it becomes a concern. Um, 416 00:23:58,960 --> 00:24:01,720 Speaker 1: there are other concerns to you. I mean, like there's 417 00:24:01,720 --> 00:24:04,159 Speaker 1: always a concern of well, if I lose connection to 418 00:24:04,160 --> 00:24:07,760 Speaker 1: the Internet for some reason, then I lose all access 419 00:24:07,800 --> 00:24:12,400 Speaker 1: to all my data. So let's say that there's some 420 00:24:12,560 --> 00:24:18,320 Speaker 1: massive failure in WiFi and three G service, which at 421 00:24:18,359 --> 00:24:20,920 Speaker 1: this point you're thinking, well, I probably have other things 422 00:24:20,960 --> 00:24:24,479 Speaker 1: to worry about. But if if there were such a problem, 423 00:24:25,119 --> 00:24:27,000 Speaker 1: then you would not be able to access your information 424 00:24:27,040 --> 00:24:29,040 Speaker 1: anymore unless you were able to store at least some 425 00:24:29,119 --> 00:24:31,879 Speaker 1: of it locally to your computer, whereas if you had 426 00:24:31,880 --> 00:24:34,880 Speaker 1: your own computer, assuming that you still had power, you'd 427 00:24:34,880 --> 00:24:36,320 Speaker 1: be able to access that. I don't know that what 428 00:24:36,359 --> 00:24:39,040 Speaker 1: good it's gonna do at that point, with you know, 429 00:24:39,119 --> 00:24:40,919 Speaker 1: the world apparently coming to an end around you, at 430 00:24:41,000 --> 00:24:43,920 Speaker 1: least digitally speaking. But um, it's one of those things 431 00:24:43,920 --> 00:24:48,080 Speaker 1: that people they kind of react to this idea of well, 432 00:24:48,119 --> 00:24:50,119 Speaker 1: there could something could go wrong and I would no 433 00:24:50,200 --> 00:24:54,160 Speaker 1: longer be able to get to the things that are mine. Um. 434 00:24:54,320 --> 00:24:56,399 Speaker 1: And part of that I think is also just a 435 00:24:56,400 --> 00:25:00,080 Speaker 1: sense of ownership, like when when your data rests on 436 00:25:00,119 --> 00:25:02,560 Speaker 1: someone else's machine, it almost feels like you don't own it, 437 00:25:03,359 --> 00:25:07,480 Speaker 1: you know, so it becomes and depending upon the way 438 00:25:08,240 --> 00:25:12,280 Speaker 1: service agreements are worded, sometimes you don't own that at 439 00:25:12,320 --> 00:25:15,239 Speaker 1: least you know, if those agreements were to hold up 440 00:25:15,240 --> 00:25:19,200 Speaker 1: in court. Um, we haven't really seen that play out 441 00:25:19,320 --> 00:25:23,560 Speaker 1: to any extent, like someone come challenging a a uh 442 00:25:23,960 --> 00:25:27,320 Speaker 1: website or service saying okay, well, I know I uploaded 443 00:25:27,320 --> 00:25:29,879 Speaker 1: my photos to your site, but that doesn't mean you 444 00:25:29,920 --> 00:25:32,680 Speaker 1: own them. We'd have to see that kind of played 445 00:25:32,680 --> 00:25:34,159 Speaker 1: out all the way through to find out, you know 446 00:25:34,200 --> 00:25:36,360 Speaker 1: what the courts have to say about that. But I mean, 447 00:25:36,359 --> 00:25:39,320 Speaker 1: these are those issues around cloud computing. It's existed since 448 00:25:39,800 --> 00:25:43,840 Speaker 1: cloud computing really started up as an idea, and they 449 00:25:43,840 --> 00:25:46,080 Speaker 1: have not really all been resolved yet. It's still i 450 00:25:46,119 --> 00:25:51,080 Speaker 1: would say, cloud computing still pretty young concept. Yeah. Yeah, 451 00:25:51,119 --> 00:25:55,119 Speaker 1: And it's funny too. When we started talking about this, 452 00:25:55,359 --> 00:26:01,040 Speaker 1: I I started thinking specifically about Google's compe Titian unwittingly 453 00:26:01,320 --> 00:26:05,320 Speaker 1: helping it because I would say, probably most people aren't 454 00:26:05,359 --> 00:26:10,280 Speaker 1: really aware that there is a Google Chrome OS. UM. 455 00:26:10,320 --> 00:26:11,840 Speaker 1: You know, I think it's out there, but because it 456 00:26:11,840 --> 00:26:15,000 Speaker 1: hasn't actually been released, UM, it's not really on a 457 00:26:15,000 --> 00:26:20,159 Speaker 1: lot of people's radar. Now. Microsoft has currently has a 458 00:26:21,080 --> 00:26:25,560 Speaker 1: uh cloud um ad campaign going on right now talking 459 00:26:25,600 --> 00:26:29,000 Speaker 1: about the benefits of cloud computing and how you can 460 00:26:29,160 --> 00:26:33,359 Speaker 1: use Windows to access information that is stored in the cloud. 461 00:26:34,000 --> 00:26:36,760 Speaker 1: And I think it's kind of funny because right now 462 00:26:37,080 --> 00:26:42,440 Speaker 1: Google's marketing legwork is all being done by it's arguably 463 00:26:42,480 --> 00:26:47,359 Speaker 1: biggest competition, UM. Because once Microsoft educates people about this, 464 00:26:47,400 --> 00:26:52,720 Speaker 1: when Google's Chrome OS is released, UM, they're Google is 465 00:26:52,760 --> 00:26:54,520 Speaker 1: not going to have nearly as much work to do 466 00:26:54,600 --> 00:26:59,639 Speaker 1: explain to to the layman what UH cloud computing is 467 00:26:59,800 --> 00:27:02,720 Speaker 1: and the benefits of using it. They're gonna be able 468 00:27:02,760 --> 00:27:05,840 Speaker 1: to say this is cloud computing Google style, and and 469 00:27:06,280 --> 00:27:08,280 Speaker 1: you know you've already you already know what this is. 470 00:27:09,040 --> 00:27:10,960 Speaker 1: Now here's how we do it, and it's going to 471 00:27:11,000 --> 00:27:14,280 Speaker 1: be faster and better with the Chromos. And I started 472 00:27:14,280 --> 00:27:18,200 Speaker 1: thinking about, wow, you know what, this is completely coincidental, 473 00:27:18,240 --> 00:27:22,400 Speaker 1: I guess, because Microsoft wouldn't necessarily want to promote Google's 474 00:27:22,440 --> 00:27:24,040 Speaker 1: new operating system. But this has come out in the 475 00:27:24,119 --> 00:27:26,960 Speaker 1: last month or two, the ads that I've seen uh 476 00:27:27,080 --> 00:27:30,440 Speaker 1: here late in so I thought about that and thought, 477 00:27:30,480 --> 00:27:32,439 Speaker 1: you know what, that's that's kind of ironic. And I 478 00:27:32,480 --> 00:27:35,639 Speaker 1: wonder if they're going to be regretting having taught people 479 00:27:35,680 --> 00:27:38,480 Speaker 1: with the cloud is now. On the other hand, they've 480 00:27:38,480 --> 00:27:43,639 Speaker 1: got a head start, um, you know, for using cloud 481 00:27:43,680 --> 00:27:46,840 Speaker 1: computing as a marketing tool. But I don't think it's 482 00:27:46,840 --> 00:27:49,959 Speaker 1: going to take Google much longer to get the Chromos 483 00:27:50,000 --> 00:27:52,040 Speaker 1: out the door. And we'll see what happens then. Yeah, 484 00:27:52,080 --> 00:27:54,800 Speaker 1: it's interesting because, um, one other thing I wanted to 485 00:27:54,840 --> 00:27:59,240 Speaker 1: mention something something that published just recently as of the 486 00:27:59,240 --> 00:28:02,840 Speaker 1: recording of this put guess anyway, was an interview on 487 00:28:02,920 --> 00:28:06,640 Speaker 1: Business Insider with Paul Buchite, and I have no idea 488 00:28:06,680 --> 00:28:08,800 Speaker 1: if I said his last name correctly or not. B 489 00:28:08,920 --> 00:28:11,840 Speaker 1: U c h h E I t uh. He was 490 00:28:12,160 --> 00:28:14,520 Speaker 1: an early employee of Google. Yeah, he was one of 491 00:28:14,560 --> 00:28:18,080 Speaker 1: the first twenty five employees. I think something along those lines. 492 00:28:18,119 --> 00:28:20,960 Speaker 1: He was also the guy who was essentially behind Gmail. 493 00:28:21,800 --> 00:28:25,200 Speaker 1: That was his big project, and he left Google. Um. 494 00:28:25,359 --> 00:28:27,359 Speaker 1: He worked with Facebook for a while then left that. 495 00:28:28,080 --> 00:28:31,760 Speaker 1: But he had some interesting things to say about Google 496 00:28:31,800 --> 00:28:33,560 Speaker 1: recently to Business Insider, and one of the things he 497 00:28:33,600 --> 00:28:37,919 Speaker 1: said was he expected Chromos to fail. Yeah, and he 498 00:28:37,960 --> 00:28:42,600 Speaker 1: attributed that not to any inherent flaw with Chromos, but 499 00:28:42,760 --> 00:28:47,080 Speaker 1: rather because the Android operating system has gathered so much 500 00:28:47,120 --> 00:28:52,480 Speaker 1: steam that it's that's going to to cannibalize the Chromos 501 00:28:52,560 --> 00:28:56,560 Speaker 1: operating system. And people are going to say, well, so 502 00:28:56,800 --> 00:28:59,120 Speaker 1: the question we made at the very beginning, why should 503 00:28:59,160 --> 00:29:02,360 Speaker 1: I get Chromos when Android is already out there? Yeah? Yeah, 504 00:29:02,400 --> 00:29:05,160 Speaker 1: Well they are they are designed for different devices. There 505 00:29:05,200 --> 00:29:08,560 Speaker 1: are people who think that mac os ten and iOS 506 00:29:08,600 --> 00:29:11,760 Speaker 1: are going to merge um and I think there are 507 00:29:11,800 --> 00:29:15,080 Speaker 1: some similarities there, but I think there is a benefit 508 00:29:15,120 --> 00:29:17,400 Speaker 1: to keeping them separate, as we were talking about before, 509 00:29:17,440 --> 00:29:20,920 Speaker 1: because the iOS will run on devices that just simply 510 00:29:21,000 --> 00:29:24,200 Speaker 1: cannot run the macOS, and the mac OS is far 511 00:29:24,240 --> 00:29:27,880 Speaker 1: more robust and supports a far greater range of applications 512 00:29:28,600 --> 00:29:31,440 Speaker 1: um and the iOS can ever support, but it needs 513 00:29:31,480 --> 00:29:34,640 Speaker 1: a faster and more heavy duty processor operate and that 514 00:29:34,640 --> 00:29:38,160 Speaker 1: would be uh, that would be sort of similar to 515 00:29:38,200 --> 00:29:41,440 Speaker 1: this situation. But the Chromos isn't really designed to run 516 00:29:41,640 --> 00:29:47,200 Speaker 1: on you know, a desktop, heavy duty machine, a pro 517 00:29:47,320 --> 00:29:50,560 Speaker 1: level machine. Well, and and not all the apps on 518 00:29:50,640 --> 00:29:54,000 Speaker 1: Android are cloud based either. A lot of them exist 519 00:29:54,080 --> 00:29:57,680 Speaker 1: on top of the hardware of the actual handheld device. 520 00:29:57,760 --> 00:30:01,840 Speaker 1: So so it's not exactly the same approach as Chromos 521 00:30:01,880 --> 00:30:04,840 Speaker 1: in the first place. And I'm not sure that the 522 00:30:04,880 --> 00:30:10,280 Speaker 1: Android experience would translate well to a computer, um like 523 00:30:10,320 --> 00:30:12,960 Speaker 1: a like a laptop or or netbook or anything like that. 524 00:30:13,120 --> 00:30:17,400 Speaker 1: It's it's meant for a different kind of of computing. 525 00:30:17,920 --> 00:30:21,880 Speaker 1: And I think, you know, Apple's really proven, uh that 526 00:30:22,760 --> 00:30:25,920 Speaker 1: there are two different ways to use these kind of devices. 527 00:30:25,920 --> 00:30:28,200 Speaker 1: And I say that because the success of the iPad, 528 00:30:28,960 --> 00:30:33,360 Speaker 1: because Steve Jobs recognize that there there's a mobile way 529 00:30:33,400 --> 00:30:36,520 Speaker 1: of browsing the Internet and using a computing device that 530 00:30:36,720 --> 00:30:39,840 Speaker 1: is a lot different from the computer approach, which I 531 00:30:39,880 --> 00:30:43,280 Speaker 1: would argue, is why there are you know, why the 532 00:30:43,320 --> 00:30:47,640 Speaker 1: iPad uses iOS instead of a version of macOS because 533 00:30:47,640 --> 00:30:50,800 Speaker 1: it you know, it's designed to do computing in a 534 00:30:50,840 --> 00:30:54,680 Speaker 1: different way. So we'll see if the chromos is going 535 00:30:54,720 --> 00:30:56,600 Speaker 1: to make an impact. I mean it's early days yet, 536 00:30:56,600 --> 00:30:59,680 Speaker 1: the beta program just launched. As of the recording of 537 00:30:59,680 --> 00:31:02,680 Speaker 1: this pod, guest Um, I actually applied for it. I 538 00:31:02,720 --> 00:31:06,280 Speaker 1: have not received my CR forty eight yet. Um. Actually, 539 00:31:06,320 --> 00:31:08,440 Speaker 1: I have no idea if they would even pick me. 540 00:31:08,920 --> 00:31:10,720 Speaker 1: I would love to get my hands on one just 541 00:31:10,760 --> 00:31:13,240 Speaker 1: to try it out and you know, see see exactly 542 00:31:13,600 --> 00:31:15,600 Speaker 1: you know what I can do and what I can't do, 543 00:31:16,480 --> 00:31:20,200 Speaker 1: and and really take it for a spin. Plus, I 544 00:31:20,200 --> 00:31:23,640 Speaker 1: think that the it's kind of got an appealing bare 545 00:31:23,720 --> 00:31:26,920 Speaker 1: bones designed to that laptop, right, And that's one of 546 00:31:26,920 --> 00:31:29,360 Speaker 1: the other elements that we didn't really address here, um, 547 00:31:29,520 --> 00:31:31,280 Speaker 1: but we can. We can just mention it very quickly 548 00:31:31,320 --> 00:31:34,600 Speaker 1: before we wrap up. One of the reasons why a 549 00:31:34,760 --> 00:31:38,080 Speaker 1: cloud based operating system may be really attractive is that 550 00:31:38,120 --> 00:31:41,520 Speaker 1: you don't have to have such advanced hardware, so you 551 00:31:41,560 --> 00:31:44,920 Speaker 1: can have cheaper computers because you know, you don't have 552 00:31:44,960 --> 00:31:47,320 Speaker 1: to have a computer capable of running of really you know, 553 00:31:47,880 --> 00:31:51,040 Speaker 1: processor heavy operating system, so you don't need the most 554 00:31:51,040 --> 00:31:54,080 Speaker 1: advanced processor, you don't need all those uh you know, 555 00:31:55,040 --> 00:31:57,160 Speaker 1: if your processor is not gonna be running super hot, 556 00:31:57,160 --> 00:32:00,240 Speaker 1: you're not gonna need great ventilation and fans. I mean, 557 00:32:00,320 --> 00:32:04,040 Speaker 1: you start to really cut down on the costs for 558 00:32:04,160 --> 00:32:11,040 Speaker 1: the devices, which can in theory make computing even cheaper. Well. Um, 559 00:32:11,240 --> 00:32:14,000 Speaker 1: and another thing that that I wanted to address really 560 00:32:14,040 --> 00:32:17,360 Speaker 1: quickly is and then we didn't really cover the whole thing. 561 00:32:17,480 --> 00:32:22,200 Speaker 1: It's really strange. It's Linux based, but everything runs essentially 562 00:32:22,320 --> 00:32:25,840 Speaker 1: out of the Chrome browser. The Chrome browser is a 563 00:32:25,840 --> 00:32:29,120 Speaker 1: building block of the Chromos And I'm still interested to 564 00:32:29,120 --> 00:32:32,600 Speaker 1: see again, if you were accepted to the program, the 565 00:32:32,640 --> 00:32:35,720 Speaker 1: beta program, I would like to see how you're supposed 566 00:32:35,760 --> 00:32:40,160 Speaker 1: to run other applications on that platform. If everything runs 567 00:32:40,240 --> 00:32:45,440 Speaker 1: essentially through the the Chrome browser, how other applications factor 568 00:32:45,480 --> 00:32:48,160 Speaker 1: into that. And I'm used to things like Google Docs 569 00:32:48,240 --> 00:32:50,920 Speaker 1: or Aviary or you know, Photoshop dot com, things that 570 00:32:51,000 --> 00:32:53,360 Speaker 1: you can do where they are applications, but they are 571 00:32:53,480 --> 00:32:58,360 Speaker 1: essentially on the web already. If you're installing theoretically installing 572 00:32:58,920 --> 00:33:02,960 Speaker 1: other applications into your Chromos experience, how does that work exactly? 573 00:33:03,000 --> 00:33:05,160 Speaker 1: Do you do you go to a website or does 574 00:33:05,200 --> 00:33:07,960 Speaker 1: it run alongside the browser. I'm interested to see how 575 00:33:08,000 --> 00:33:11,080 Speaker 1: that works. It's it's difficult for me to understand without 576 00:33:11,120 --> 00:33:13,920 Speaker 1: actually having an opportunity to try it out for myself, 577 00:33:14,000 --> 00:33:15,640 Speaker 1: and I think a lot of our our listeners would 578 00:33:15,680 --> 00:33:18,680 Speaker 1: probably agree it's it's kind of a different concept and 579 00:33:18,680 --> 00:33:20,960 Speaker 1: it might require a hands on approach to really get it. 580 00:33:21,080 --> 00:33:23,040 Speaker 1: I'm pretty sure a few of them already have this 581 00:33:23,320 --> 00:33:26,640 Speaker 1: computer actually, based upon emails that I've received. Well, they 582 00:33:26,680 --> 00:33:30,880 Speaker 1: need to tell us what's going on. Yeah, yeah, you 583 00:33:30,920 --> 00:33:34,520 Speaker 1: guys gotta hook hook us up. You know we we 584 00:33:34,600 --> 00:33:38,800 Speaker 1: do not have the bat line directly into Google headquarters, Yes, Commissioner, 585 00:33:38,880 --> 00:33:41,160 Speaker 1: not anymore. Yeah, yeah, that was a couple of years 586 00:33:41,200 --> 00:33:45,160 Speaker 1: ago when we had that. Yeah, it's pretty cool. So 587 00:33:45,320 --> 00:33:48,400 Speaker 1: that it all communicated in high pitched squeaks beyond the 588 00:33:48,480 --> 00:33:51,360 Speaker 1: range of human hearing. That was a little irritating. Beyond that, 589 00:33:51,440 --> 00:33:53,280 Speaker 1: it was awesome, And they expected us to know what 590 00:33:53,320 --> 00:33:57,720 Speaker 1: was going on down They need to start listening to 591 00:33:57,880 --> 00:34:00,200 Speaker 1: our podcast more often and they would know you have 592 00:34:00,440 --> 00:34:03,680 Speaker 1: no idea what's going on? All right, Well, with that, 593 00:34:04,000 --> 00:34:07,400 Speaker 1: let's wrap this up. This was another fun episode. If 594 00:34:07,400 --> 00:34:09,879 Speaker 1: you guys have any suggestions for topics, or you want 595 00:34:09,880 --> 00:34:13,400 Speaker 1: to chime in on a discussion about chromos and cloud computing, 596 00:34:14,160 --> 00:34:17,000 Speaker 1: let us know on Facebook and Twitter are handle There 597 00:34:17,120 --> 00:34:20,720 Speaker 1: is text stuff h s W or you can shoot 598 00:34:20,800 --> 00:34:23,600 Speaker 1: us an email. That address is tech stuff at how 599 00:34:23,680 --> 00:34:26,000 Speaker 1: stuff works dot com and Chris and I will talk 600 00:34:26,000 --> 00:34:30,480 Speaker 1: to you again really soon. For more on this and 601 00:34:30,600 --> 00:34:33,279 Speaker 1: thousands of other topics, visit how stuff works dot com. 602 00:34:33,480 --> 00:34:36,160 Speaker 1: To learn more about the podcast, click on the podcast 603 00:34:36,320 --> 00:34:39,680 Speaker 1: icon in the upper right corner of our homepage. The 604 00:34:39,760 --> 00:34:42,760 Speaker 1: house stuff Works iPhone app has arrived. Download it today 605 00:34:43,000 --> 00:34:50,440 Speaker 1: on iTunes, brought to you by the reinvented two thousand 606 00:34:50,440 --> 00:34:52,640 Speaker 1: twelve camera. It's ready, are you