WEBVTT - TechStuff Looks at Windows 8 0:00:00.280 --> 0:00:02.960 Brought to you by the reinvented two thousand twelve Camray. 0:00:03.160 --> 0:00:08.880 It's ready. Are you get in touch with technology? With 0:00:09.000 --> 0:00:17.520 tech Stuff from how stuff works dot com. Hello everyone, 0:00:17.560 --> 0:00:20.400 Welcome to tech stuff. My name is Chris Poulette and 0:00:20.440 --> 0:00:22.600 I'm an editor at how stuff works dot com. Sitting 0:00:22.600 --> 0:00:25.439 across from me, as he always does, is senior writer 0:00:25.520 --> 0:00:32.360 Jonathan Strickland. Come to my window. I'll be home soon. Ah, yes, 0:00:32.440 --> 0:00:36.840 because today we are talking about the next iteration of 0:00:36.880 --> 0:00:41.080 the Microsoft computer operating system. Well, actually that's sort of 0:00:41.080 --> 0:00:42.880 a misnumber, but we'll get into that in a second, 0:00:43.360 --> 0:00:45.680 or what we know about it since it's so far 0:00:45.760 --> 0:00:50.080 from release. By the developer release it's Windows eight, which 0:00:50.120 --> 0:00:51.879 is actually just a code name. It may not be 0:00:52.040 --> 0:00:55.040 called that once it hits the market sometime in the year. 0:00:56.080 --> 0:01:00.760 I'm hoping it'll be called Susan, but I doubt it. Um. 0:01:01.200 --> 0:01:04.840 Mr Ballmer said, get away from him and os named Sue. Yes. 0:01:05.160 --> 0:01:09.080 Nice a little man in black action right there. Um 0:01:09.200 --> 0:01:12.760 so yeah, we're just trying to cash in. Thanks. We 0:01:12.840 --> 0:01:16.000 don't even really know a whole lot about this upbring system. 0:01:16.040 --> 0:01:19.920 We know bits and pieces. Um ha ha bits. I 0:01:19.959 --> 0:01:23.600 see what I did there, but it's really a lot 0:01:23.640 --> 0:01:26.680 of it will be revealed further down the line. And 0:01:26.720 --> 0:01:30.040 of course you may be listening to this, in which 0:01:30.080 --> 0:01:33.880 case you're thinking, oh, wow, boy, did they get that wrong. 0:01:34.319 --> 0:01:36.880 It's not our fault. We still we still get every 0:01:36.920 --> 0:01:39.479 once in a while we'll get a comment on our 0:01:39.600 --> 0:01:42.360 challenge for people to tell us what all seven versions 0:01:42.360 --> 0:01:47.000 of Windows were. Yeah, because there are more than just seven. 0:01:47.000 --> 0:01:49.400 And it's funny because we always get messages like no, no, 0:01:49.520 --> 0:01:51.920 you're wrong. I'm like, no, I'm not wrong. I took 0:01:51.960 --> 0:01:54.800 this directly from Microsoft, So I mean, if I'm wrong, 0:01:55.280 --> 0:01:58.520 Microsoft's wrong, and they're the ones naming it, so take 0:01:58.560 --> 0:02:00.680 it up with them. So Windows eight right now, we're 0:02:00.720 --> 0:02:02.800 just calling it that we know it's because it's the 0:02:02.840 --> 0:02:07.000 Windows after Windows seven. Yes, but who knows what wacky 0:02:07.080 --> 0:02:09.119 name it will have when it comes out. But it's 0:02:09.200 --> 0:02:11.840 really if you've if you've seen any pictures of it 0:02:11.919 --> 0:02:14.920 or seen any video of it, it's actually a pretty 0:02:15.040 --> 0:02:19.800 significant departure from the way the Windows operating system works 0:02:19.880 --> 0:02:24.120 right now. I mean it's it's like Windows seven wasn't 0:02:25.600 --> 0:02:30.000 such a huge change from the previous versions of Windows 0:02:30.000 --> 0:02:32.280 that you felt like you were looking at something totally different. 0:02:33.000 --> 0:02:36.959 But Windows eight kind of is. Oh yeah, well, I'm 0:02:36.960 --> 0:02:39.800 actually surprised you didn't quote Berlin at the beginning of 0:02:39.840 --> 0:02:45.240 this um, because it would be appropriate in this particular instance. 0:02:45.320 --> 0:02:50.160 Now see Windows eight is right now, uh sort of 0:02:51.040 --> 0:02:55.600 going back to one of Jonathan's old favorite words, convergence. Yeah, 0:02:55.639 --> 0:03:00.680 because it's really uh apparently isn't as say, apparently, of 0:03:00.680 --> 0:03:02.800 course we're we're still going on what we know of 0:03:02.840 --> 0:03:05.600 the operating system and things change, you know, but it 0:03:05.639 --> 0:03:09.239 apparently is designed to be sort of a go between 0:03:09.440 --> 0:03:15.360 for Windows mobile devices, not Windows mobile devices, but no 0:03:15.600 --> 0:03:19.919 mobile devices that use Windows and computers that run with 0:03:20.280 --> 0:03:23.880 desktops and laptops. Yeah, it's actually really interesting to me. 0:03:23.880 --> 0:03:26.560 I'm glad that you brought that up, because you could 0:03:26.639 --> 0:03:31.160 argue that up to a certain point, the smartphone operating 0:03:31.200 --> 0:03:33.959 systems that you encounter, and even the tablet operating systems 0:03:34.000 --> 0:03:39.040 you encounter, are trying to emulate the operating systems you 0:03:39.080 --> 0:03:42.400 find on desktops and laptops, at least as much as 0:03:42.440 --> 0:03:46.320 they can, given the limitations of the form factor of 0:03:46.360 --> 0:03:49.720 smartphones and tablets. Right, I mean, you want you want 0:03:49.800 --> 0:03:52.840 something that's acting as a foundation for programs, and you 0:03:52.880 --> 0:03:55.800 want something that's easy to navigate and to you know, 0:03:55.880 --> 0:03:59.480 you want a certain UH file system built into their 0:04:00.240 --> 0:04:04.680 A lot of the the models for the operating systems 0:04:04.680 --> 0:04:07.360 for these mobile devices are based, at least in part 0:04:07.520 --> 0:04:12.320 off of desktop systems. And here we're seeing a fully 0:04:12.440 --> 0:04:16.960 fledged operating system that presumably will be on desktops and 0:04:17.120 --> 0:04:21.440 laptops that is starting to emulate what we find on 0:04:21.520 --> 0:04:25.520 mobile devices. So the two are coming together. It's just that, 0:04:25.880 --> 0:04:29.000 you know, while you might have expected the operating systems 0:04:29.000 --> 0:04:31.480 for mobile devices to get more and more sophisticated and 0:04:31.600 --> 0:04:35.560 approach the what we have for desktops and laptops, it 0:04:35.560 --> 0:04:38.719 looks like it's more like, at least when Microsoft's approach 0:04:38.839 --> 0:04:41.919 is to make the desktop laptop more like the mobile. 0:04:42.520 --> 0:04:44.559 And it might be because we are entering this post 0:04:44.560 --> 0:04:48.080 PC era where people are getting more used to interacting 0:04:48.480 --> 0:04:53.279 with an operating system in this sort of mobile model. Yeah. 0:04:53.360 --> 0:04:56.800 The when I was making my comment about Berlin that's 0:04:56.880 --> 0:05:00.320 the band, not the city, um yeah, earlier it's because 0:05:00.360 --> 0:05:04.880 they had a hit with a song Metro and the 0:05:05.400 --> 0:05:08.880 if you've seen if you've not actually held one of 0:05:08.880 --> 0:05:13.480 the UH more recent Windows phones using the latest version 0:05:13.480 --> 0:05:18.400 of Microsoft software. Um, if you see the commercials at 0:05:18.480 --> 0:05:21.599 least where you see the little different colorful boxes that 0:05:21.680 --> 0:05:23.920 you use to operate the operating system, that's what they 0:05:23.960 --> 0:05:29.400 call the metro interface, and Windows eight appears to be 0:05:29.480 --> 0:05:32.880 trying to bring that to the desktop and laptop as well. 0:05:33.320 --> 0:05:35.680 Now I think from what I've read, it looks like 0:05:35.800 --> 0:05:37.719 you will have the option to go to a more 0:05:37.760 --> 0:05:42.160 traditional looking Windows interface, but they're really pushing the metro look. Yeah, 0:05:42.160 --> 0:05:46.039 so if you turn on a smartphone or or tablet 0:05:46.279 --> 0:05:49.599 something like that. UH. And you know, every operating system 0:05:49.640 --> 0:05:53.720 has its own own features and its own UH traits, 0:05:54.040 --> 0:05:57.160 but in general, they all have a very similar kind 0:05:57.160 --> 0:05:59.560 of approach. And that You've got these icons that are 0:05:59.600 --> 0:06:02.960 on the green, and you select an icon by touching it, 0:06:03.040 --> 0:06:05.279 and that opens up an app and then you use 0:06:05.400 --> 0:06:10.960 various gestures to uh to execute commands within that app 0:06:11.480 --> 0:06:13.440 and UH and you know, this is something that people 0:06:13.480 --> 0:06:16.480 grasp pretty quickly. And in fact, I've heard a lot 0:06:16.520 --> 0:06:20.600 of anecdotal evidence that kids pick up on this really 0:06:20.640 --> 0:06:23.320 really fast. Oh I can, I can. Yeah, it's more 0:06:23.360 --> 0:06:26.320 than just anecdotal. Yeah, I could say this from personal experience. Well, 0:06:26.320 --> 0:06:29.960 that's still anecdotal. It's pretty well you didn't. I didn't 0:06:30.000 --> 0:06:34.679 do a double blind test, did you. Well that's true, okay, okay, 0:06:34.720 --> 0:06:36.880 so but yeah, no, I get it. You've got personal 0:06:36.920 --> 0:06:39.599 experience now for me. For me, it's all secondhand because 0:06:40.000 --> 0:06:42.719 you know, my dogs still don't get a touch interface. 0:06:43.400 --> 0:06:46.640 My cats do. Yeah, uh no, my dogs just don't 0:06:46.680 --> 0:06:51.760 care the But yeah, the point being that this interface 0:06:51.800 --> 0:06:54.920 seems to be very intuitive, very easy to pick up, 0:06:54.960 --> 0:06:59.839 and the louring curve is so easy that unlike traditional 0:07:00.040 --> 0:07:03.440 brain systems, especially old operating systems, you know, you don't 0:07:03.520 --> 0:07:06.680 have that huge barrier to be able to pick up 0:07:06.720 --> 0:07:09.600 a device and just start working on it um And 0:07:09.680 --> 0:07:12.440 that's kind of the approach with this metro system. And 0:07:12.480 --> 0:07:17.520 in fact, the Windows eight operating system is built with 0:07:17.800 --> 0:07:22.960 touch screens in mind, at least partially. Now that you know, 0:07:23.640 --> 0:07:25.480 it's pretty safe to assume that we're going to see 0:07:25.520 --> 0:07:28.320 a lot of different devices you touch screens in the 0:07:28.400 --> 0:07:32.080 in the near future, including things like desktops and laptops 0:07:32.080 --> 0:07:35.200 that you can find them already on the market, right. Yeah, 0:07:35.320 --> 0:07:38.480 So you've got these these devices that traditionally did not 0:07:38.680 --> 0:07:41.239 use touch screens. You're just worried about using a keyboard 0:07:41.240 --> 0:07:43.160 and a mouse. Well, now you've got some out there 0:07:43.200 --> 0:07:45.240 that have touch screens, and Windows eight is meant to 0:07:45.400 --> 0:07:49.240 leverage that and make that a a pivotal part of 0:07:49.280 --> 0:07:52.040 your experience on Windows eight. Now that's not to say 0:07:52.080 --> 0:07:55.760 you can't navigate through Windows eight with a keyboard and mouse. 0:07:55.800 --> 0:07:58.920 You you can. It's just that you're not going to 0:07:59.000 --> 0:08:01.720 have you know, the gestures that you would use on 0:08:01.760 --> 0:08:04.960 a screen are going to translate into different commands that 0:08:05.000 --> 0:08:08.119 you'll use with a keyboard and mouse. So the stuff 0:08:08.120 --> 0:08:10.320 that would be really intuitive if you had a touch 0:08:10.400 --> 0:08:15.080 screen might be a little more complex if you're using 0:08:15.120 --> 0:08:18.240 the traditional mouse and keyboard set up. So, but but 0:08:18.320 --> 0:08:21.880 since we're moving towards that touch screen world, it's not 0:08:21.920 --> 0:08:24.280 really something to be concerned about, especially since Windows eight 0:08:24.320 --> 0:08:27.040 is not gonna be released until when we're gonna have 0:08:27.080 --> 0:08:31.120 even more products out there with touch screens. Yeah, I 0:08:31.160 --> 0:08:33.320 was going to uh, I was gonna say too that 0:08:33.600 --> 0:08:38.320 um uh, you could tell that they're they're they're just 0:08:38.440 --> 0:08:44.120 the paradigm. The whole entire paradigm is designed for that too, because, um, 0:08:44.240 --> 0:08:47.720 where the doc used to be on the traditional interface, 0:08:47.920 --> 0:08:52.000 it's actually moved over to the left, but I think 0:08:52.000 --> 0:08:53.920 it's silly. Well I don't know that this is the 0:08:53.960 --> 0:08:58.800 actual proper word, but i've seen those, uh the icons 0:08:58.840 --> 0:09:02.040 referred to as charm. Yes, no, that's that's the official 0:09:03.760 --> 0:09:07.640 was the set of icons on the Edge user interface 0:09:07.920 --> 0:09:11.160 which disappears right and you actually use a gesture to 0:09:11.480 --> 0:09:15.000 move it over. You swipe the screen from the edge 0:09:15.040 --> 0:09:17.840 toward the interior, and that will bring up the Edge 0:09:17.960 --> 0:09:22.480 user interface, which has a set of five icons called charms, 0:09:23.400 --> 0:09:27.280 and those charms have relate to specific commands like search. 0:09:27.960 --> 0:09:31.240 So let's say you're in your inside an app. You know, 0:09:31.280 --> 0:09:33.120 it's not just when you're in the operating system, although 0:09:33.160 --> 0:09:35.559 it works that way too. Let's say you're inside an 0:09:35.559 --> 0:09:38.000 app or inside a document and you want to search 0:09:38.080 --> 0:09:41.000 that document for something. You could do that swipe gesture 0:09:41.040 --> 0:09:42.920 and it would pull up those basic commands and you 0:09:42.960 --> 0:09:46.000 can search that way. Um, but you it also works 0:09:46.040 --> 0:09:48.480 within the operating system itself. So you're just looking at 0:09:48.520 --> 0:09:51.320 the OS view and you do that that swipe and 0:09:51.360 --> 0:09:53.760 you can search for something just like you could. You know, 0:09:53.800 --> 0:09:56.800 and Windows that has the Windows Search that's in the 0:09:56.840 --> 0:09:59.200 operating system. It's the same basic thing. It's just built 0:09:59.240 --> 0:10:03.800 in a a different the interface is different, but the 0:10:03.800 --> 0:10:09.319 the actual application does the same thing. It's always done. UM. 0:10:09.480 --> 0:10:13.000 You can also swipe to get a menu bar UM. 0:10:13.120 --> 0:10:16.959 You get different different sets of information from UH. Well, 0:10:16.960 --> 0:10:19.240 actually if you do from the top or bottom of 0:10:19.360 --> 0:10:22.160 the screen, you should get a list of commands basically 0:10:22.240 --> 0:10:25.720 contextual commands that you can use in that particular instance, 0:10:25.800 --> 0:10:27.560 depending on what it is that you're doing. And the 0:10:27.559 --> 0:10:30.880 apps are full screen, so you know, you're that's that's 0:10:30.960 --> 0:10:33.800 what you're gonna see when you're using the Metro and 0:10:33.800 --> 0:10:37.640 you're using there are two different basic types of apps. 0:10:38.120 --> 0:10:41.240 They're there are metro apps, which are kind of what 0:10:41.280 --> 0:10:44.120 we think of when we think of smartphone or tablet apps. 0:10:44.760 --> 0:10:48.160 You know, these are they tend to be lightweight. They're 0:10:48.200 --> 0:10:51.880 designed to run within something called Windows run time, which 0:10:51.920 --> 0:10:57.280 is a virtual environment. UM. And they're written in HTML 0:10:57.360 --> 0:11:01.280 five or or dot Net programming language. I believe, Yeah, 0:11:01.280 --> 0:11:03.000 I was gonna say, you can. You can also use 0:11:03.000 --> 0:11:06.200 the C family see C plus plus, C sharp, UH 0:11:06.240 --> 0:11:09.520 and Visual Basic. So these tend to be a little 0:11:09.600 --> 0:11:12.880 more lightweight in the sense of, you know, they're they're 0:11:12.920 --> 0:11:15.439 not going to have the full, huge amount of features 0:11:15.440 --> 0:11:18.760 that you're used to with what the second type of 0:11:18.800 --> 0:11:22.439 app is called, which is the legacy apps. Legacy apps 0:11:22.440 --> 0:11:25.120 would be things like if you wanted to use the 0:11:25.200 --> 0:11:28.880 full Microsoft Office suite with all of the features that 0:11:28.960 --> 0:11:31.720 come with Microsoft Office, that's more of a legacy app 0:11:31.760 --> 0:11:35.000 because it's got a lot more depth and breadth to 0:11:35.160 --> 0:11:38.560 it than a typical UH app would have. You know, 0:11:38.640 --> 0:11:41.000 you might be able to get like a simple word 0:11:41.080 --> 0:11:45.960 processing app as well, which would have limited features compared 0:11:46.000 --> 0:11:48.200 to all the ones you would get with Microsoft Office. 0:11:49.000 --> 0:11:50.839 But Windows A will be able to run both of them. 0:11:50.880 --> 0:11:53.200 It's just that the metro one that's kind of what 0:11:53.920 --> 0:11:56.240 it's tuned to. And in a way this makes sense 0:11:56.280 --> 0:11:58.760 to me because, as we've talked about so many times 0:11:58.760 --> 0:12:03.280 in this podcast, UH, cloud computing is is not going 0:12:03.320 --> 0:12:06.800 away anytime real soon now, right. So I mean, so, 0:12:06.840 --> 0:12:09.520 if you build an operating system that can take advantage 0:12:09.520 --> 0:12:12.360 of cloud computing, and that the apps on the operating 0:12:12.360 --> 0:12:16.160 system itself are very lightweight and don't require a lot 0:12:16.320 --> 0:12:19.559 of resources, you can offload a lot of the heavy 0:12:19.600 --> 0:12:23.360 lifting to the cloud, and you don't need as many 0:12:24.200 --> 0:12:29.680 really heavy duty programs on the device. Itself, right, you know, 0:12:29.760 --> 0:12:32.640 you just have like a very thin client that works 0:12:32.679 --> 0:12:36.800 with this cloud computer system. And um, I think it's 0:12:36.840 --> 0:12:39.160 interesting that Windows eight really seems to be embracing that 0:12:39.160 --> 0:12:41.560 because when you think about Microsoft, I mean, that's a 0:12:41.600 --> 0:12:48.680 software company. They're all about making those really uh rich 0:12:49.160 --> 0:12:52.480 software applications. I was going to use the word compelling, 0:12:52.480 --> 0:12:54.960 but it's kind of hard to talk about spreadsheets being 0:12:55.040 --> 0:12:58.920 compelling the average person. Well, yeah, I mean the operating 0:12:58.960 --> 0:13:02.319 system and the Fist suite are Microsoft's meat and potatoes, 0:13:03.160 --> 0:13:07.679 if you will. Um, so, I mean they they have 0:13:07.840 --> 0:13:12.120 every reason to uh continue to update in and protect 0:13:12.160 --> 0:13:14.839 those products because they are they bring in quite a 0:13:14.880 --> 0:13:18.000 bit of income. But it is interesting to note though 0:13:18.000 --> 0:13:20.720 that there that it appears at this point that there's 0:13:20.720 --> 0:13:24.280 going to be just one version of Windows moving forward, 0:13:24.400 --> 0:13:26.240 rather than the multiple versions we've seen in the last 0:13:26.240 --> 0:13:29.320 couple of iterations. And that version is going to be 0:13:29.720 --> 0:13:32.000 is going to have to work on both Arm and 0:13:32.200 --> 0:13:37.240 Intel's process Yeah. That that is new. Um, before the 0:13:37.280 --> 0:13:40.720 Windows were just run on anything that's running on x 0:13:40.760 --> 0:13:45.000 A D six architecture, and uh now it's gonna be 0:13:45.080 --> 0:13:49.000 running on ARM processors, which are that's that's new that's 0:13:49.040 --> 0:13:52.720 kind of interesting. Um it's it's actually that coused a 0:13:52.720 --> 0:13:56.440 little bit of stir when it was announced because uh, 0:13:56.600 --> 0:13:59.960 there was there was a lot of discussion about Google 0:14:00.240 --> 0:14:03.560 working with Intel and Microsoft maybe getting away from Intel 0:14:03.600 --> 0:14:05.719 a little bit, and it just it's one of those 0:14:05.720 --> 0:14:08.720 things where everyone's looking around wondering what's happening next in 0:14:08.760 --> 0:14:11.520 this in the world of of computers, because these are 0:14:11.640 --> 0:14:17.319 relationships that span many years. Um. But anyway, they there 0:14:17.320 --> 0:14:19.600 are there some some other interesting things about Windows eight 0:14:19.600 --> 0:14:22.200 that I thought kind of you know, just like other 0:14:22.320 --> 0:14:25.720 versions of Windows, you can run multiple processes all at 0:14:25.720 --> 0:14:29.000 the same time. You can multitask in other words, and 0:14:29.080 --> 0:14:32.520 you can flip between the processes, so with a gesture 0:14:32.560 --> 0:14:34.840 you can go from one to another, which you know 0:14:34.920 --> 0:14:37.960 for those old time Windows users they're you know, doing 0:14:38.480 --> 0:14:41.640 all tab all tab to go between. That still works 0:14:41.640 --> 0:14:48.040 on the keyboard. And you can also snap, oh sap. Snapping. 0:14:48.360 --> 0:14:50.400 Snapping though is kind of like flipping. Like flipping would 0:14:50.400 --> 0:14:55.440 be a little casual uh flick from uh the leftmost 0:14:55.520 --> 0:14:57.000 edge of the screen and you flick it over and 0:14:57.040 --> 0:15:01.040 you've got a new um um app showing up. Snap 0:15:01.120 --> 0:15:04.080 is where you hold your fingers against the screen while 0:15:04.080 --> 0:15:06.320 you do this, and it will pull up a side 0:15:06.320 --> 0:15:10.200 by side view of two apps. So that way you 0:15:10.200 --> 0:15:12.680 can have multiple apps on the screen at one time. 0:15:12.720 --> 0:15:14.880 Because yeah, the apps, like like Chris said, these are 0:15:14.920 --> 0:15:17.720 apps that are designed to go full screen. But if 0:15:17.760 --> 0:15:20.520 you want to have multiple apps on your screen at once, 0:15:20.600 --> 0:15:23.440 you can do that. Um. I've seen people who are 0:15:23.480 --> 0:15:26.080 really good at this, who have you know, They'll have 0:15:26.160 --> 0:15:30.800 multiple screens, multiple monitors, and then I'll have multiple applications 0:15:30.800 --> 0:15:33.440 open on each monitor and they're like doing this weird 0:15:34.240 --> 0:15:37.320 uh minority report thing where they're just looking at all that. 0:15:37.560 --> 0:15:40.440 I can't do that. I have to have a single 0:15:40.520 --> 0:15:44.440 app per screen. I cannot have. I can't stand to 0:15:44.560 --> 0:15:48.240 have multiple apps in view on a screen at the 0:15:48.240 --> 0:15:51.680 same time. I want as much screen real estate per 0:15:51.720 --> 0:15:56.040 app as I possibly can get. I don't. It's just 0:15:56.080 --> 0:15:59.800 the way I'm wired. I can't. I can't handle it otherwise. 0:16:00.040 --> 0:16:02.040 So like if you see someone working in a smaller 0:16:02.040 --> 0:16:04.360 window in a word processor and they've got another window 0:16:04.400 --> 0:16:08.440 open with other stuff, and I I don't understand you. 0:16:08.440 --> 0:16:11.240 You must be from a different planet because that is 0:16:11.240 --> 0:16:15.000 not how I work. Um. But anyway, so you can 0:16:15.080 --> 0:16:19.040 still multitask on Windows eight. Uh, it's the developer one 0:16:19.080 --> 0:16:23.720 has a beta version of Internet Explorer ten included, which 0:16:24.920 --> 0:16:30.120 upon the beta launch did not support extensions, so you 0:16:30.160 --> 0:16:35.960 could not run flash in it. Yes, and I'm told, well, okay, 0:16:36.200 --> 0:16:39.800 I've read some information about that that suggests that that 0:16:40.480 --> 0:16:44.240 may not go away. Yes, So that might not because 0:16:44.280 --> 0:16:47.040 they haven't put it in yet. It might be intentionally 0:16:47.120 --> 0:16:51.360 left out. It might mean that Microsoft, like another big 0:16:51.560 --> 0:16:56.640 computer company that rhymes with Shmapple, has decided to really 0:16:56.720 --> 0:17:05.040 back HTML five over the various UH platforms that extend 0:17:05.280 --> 0:17:10.080 ht ML's usability. UM like like flash. Flash should be 0:17:10.119 --> 0:17:12.639 the big example. There's so many websites out there that 0:17:12.680 --> 0:17:18.160 depend on flash to deliver the content to you. And Uh, 0:17:18.200 --> 0:17:21.639 there's a problem with these extensions. The main problem is 0:17:21.680 --> 0:17:26.840 that they introduce the possibility of security vulnerabilities because they 0:17:26.840 --> 0:17:30.960 are beyond the control of the the company that is 0:17:31.000 --> 0:17:34.680 providing either the operating system or the browser. Yes. So 0:17:35.200 --> 0:17:38.680 if you've introduced vulnerabilities through these extensions, then you are 0:17:39.560 --> 0:17:42.360 putting your customer base in danger. So the idea behind 0:17:42.480 --> 0:17:46.119 HTML five is that HTML five will natively support these 0:17:46.440 --> 0:17:50.280 features that previously were not supported in HTML, thus the 0:17:50.400 --> 0:17:54.359 need for extensions, and then you don't have to worry 0:17:54.400 --> 0:17:57.320 about mucking around with your web browser and adding in 0:17:57.560 --> 0:18:01.760 elements that could create vulnerabilities. Mucky mucky muckey. So Internet 0:18:01.760 --> 0:18:07.400 Explorer ten may very well not support flash. It's very interesting. 0:18:07.440 --> 0:18:11.040 Won't stop you from downloading Chrome? Well at work with 0:18:11.119 --> 0:18:15.680 silver Light? Yeah, that's a good question. Really. I mean, 0:18:16.440 --> 0:18:18.600 I'm amazed that silver Light is still around, tell you 0:18:18.640 --> 0:18:21.359 the truth, but it is. I know it is. But 0:18:21.760 --> 0:18:25.919 even even when it tried to push for uh, you know, 0:18:26.080 --> 0:18:30.280 massive market acceptance through things like wasn't it the Olympics 0:18:31.000 --> 0:18:36.440 that Yeah, that that you could watch Olympic footage by 0:18:36.800 --> 0:18:40.840 by installing silver Light, which is a different video component 0:18:40.880 --> 0:18:44.720 player well not not just video but rich Internet interface 0:18:45.240 --> 0:18:49.960 and and again just it's similar to Flash in that respect. 0:18:50.200 --> 0:18:53.439 It's something that is not natively supported by HTML. You 0:18:53.480 --> 0:18:56.040 have to incorporate it into it. It's just that silver 0:18:56.119 --> 0:19:00.679 Light happens to actually be developed by Microsoft. Another interesting 0:19:00.720 --> 0:19:06.480 feature is that they have decided to change the way 0:19:06.720 --> 0:19:11.879 your computer handles things when it's not being used. Um, 0:19:11.920 --> 0:19:13.919 there's a video I saw when I was doing my 0:19:13.960 --> 0:19:17.240 research on Windows eight from a Microsoft employee. I think 0:19:17.240 --> 0:19:21.360 it's actually on YouTube somewhere. Um, and she has a laptop. 0:19:21.640 --> 0:19:23.760 She's holding a laptop and in one hand in the 0:19:23.760 --> 0:19:26.040 battery for the laptop. In the other hand, she said, okay, 0:19:26.280 --> 0:19:28.080 you need to watch this, and so she plugs it in. 0:19:28.119 --> 0:19:30.280 And that's a paraphrasing. She didn't say that exactly. I 0:19:30.320 --> 0:19:33.399 don't think plugged in the battery, flips open the laptop, 0:19:33.480 --> 0:19:38.359 turns it on, and blamo, it's on. Basically, this is 0:19:38.359 --> 0:19:43.639 because Windows eight hibernates it. It actually doesn't do it 0:19:43.680 --> 0:19:49.480 actually doesn't store information the same way um that previous 0:19:49.560 --> 0:19:52.320 versions of Windows did. So you're when you're booting, it's 0:19:52.359 --> 0:19:56.440 not a cold boot, uh you know, like it would 0:19:56.480 --> 0:19:59.080 be for previous versions of the operating systems. And when 0:19:59.119 --> 0:20:03.440 it boots up, it boots much faster, um than previous 0:20:03.520 --> 0:20:07.400 versions didn't. Yeah, there's there's part of the whole process 0:20:07.440 --> 0:20:10.240 is preloaded, so it doesn't have to go through the 0:20:10.280 --> 0:20:13.440 whole uh, the whole routine. Um. Yeah. It's also got 0:20:13.440 --> 0:20:17.359 the Connected Standby feature, which is a power management mode 0:20:17.600 --> 0:20:20.439 for the for ARM based versions of Windows eight, so 0:20:20.480 --> 0:20:23.560 that not not all chips, not all devices are going 0:20:23.600 --> 0:20:25.440 to take advantage of this, but the arm based ones 0:20:25.480 --> 0:20:28.280 will and that allows the PC to operate at a 0:20:28.400 --> 0:20:32.800 very low power level for for long periods when you're 0:20:32.800 --> 0:20:35.720 not using it. So, in other words, UM, you don't 0:20:35.760 --> 0:20:39.360 have to worry about shutting down your system completely if 0:20:39.400 --> 0:20:41.840 you need to, Like you're gonna go on a car 0:20:41.960 --> 0:20:44.160 trip or whatever, and you want to be able to 0:20:44.160 --> 0:20:48.240 to whip the a particular app or map up or 0:20:48.320 --> 0:20:50.320 something at a moment's notice, but you're not going to 0:20:50.400 --> 0:20:53.760 have it on all the time. It should, at least 0:20:53.800 --> 0:20:58.280 in theory, keep that power level uh nice and stable 0:20:58.680 --> 0:21:01.960 so that your your battery doesn't just drain away while 0:21:02.000 --> 0:21:04.960 your computer is in sleep mode or whatever the other devices. 0:21:05.480 --> 0:21:07.320 You know what, I'm sorry you're gonna say something. Well, 0:21:07.359 --> 0:21:08.919 I was gonna say that I had read an article 0:21:09.240 --> 0:21:12.840 by Chloe Albnsius and PC mag in which he had 0:21:13.119 --> 0:21:17.760 interviewed Gave All, who's the director of program management for Windows, 0:21:17.880 --> 0:21:22.040 and basically he was talking about how it how it works. 0:21:22.640 --> 0:21:26.200 It writes the information to a a hibernate file or 0:21:26.280 --> 0:21:28.880 hyber file i think it's what they called it, UM, 0:21:29.320 --> 0:21:32.919 and it just keeps all that that information in the 0:21:32.960 --> 0:21:37.280 kernel so that it's it's handy that basically the system, 0:21:37.280 --> 0:21:40.199 the entire system state, is sitting there in the kernel, 0:21:40.359 --> 0:21:41.920 so as soon as it gets to that point in 0:21:41.960 --> 0:21:43.520 the boot, it just goes, oh, here's where you are 0:21:44.080 --> 0:21:46.800 and puts it back up and makes that noise to yep, 0:21:47.000 --> 0:21:49.080 it does. I think that would be a little off 0:21:49.080 --> 0:21:51.480 putting for people who are you know, wait, Windows seven 0:21:51.480 --> 0:21:54.440 didn't go Actually it doesn't make that noise, but Chris 0:21:54.480 --> 0:21:56.399 will come up and stand next to you while you 0:21:56.400 --> 0:21:59.120 turn on your device and make that noise for you personally. Yeah, 0:21:59.200 --> 0:22:01.280 just let me know when you get When does eight installed? Actually, 0:22:01.320 --> 0:22:04.400 that's interesting a sign up sheet? Yeah, uh there. There 0:22:04.480 --> 0:22:07.080 is a developer preview available and you don't have to 0:22:07.119 --> 0:22:09.200 sign up to be a developer to get it, so 0:22:09.480 --> 0:22:12.399 members of the public are free to download the developer preview. 0:22:12.560 --> 0:22:16.760 What you gotta remember, the developer preview is not fully implemented. 0:22:16.800 --> 0:22:19.560 It's it is an early build, and there's not all 0:22:19.600 --> 0:22:22.399 the functionality, is there. Yeah, you could say, try to 0:22:22.440 --> 0:22:25.080 install a copy in your virtual machine and it could 0:22:25.240 --> 0:22:29.240 never actually work, right. I admittedly only tried it a 0:22:29.280 --> 0:22:31.280 couple of times. One of the two of us had 0:22:31.320 --> 0:22:34.000 that happen the other one didn't bother to try. Yeah, 0:22:34.720 --> 0:22:37.359 so not that I won't keep trying, and just so. 0:22:37.400 --> 0:22:42.639 Another another interesting feature which is again creating something of 0:22:43.119 --> 0:22:45.000 I don't know that controversy is the right word, but 0:22:45.000 --> 0:22:49.679 it's creating conversations, is the early load anti malware feature. 0:22:49.960 --> 0:22:52.720 Oh yes, so Windows eight is going to have built 0:22:52.800 --> 0:22:58.480 into it an anti malware function that will UH that 0:22:58.560 --> 0:23:02.960 will load early in the operating system boot process. And 0:23:03.040 --> 0:23:06.080 the idea here is that the anti malware will load 0:23:06.200 --> 0:23:11.000 up before uh some sort of other malware can be 0:23:11.040 --> 0:23:14.720 initiated during the startup sequence, because a lot of malware 0:23:14.760 --> 0:23:17.200 that's when it attacks, right, It's when your your machine 0:23:17.240 --> 0:23:19.560 is booting up. The code has been put into your 0:23:19.600 --> 0:23:23.159 machine but hasn't been activated yet until you reboot. So 0:23:23.200 --> 0:23:26.400 this would be uh sort of like an anti virus 0:23:26.560 --> 0:23:31.800 software package that boots very very early in the process 0:23:31.840 --> 0:23:34.840 so that it can try and capture that malware before 0:23:34.880 --> 0:23:37.919 it can do anything bad. And UH, of course, what 0:23:38.040 --> 0:23:40.440 this really means is ultimately means that the people who 0:23:40.520 --> 0:23:43.720 make malware are going to revisit how they make malware 0:23:43.760 --> 0:23:46.920