WEBVTT - TechStuff Opens Windows 8 0:00:02.400 --> 0:00:05.760 Get in touch with technology with tech Stuff from stuff 0:00:06.040 --> 0:00:14.200 dot com. Hello again, everyone, and welcome to tech Stuff. 0:00:14.200 --> 0:00:16.520 My name is Chris Polette and I am an editor 0:00:16.520 --> 0:00:19.200 at how stuff works dot com. Sitting across from me 0:00:19.280 --> 0:00:22.560 as usual, this star of stage and screen, the inimitable 0:00:22.840 --> 0:00:29.720 senior writer Jonathan Strickland. Hey there, that's my that's my 0:00:29.800 --> 0:00:33.760 disaffected Hollywood voice. Uh now, right off the bat, we've 0:00:33.760 --> 0:00:36.360 talked about Windows eight before. Yes, we know that, yes, 0:00:36.520 --> 0:00:38.599 so don't write in. But when we talked about Windows eight, 0:00:38.680 --> 0:00:42.959 it was from whatever little information we could glean at 0:00:42.960 --> 0:00:45.760 the time, because we had not had any experience really 0:00:46.080 --> 0:00:48.639 using Windows eight, at least not much. I think we had. 0:00:49.000 --> 0:00:51.920 You had I think downloaded an early, early early build 0:00:51.920 --> 0:00:54.800 of Windows at to developer build. Yes, and that was 0:00:55.000 --> 0:00:56.960 all we had had a chance to play with. But 0:00:57.080 --> 0:01:00.520 since then we have had a chance to a with 0:01:00.680 --> 0:01:04.479 the more or less full version of Windows eight. Now, granted, 0:01:04.480 --> 0:01:06.640 by the time this podcast goes out, Windows eight will 0:01:06.680 --> 0:01:10.200 have been released to the wild in the wild, to 0:01:10.280 --> 0:01:13.680 the wild wild people will be using Windows eight by 0:01:13.680 --> 0:01:16.319 the time this podcast goes live, But we're recording it 0:01:16.400 --> 0:01:19.960 the week before that happens. Ye, And uh, you know 0:01:20.520 --> 0:01:24.720 I am one of those people that I've learned sort 0:01:24.720 --> 0:01:27.120 of from past experience that maybe you don't want to 0:01:27.160 --> 0:01:30.000 stand in line for the brand new operating system the 0:01:30.120 --> 0:01:32.679 first day it comes out. It might be better to 0:01:34.120 --> 0:01:37.240 see what happens and let them release an update before 0:01:37.280 --> 0:01:39.720 you go ahead and put it on there. Because it 0:01:39.760 --> 0:01:41.880 seems like there's and it doesn't seem to matter who 0:01:41.920 --> 0:01:45.280 it's coming from. This just computer operating systems in general. 0:01:45.400 --> 0:01:49.120 It's agnostic as far as as operating systems go, in 0:01:49.120 --> 0:01:53.040 the sense that there's only there's so much testing you 0:01:53.080 --> 0:01:55.320 can do during the development of an operating system, but 0:01:55.480 --> 0:02:00.880 the the even the most rigorous testing uh environment is 0:02:00.880 --> 0:02:03.680 not going to be able to account for every single 0:02:04.600 --> 0:02:08.680 way people use their computers and the software they use 0:02:08.720 --> 0:02:11.200 in the hardware they use. So often in the early 0:02:11.280 --> 0:02:13.840 days of any operating system being released, you'll hear problems 0:02:13.880 --> 0:02:18.000 about or people complain about problems like certain software doesn't 0:02:18.280 --> 0:02:21.400 seem to work with that operating system, or it doesn't 0:02:21.400 --> 0:02:25.000 seem to recognize particular types of hardware You plug it 0:02:25.040 --> 0:02:27.120 in and like the driver is missing, so you can't 0:02:27.240 --> 0:02:30.000 use this one particular kind of hardware like a microphone 0:02:30.040 --> 0:02:32.440 or mixer or that's the kind of stuff that I 0:02:32.480 --> 0:02:35.280 always worry about. I was writing a paper for school, 0:02:35.280 --> 0:02:37.120 but I wanted to go ahead and install the new 0:02:37.160 --> 0:02:40.400 operating system, and now I can't print. Yeah, that can happen, 0:02:40.919 --> 0:02:43.760 so but but feeling that, I mean, that's just a 0:02:43.760 --> 0:02:46.480 problem that is that goes with the territory with any 0:02:46.480 --> 0:02:49.639 new operating system. We wanted to talk more about what 0:02:49.760 --> 0:02:54.080 makes Windows eight different, and uh, it's it's it's a 0:02:54.160 --> 0:02:58.960 dramatic departure from previous versions of Windows. If you are 0:02:59.120 --> 0:03:03.399 familiar with the the way Windows tends to look, that's 0:03:03.480 --> 0:03:06.760 it's a graphic user interface and has been for a 0:03:06.800 --> 0:03:11.639 couple of decades now. Um it's uh, you know, you're 0:03:11.680 --> 0:03:14.400 you're used to things like the start button at the 0:03:14.440 --> 0:03:16.720 in the bottom, which was introduced what was that Windows 0:03:16.760 --> 0:03:21.519 ninety five or I remember it being in wind Okay. 0:03:21.560 --> 0:03:24.240 So it's been around for a while and it's gone now. 0:03:24.400 --> 0:03:26.720 So that's so long since I've used Windows three point 0:03:26.919 --> 0:03:29.320 x that I write, I don't even remember what. I 0:03:29.360 --> 0:03:33.320 just remember all the tiles or or the icons rather tiles, 0:03:33.400 --> 0:03:36.080 but the icons that you would click on. So you know, 0:03:36.440 --> 0:03:40.200 Windows eight still has a desktop mode, although the start 0:03:40.240 --> 0:03:43.440 button has gone from it. UM, so if you were 0:03:43.600 --> 0:03:46.920 used to the start button, be prepared to lose it 0:03:47.120 --> 0:03:51.040 right it's gone. But it also the probably the thing 0:03:51.120 --> 0:03:55.480 that's gotten the most attention is the the tiled interface 0:03:55.560 --> 0:04:00.200 that Windows eight has, the Windows eight interface that you 0:04:00.280 --> 0:04:03.760 can when you look at you just know this thing 0:04:03.880 --> 0:04:07.200 was made for touch screen devices. You look at and 0:04:07.200 --> 0:04:09.360 you're like, this is It's clear that these are the 0:04:09.400 --> 0:04:11.200 kind of icons where if this were a touch screen 0:04:11.280 --> 0:04:13.280 I would touch that part of the screen and the 0:04:13.360 --> 0:04:16.880 app would launch. Uh, And in fact that is the case. 0:04:16.960 --> 0:04:20.120 It is designed so that will will work both with 0:04:20.400 --> 0:04:25.880 touch screen interface devices or displays and with the more 0:04:25.880 --> 0:04:30.640 traditional keyboard and mouse interface. UM, you can do either. 0:04:32.160 --> 0:04:36.360 I think it's with our our limited experience with it, 0:04:36.440 --> 0:04:38.960 I would say that I would imagine there's going to 0:04:39.000 --> 0:04:41.880 be quite a learning curve for people who adopt this, 0:04:42.080 --> 0:04:44.600 who are especially people who are really used to older 0:04:44.680 --> 0:04:49.120 versions of Windows. It's going to take time to get 0:04:49.160 --> 0:04:53.640 to a familiarity with this oberating system where they feel 0:04:53.640 --> 0:04:58.000 they can navigate through it seamlessly, particularly if they're using 0:04:58.080 --> 0:05:01.599 a keyboard and mouse. It's not that it's impossible, it's 0:05:01.600 --> 0:05:05.720 not that Windows has made it uh ungainly or anything. 0:05:05.760 --> 0:05:08.599 It's just so different from what you knew before that 0:05:08.720 --> 0:05:10.800 it's going to take time to learn all those tricks 0:05:11.279 --> 0:05:14.120 and it may be a little frustrating at first. Now, 0:05:14.120 --> 0:05:16.640 if you have a touch screen device or touch screen display, 0:05:17.160 --> 0:05:20.159 it's going to feel pretty natural because it's got this, 0:05:20.320 --> 0:05:24.720 like I said, this tiled approach to laying out all 0:05:24.760 --> 0:05:29.160 the apps, and you navigate the way I guess the 0:05:29.200 --> 0:05:31.480 way you navigate just about any touch screen interface. At 0:05:31.480 --> 0:05:34.000 this point, you touch the screen, you can drag your 0:05:34.040 --> 0:05:36.039 finger one way or the other and it moves the 0:05:36.120 --> 0:05:39.400 tiles accordingly. And then by tapping on a tile, you 0:05:39.440 --> 0:05:42.400 open up the the app or feature or whatever it is. 0:05:43.040 --> 0:05:48.080 And so I mean it's very intuitive from a touch perspective, 0:05:48.520 --> 0:05:50.560 but using the mouse and keyboard, like I said, it's 0:05:50.560 --> 0:05:53.039 going to it's gonna take some time for people to 0:05:53.080 --> 0:05:58.680 adjust to the different layout and the different navigation scheme. Yeah, 0:05:58.720 --> 0:06:05.039 the uh Microsoft really got into the navigation and how 0:06:05.080 --> 0:06:07.920 people are going to be using this, and they, um, 0:06:07.960 --> 0:06:10.599 it's clear that they were thinking about something that could 0:06:10.600 --> 0:06:14.680 be cross hardware. Um, you know, it could be used 0:06:14.680 --> 0:06:18.960 on a computer, could be used on a mobile device. Um. 0:06:19.000 --> 0:06:21.120 And frankly, you know, if you look at the form 0:06:21.240 --> 0:06:25.800 factor of screens of all types, we've really gone, you know, 0:06:26.360 --> 0:06:29.839 towards the sixteen by nine ratio as opposed to the 0:06:29.880 --> 0:06:32.039 four by three, which four by three is like a 0:06:32.080 --> 0:06:34.400 standard definition TV when you're looking at it in the 0:06:34.440 --> 0:06:38.080 sixteen by nine is the um the way an HD 0:06:38.160 --> 0:06:41.560 TV looks. So it's you know, uh, longer, more rectangular, 0:06:41.680 --> 0:06:44.400 less square, more of a wide screen. Look. Yeah, and 0:06:44.560 --> 0:06:48.720 I mean our phones look like that, tablets look like that. UM, 0:06:48.960 --> 0:06:53.400 computer monitors look like that. Laptops have have developed you know, 0:06:53.839 --> 0:06:56.440 according to that too, So uh it makes a lot 0:06:56.480 --> 0:07:01.400 more sense, um, to have the operating system be designed 0:07:01.440 --> 0:07:05.440 with that in mind. And UM, they've really um, you know, 0:07:05.480 --> 0:07:08.160 talking about the earlier release that we had a chance 0:07:08.200 --> 0:07:11.360 to play with some quite some time ago. Now, UM, 0:07:11.480 --> 0:07:16.520 Microsoft has been really um outgoing about its efforts to 0:07:16.760 --> 0:07:21.040 woo the developers because you know, they do have a 0:07:21.080 --> 0:07:26.960 strong relationship with their developers. And um they's subtle, subtle, 0:07:27.840 --> 0:07:32.880 little references to a very popular video on YouTube, which 0:07:32.920 --> 0:07:35.240 is not so subtle. But no, they've they've they've really 0:07:35.240 --> 0:07:37.560 reached out and said, look, these are guidelines that we've 0:07:37.960 --> 0:07:41.160 uh that we've come up with usability guidelines, navigation guidelines. 0:07:41.200 --> 0:07:44.200 We really think if you design your applications to work 0:07:44.240 --> 0:07:47.120 with this in mind, it will be a positive experience. 0:07:47.320 --> 0:07:49.720 And the the the apps that we had a chance 0:07:49.760 --> 0:07:54.400 to play around with really did you know, it wasn't seamless, 0:07:54.600 --> 0:07:56.960 but there was very little seam if you will, I mean, 0:07:57.000 --> 0:07:59.560 they really did fit in with the environment. Pardon me, 0:07:59.600 --> 0:08:02.160 wise backed the table with my n What's what's interesting 0:08:02.240 --> 0:08:06.240 also is that you know, bringing the world of mobile 0:08:06.600 --> 0:08:12.520 with the world of PC together is challenging on multiple fronts. 0:08:12.760 --> 0:08:16.120 Um One, you have to design hardware that is capable 0:08:16.280 --> 0:08:19.960 of keeping up with like mobile hardware that's capable of 0:08:20.000 --> 0:08:23.280 keeping up with what we're used to from a PC, 0:08:23.440 --> 0:08:26.800 whether it's a laptop or desktop. You also have to 0:08:27.320 --> 0:08:31.760 factor in, well, the input for a tablet tends to 0:08:31.800 --> 0:08:35.280 be very different than the input for a computer, So 0:08:36.360 --> 0:08:39.400 how do we account for that. For apps that are 0:08:39.400 --> 0:08:42.040 designed for touch, there's no problem, you know, that's that's 0:08:42.040 --> 0:08:44.520 designed with the tablet form factor in mind. But what 0:08:44.600 --> 0:08:49.599 about those desktop applications that are not designed for touch interface, 0:08:49.720 --> 0:08:53.080 at least not not primarily designed for touch interface? How 0:08:53.120 --> 0:08:56.600 do you get around that and it's it's Windows eight 0:08:56.679 --> 0:08:59.560 is a is goes a long way to trying to 0:08:59.600 --> 0:09:04.559 reckon style all of that. Now, we haven't had chance 0:09:04.600 --> 0:09:07.000 to really play with all the different stuff that we 0:09:07.040 --> 0:09:11.120 would normally use on a Windows machine. For example, Office, 0:09:11.559 --> 0:09:14.640 which is you know, that's productivity software. And a lot 0:09:14.679 --> 0:09:17.600 of people know what Microsoft You know they've used Microsoft Office. 0:09:17.720 --> 0:09:22.000 It's word and Excel and power Point, things like that. Uh, 0:09:22.120 --> 0:09:26.800 I've used those quite a bit on computers with the 0:09:26.920 --> 0:09:30.280 mouse and keyboard combinations. I'm very familiar with that. I 0:09:30.320 --> 0:09:32.640 don't know what that would be like on a tablet 0:09:33.160 --> 0:09:39.240 if I did not have a peripheral devices because most 0:09:39.280 --> 0:09:42.880 tablets nowadays will support peripheral devices, whether it's through Bluetooth 0:09:42.960 --> 0:09:46.880 or USB or whatever. But you can often connect to 0:09:47.000 --> 0:09:50.840 a tablet something like a keyboard and a mouse, or 0:09:50.880 --> 0:09:52.720 it will have a docking station where you can connect 0:09:52.760 --> 0:09:55.920 everything through the docking station to the tablet and it 0:09:55.920 --> 0:10:00.400 it becomes essentially like a very lightweight laptop computer. It's 0:10:00.400 --> 0:10:04.560 just that all the elements detached from each other. Um. 0:10:04.600 --> 0:10:07.520 Now in that case, you would I could see using 0:10:07.760 --> 0:10:11.200 those those uh, those pieces of software in essentially the 0:10:11.200 --> 0:10:13.560 same way you would if it were a true laptop 0:10:13.640 --> 0:10:17.880 or PC. Without them, I'm not sure how I would 0:10:17.960 --> 0:10:21.280 use them. Uh. It's not to say that they're unusable. 0:10:21.320 --> 0:10:24.080 I just haven't had that experience. But that's one of 0:10:24.120 --> 0:10:27.600 the challenges that Microsoft faces with Windows eight and the 0:10:27.679 --> 0:10:30.960 design of an operating system that can work on both 0:10:31.080 --> 0:10:36.160 mobile and and PC platforms is how do you make 0:10:36.240 --> 0:10:40.320 sure that you you are catering to both audiences without 0:10:40.440 --> 0:10:44.680 sacrificing too much for either one. Because if you cater 0:10:44.760 --> 0:10:47.760 too much on the tablet side, everyone who uses the 0:10:47.800 --> 0:10:52.880 desktop or laptop version of the the operating system is 0:10:52.920 --> 0:10:56.959 going to feel like things are too difficult to do 0:10:57.440 --> 0:11:02.520 in that form factor to just by that operating system, right, 0:11:02.559 --> 0:11:07.400 So balancing that is really tricky, and I think they 0:11:07.440 --> 0:11:09.960 did a pretty good job with it. We did practice 0:11:10.640 --> 0:11:13.760 navigating through Windows eight using only the mouse and keyboard, 0:11:13.840 --> 0:11:15.640 so even though we were we were using it on 0:11:15.679 --> 0:11:18.640 a tablet. We had a tablet device that had Windows 0:11:18.640 --> 0:11:20.800 eight loaded on it that we tried to play with. 0:11:21.080 --> 0:11:22.720 By the way, I'm just gonna go ahead and tell 0:11:22.720 --> 0:11:27.080 you it was not the surface. I really want to 0:11:27.120 --> 0:11:29.679 play with a surface tablet, but I have not had 0:11:29.720 --> 0:11:32.960 that opportunity yet, at least as of the recording of 0:11:32.960 --> 0:11:35.000 this podcast. Who knows by the time between the wind 0:11:35.559 --> 0:11:38.560 is recorded when it launches, I'm gonna guess I still 0:11:38.600 --> 0:11:41.320 haven't really played with one, but unless there's a store 0:11:41.320 --> 0:11:45.200 that happens to have one. Anyway, we we did navigate 0:11:45.240 --> 0:11:48.320 with just the keyboard and mouse, and it took some 0:11:49.280 --> 0:11:51.040 even for us. It took some time for us to 0:11:51.080 --> 0:11:53.439 kind of just even get the basics. But once we 0:11:53.520 --> 0:11:56.920 got the basis right, Okay, I understand how this works. Now. 0:11:57.000 --> 0:11:58.520 It's definitely one of those things where I'd have to 0:11:58.559 --> 0:12:03.040 train my brain to catch up to make this feel natural. 0:12:03.600 --> 0:12:06.959 But you know, we could definitely see how to get 0:12:07.000 --> 0:12:10.400 around whether or not it's easy enough for the average 0:12:10.520 --> 0:12:14.800 user so that that level of frustration isn't overwhelming. I 0:12:14.840 --> 0:12:18.720 don't know it'll be. That will be a real test 0:12:18.760 --> 0:12:22.320 of the operating system. It'll especially once people if people 0:12:22.360 --> 0:12:23.880 want to go to the desktop to use some of 0:12:23.880 --> 0:12:27.760 the more robust programs, because as I understand it, things 0:12:27.840 --> 0:12:31.200 like the productivity software of Office would be in the 0:12:31.280 --> 0:12:35.079 desktop version of the view, not the Windows eight interface 0:12:35.200 --> 0:12:37.520 version of the view. So if you wanted to open 0:12:37.600 --> 0:12:39.800 up Word, you would go into the desktop and then 0:12:39.840 --> 0:12:42.400 open it up that way, and you would, you know, 0:12:42.679 --> 0:12:44.480 do all your your work in there. And now they 0:12:44.480 --> 0:12:48.040 do have some uh they have an upcoming version of 0:12:48.040 --> 0:12:52.400 of Office that's going to incorporate touch commands as well 0:12:52.440 --> 0:12:55.959 as your regular keyboard and mouse commands. But even then, 0:12:56.080 --> 0:12:59.280 I think it's all relegated to the if I may 0:12:59.320 --> 0:13:01.240 be wrong about this, but I think it's all relegated 0:13:01.280 --> 0:13:05.959 to the desktop version of the view of Microsoft date, 0:13:06.080 --> 0:13:10.800 not the interface, not the tiled interface. Um on. One 0:13:10.840 --> 0:13:13.280 thing that I'm sorry to all I was gonna say 0:13:13.360 --> 0:13:16.040 is that this should not be confused with there are 0:13:16.080 --> 0:13:18.800 two different versions of this tiled interface coming out. There's 0:13:18.800 --> 0:13:22.080 Windows are T and there's Windows eight. And Windows are 0:13:22.120 --> 0:13:25.760 T is designed for mobile devices that are on the 0:13:25.840 --> 0:13:29.760 lower powered end of the spectrum. So these are ones 0:13:29.840 --> 0:13:33.160 that that tiled interface is what you get, and that's 0:13:33.240 --> 0:13:36.120 you know, it's it's mainly meant to to compete in 0:13:36.200 --> 0:13:40.080 the tablet market as we understand it today, so that 0:13:40.160 --> 0:13:43.600 being things like the iPad and Android tablets where they 0:13:43.640 --> 0:13:49.840 are running uh, simplified versions of software so that the 0:13:49.880 --> 0:13:52.040 software doesn't tend to be as robust as a full 0:13:52.120 --> 0:13:56.000 PC program would be you know, they're there. They're more 0:13:56.120 --> 0:13:59.120 like the apps that we've become accustomed to over the 0:13:59.200 --> 0:14:04.079 last few years. Windows eight, the full version of Windows eight, 0:14:04.400 --> 0:14:09.440 is something that is running on higher end tablets as 0:14:09.440 --> 0:14:13.600 well as PCs and laptops. That would be uh, the 0:14:13.640 --> 0:14:16.480 one that has the desktop view and can run these 0:14:16.600 --> 0:14:22.400 more robust programs like Microsoft Office. Yeah, and UM yeah, 0:14:22.480 --> 0:14:24.880 that's that's a good point because they've kind of gone 0:14:24.880 --> 0:14:29.120 in the other direction to um to have some of 0:14:29.160 --> 0:14:34.960 the elements of Microsoft Office bleed over into the operating system. UM. 0:14:34.960 --> 0:14:36.640 I don't know if you've noticed this or not been 0:14:36.680 --> 0:14:39.640 In opening a couple of the Windows just in Windows Explorer, 0:14:40.040 --> 0:14:45.920 I noticed that the ribbon interface from Office, which Jonathan 0:14:45.960 --> 0:14:48.760 loves so much, by the way, um, that appears at 0:14:48.760 --> 0:14:51.120 the top of the screen with all your little uh 0:14:51.360 --> 0:14:55.760 gadgets and gizmos a plenty. Um, and who's it some 0:14:55.840 --> 0:15:00.120 webs at skill Lore. Um. The that same in your 0:15:00.120 --> 0:15:03.120 faces appearing in other parts of Windows at least in there. 0:15:03.200 --> 0:15:07.800 So people who are familiar with Office are going to 0:15:07.840 --> 0:15:11.240 be familiar with that part of the operating system as 0:15:11.280 --> 0:15:13.080 a whole, with that part of the interface as a whole. 0:15:13.120 --> 0:15:16.200 So I think I finally figured that ribbon thing out. 0:15:16.240 --> 0:15:18.960 Now it's about time form you change with the Yeah, 0:15:19.280 --> 0:15:22.040 now that that is something that I feel a lot 0:15:22.080 --> 0:15:25.520 of empathy toward users who get frustrated with major changes 0:15:25.560 --> 0:15:29.000 in operating systems or any kind of software, because when 0:15:29.040 --> 0:15:33.720 you become accustomed to something and you really have streamlined 0:15:33.760 --> 0:15:37.000 your approach to using a particular piece of software, it 0:15:37.040 --> 0:15:39.960 does become a bit of a frustration when that changes 0:15:40.040 --> 0:15:43.320 so dramatically as to interrupt that flow. And I mean 0:15:43.600 --> 0:15:47.360 this is not this is not unique to Windows or 0:15:47.560 --> 0:15:50.200 really to Microsoft at all. This is something that goes 0:15:50.240 --> 0:15:55.920 across all platforms, all software, all operating systems, really any product. 0:15:56.040 --> 0:15:58.040 When you get down to it, is that when you 0:15:58.080 --> 0:16:00.200 get used to the way something is and then get 0:16:00.240 --> 0:16:04.400 the new thing, that's even if it's demonstrably better than 0:16:04.480 --> 0:16:07.160 the old thing, if it's different enough you start to 0:16:07.200 --> 0:16:10.880 complain about, I can't find anything on this this because 0:16:10.920 --> 0:16:15.360 it's they've changed where everything is. Um So I'm not 0:16:15.440 --> 0:16:18.320 immune to that. Yeah. Well, Apple has had the same 0:16:18.360 --> 0:16:21.720 thing going on too with um uh. One of the things, 0:16:21.800 --> 0:16:24.920 the example that popped into my mind was the recent 0:16:25.080 --> 0:16:29.200 change of the scroll direction with a scrolling mouse. We 0:16:29.360 --> 0:16:34.400 flipped it so that exactly so if you, you know, 0:16:34.760 --> 0:16:37.440 use your iPad and you now you you go through 0:16:37.440 --> 0:16:39.840 your email and then you go to your computer, you 0:16:40.120 --> 0:16:43.680 don't scroll in the opposite direction. And people complained about that, 0:16:44.160 --> 0:16:46.800 and of course Apple made it possible for you to 0:16:46.920 --> 0:16:49.880 go into your your system preferences and it off and 0:16:50.040 --> 0:16:53.600 make it make it the traditional way. But people were 0:16:53.600 --> 0:16:56.680 complaining about that thing. And you can you can tell, 0:16:56.720 --> 0:17:00.800 I mean the Windows ahead, I'm sorry it with Windows eight, 0:17:00.840 --> 0:17:05.320 with the the option for the more touchscreen oriented layout 0:17:05.320 --> 0:17:09.120 even on a computer, and uh, the mac os appearing 0:17:09.119 --> 0:17:14.359 more like iOS that that um computer and operating system 0:17:14.440 --> 0:17:20.160 manufacturers are seeing that the world's bleeding over into one another. 0:17:20.560 --> 0:17:24.480 That you expect computer functionality from a tablet or a smartphone, 0:17:24.600 --> 0:17:27.600 and you expect navigation to work the same on on both, 0:17:27.760 --> 0:17:30.280 and beyond that that you expect to be able to 0:17:30.359 --> 0:17:33.520 work on the same stuff from one platform to the 0:17:33.560 --> 0:17:36.040 next in a in a seamless a way as possible. 0:17:36.440 --> 0:17:39.120 So this brings in the whole idea of the cloud 0:17:39.400 --> 0:17:41.640 in there as well, so that when you are saving 0:17:41.960 --> 0:17:45.800 a project, whatever it may be, in whatever program you're 0:17:45.800 --> 0:17:49.639 thinking about that when you put down one piece of 0:17:49.680 --> 0:17:52.199 technology and pick up another, that you are able to 0:17:52.240 --> 0:17:55.960 go right back into that project uninterrupted as if you 0:17:56.000 --> 0:17:58.840 have been working on the same platform the entire time. Yeah, 0:17:59.240 --> 0:18:03.359 that's that's a powerful experience. Anyone who has had that 0:18:03.440 --> 0:18:06.919 where they you know, something as simple as watching a 0:18:07.040 --> 0:18:12.359 video on Let's say you pull up a really long video, 0:18:12.440 --> 0:18:15.600 like a movie on your laptop and you're watching a 0:18:15.600 --> 0:18:19.960 bit of it, and then you have to take a 0:18:20.040 --> 0:18:22.280 bus ride somewhere, and it's a long bus ride, so 0:18:22.320 --> 0:18:24.000 you pull up your your phone and you get your 0:18:24.040 --> 0:18:26.719 your earbuds in because you're being nice and you're not 0:18:26.760 --> 0:18:29.159 listening to something so that the entire bus has to 0:18:29.240 --> 0:18:33.040 hear you watch Independence Day you um, you pull it 0:18:33.119 --> 0:18:36.520 up in it and because you're using this this uh 0:18:36.520 --> 0:18:39.359 service that goes across multiple platforms, it pulls it up 0:18:39.440 --> 0:18:41.040 right where you left off when you were watching on 0:18:41.040 --> 0:18:43.760 the PC, and you continue watch again. Then you get 0:18:43.760 --> 0:18:45.600 home and you think, oh, well, I've got this set 0:18:45.640 --> 0:18:49.200 top box connected to my television and there's the last 0:18:49.359 --> 0:18:52.919 fifteen minutes the movie and I need to see uh 0:18:53.080 --> 0:18:56.280 Quaid go up and blow himself up inside the giant 0:18:56.600 --> 0:19:01.159 spaceship spoiler alert. Um, then you know you can you 0:19:01.160 --> 0:19:03.600 can load that up. And because again it's a service 0:19:03.600 --> 0:19:06.119 that goes across these multiple platforms, it picks up right 0:19:06.160 --> 0:19:09.800 where you left off on the phone. That's a great experience, 0:19:10.080 --> 0:19:11.760 and I mean that's that's the one that I think 0:19:11.800 --> 0:19:15.080 everyone uses as an example, like you're listening to music 0:19:15.200 --> 0:19:17.440 or you're watching a movie and you're able to move 0:19:17.560 --> 0:19:21.239 from one device to another and continue that experience as 0:19:21.280 --> 0:19:24.679 always shown as being completely seamless, which in reality never happens. 0:19:24.720 --> 0:19:28.080 There's always there's always buffering, there's there's lots of things 0:19:28.080 --> 0:19:31.960 that go into that, but you know, the idea is there. Well, 0:19:32.000 --> 0:19:34.560 the same thing is true with these operating systems like 0:19:34.600 --> 0:19:38.119 Windows eight, where the idea is to try and have 0:19:38.680 --> 0:19:40.880 the mobile world and PC world together so that you 0:19:40.920 --> 0:19:45.000 can have an uninterrupted experience and whatever you're working in. 0:19:45.240 --> 0:19:48.280 So that way, if you need to pick up and 0:19:48.320 --> 0:19:51.080 go and you want to do some minor changes to 0:19:51.280 --> 0:19:53.960 something on a tablet that you had been working on 0:19:54.040 --> 0:19:57.880 in a PC, you have that option and UH. And 0:19:58.320 --> 0:20:01.600 so that requires a very robe bust operating system that 0:20:01.880 --> 0:20:06.000 is UH that can be used in multiple form factors 0:20:06.680 --> 0:20:10.320 It's also true that in upcoming there there are more 0:20:10.400 --> 0:20:14.400 and more laptops and even desktop displays coming out they 0:20:14.440 --> 0:20:19.000 have touch screen functionality built into them. I do not 0:20:19.119 --> 0:20:21.880 own any of these. I don't have a touch screen display. 0:20:21.920 --> 0:20:25.040 I don't have a laptop with a touch screen monitor. 0:20:25.600 --> 0:20:28.640 But um, but imagine they're pretty pricey for for most 0:20:28.640 --> 0:20:31.200 people at this point. Yeah, but they have been coming on. 0:20:31.240 --> 0:20:33.560 I mean, I remember seeing a few of them a 0:20:33.600 --> 0:20:36.160 couple of years ago at c E S, and I'm 0:20:36.200 --> 0:20:38.760 sure I'll see a lot more of them at the 0:20:39.960 --> 0:20:45.360 c E S. Uh. I don't know. It may very 0:20:45.359 --> 0:20:48.040 well be that the future of operating systems requires that 0:20:48.119 --> 0:20:51.800 kind of hardware to be optimal right for you to 0:20:51.800 --> 0:20:55.560 get the most out of it. But again, the goal 0:20:55.640 --> 0:20:58.600 that Microsoft had was to treat create an operating system that, 0:20:58.640 --> 0:21:02.240 no matter what for M you were using UH to 0:21:02.520 --> 0:21:05.600 run the operating system on, you would be able to 0:21:05.720 --> 0:21:09.840 navigate through it as easily as possible. It's it's a 0:21:09.920 --> 0:21:15.040 challenging thing because it's so fundamentally different, you know. I 0:21:15.040 --> 0:21:18.760 mean that was something that Apple really paid attention to 0:21:18.840 --> 0:21:22.160 in the development of the iPhone and the iPod Touch, 0:21:22.359 --> 0:21:25.800 and then later the iPad was that, how do we 0:21:25.840 --> 0:21:30.720 design a an operating system that is easy and intuitive? 0:21:31.359 --> 0:21:33.919 And uh, do we you know, how much attention do 0:21:34.000 --> 0:21:39.040 we pay to our uh computer version of that operating system, 0:21:39.080 --> 0:21:41.400 like do do we model it after a computer reversion? 0:21:41.560 --> 0:21:47.000 And Apple's decision was to depart dramatically from the computer 0:21:47.080 --> 0:21:52.480 operating system. Uh. Microsoft's decision is more to create a 0:21:52.480 --> 0:21:55.640 an experience that can work across all of it, as 0:21:55.680 --> 0:22:00.600 opposed to let's do something specifically for this form factor 0:22:00.680 --> 0:22:04.919 and only this form factor. Yeah. Microsoft, of course is 0:22:05.160 --> 0:22:10.119 uh the still very much the operating system of choice 0:22:10.760 --> 0:22:17.520 for businesses and very very popular among enterprise applications. Yeah, 0:22:17.560 --> 0:22:21.280 and I would I would say that it's likely that 0:22:21.960 --> 0:22:25.520 with the release of the new Office Suite and the 0:22:25.520 --> 0:22:29.680 the cross hardware capabilities of the operating system, they're they're 0:22:29.680 --> 0:22:33.159 planning on making a big push to be the operating 0:22:33.160 --> 0:22:36.439 system with Windows eight for the for the enterprise market, 0:22:36.880 --> 0:22:40.640 you know. Plus with the hybrid computers coming out now, 0:22:40.680 --> 0:22:44.200 to the laptops that have a removable screen that turns 0:22:44.240 --> 0:22:49.160 into a tablet or they flip around with a slate, Yeah, 0:22:49.240 --> 0:22:52.439 they you know, these are intended to you know, to 0:22:52.560 --> 0:22:56.520 function in multiple modes and uh, you know previously the uh, 0:22:57.000 --> 0:22:59.800 the Lenovo that you saw at CES a couple of 0:22:59.840 --> 0:23:04.920 years to go, um the U one yeah, um, when 0:23:04.920 --> 0:23:06.800 you pulled the you know, the screen out and it 0:23:06.880 --> 0:23:12.080 became a tablet, it ran on Linux, it switched operating systems. 0:23:12.200 --> 0:23:14.359 When it was in laptop form, it was running a 0:23:14.440 --> 0:23:18.119 version of Windows, and then you detached the screen and 0:23:18.200 --> 0:23:21.000 it would switch to a Linux based operating system. The 0:23:21.040 --> 0:23:26.919 idea trying again trying to maintain the seamless approach as 0:23:27.000 --> 0:23:29.040 much as possible, so that if you were working on 0:23:29.080 --> 0:23:31.919 something in Windows and then you detached the screen, it 0:23:31.920 --> 0:23:36.760 would open up a comparable application within Linux and try 0:23:36.840 --> 0:23:40.520 to continue that experience, which, as I'm sure you can 0:23:40.560 --> 0:23:43.240 all imagine, is not an easy thing to do, nor 0:23:43.440 --> 0:23:49.760 was it completely successful. Right, Yeah, so tough. That's a 0:23:49.800 --> 0:23:51.640