1 00:00:02,520 --> 00:00:05,760 Speaker 1: Get in touch with technology with tech Stuff from hof 2 00:00:06,120 --> 00:00:14,240 Speaker 1: dot com. Hello again, everyone, and welcome to tech Stuff. 3 00:00:14,280 --> 00:00:15,920 Speaker 1: My name is Chris Poulette and I'm an editor at 4 00:00:15,920 --> 00:00:18,040 Speaker 1: how Stuff Works dot com. Sitting here across from me 5 00:00:18,200 --> 00:00:24,959 Speaker 1: as usual as senior writer Jonathan Strick. I crave baked goods. Uh. Yeah, 6 00:00:25,000 --> 00:00:28,360 Speaker 1: you know, we don't really have a lot of outtakes 7 00:00:28,440 --> 00:00:31,480 Speaker 1: on this ship. I managed to say every bun last 8 00:00:31,520 --> 00:00:35,760 Speaker 1: time and another and then I referenced it and you 9 00:00:35,840 --> 00:00:39,120 Speaker 1: got it. Anyway, Thanks, You're welcome. So anyhow, we'll talk 10 00:00:39,120 --> 00:00:42,239 Speaker 1: a little bit about HTML five. Why don't we? Why not? 11 00:00:42,880 --> 00:00:45,680 Speaker 1: All right then, So, first of all, I would like 12 00:00:45,720 --> 00:00:48,519 Speaker 1: to tell everyone out there in the listening audience we 13 00:00:48,600 --> 00:00:52,239 Speaker 1: are currently recording this episode in the afternoon, in the 14 00:00:52,240 --> 00:00:54,640 Speaker 1: middle of the week. Now, the reason why that's interesting 15 00:00:54,680 --> 00:00:57,720 Speaker 1: to us is that we normally record on Friday mornings 16 00:00:58,080 --> 00:01:00,280 Speaker 1: at the end of a long week, but this is 17 00:01:00,320 --> 00:01:06,640 Speaker 1: a Tuesday afternoon and I'm feeling a little zany. So okay, 18 00:01:06,640 --> 00:01:10,480 Speaker 1: but HTML five, So HTML five, before we even get 19 00:01:10,520 --> 00:01:12,959 Speaker 1: into that, we need to talk about what hypertext markup 20 00:01:13,040 --> 00:01:17,400 Speaker 1: language is. Yes, Now, this is the stuff that essentially, 21 00:01:17,400 --> 00:01:20,600 Speaker 1: this language is what helps a web web developer design 22 00:01:20,640 --> 00:01:23,800 Speaker 1: a web page so that it appears a certain way 23 00:01:23,840 --> 00:01:26,520 Speaker 1: when you access it with a web browser. It's a 24 00:01:26,640 --> 00:01:30,800 Speaker 1: very basis of making stuff appear on a web page 25 00:01:31,080 --> 00:01:33,480 Speaker 1: the right way. And so this dates all the way 26 00:01:33,480 --> 00:01:37,360 Speaker 1: back to the early nineties. Do you remember the early nineties? Yes, yeah, 27 00:01:37,640 --> 00:01:40,440 Speaker 1: what a magical time that was. Huh No, no, you're right, 28 00:01:40,520 --> 00:01:43,800 Speaker 1: let's move on. So but but in general, this is 29 00:01:43,840 --> 00:01:45,959 Speaker 1: the stuff that has the tags in it that tell 30 00:01:46,640 --> 00:01:49,360 Speaker 1: you know, the tag is essentially a message to the 31 00:01:49,400 --> 00:01:53,040 Speaker 1: web browser saying, when you see this tag, you need 32 00:01:53,080 --> 00:01:57,800 Speaker 1: to take this action, uh and make whatever comes after 33 00:01:57,920 --> 00:02:01,760 Speaker 1: that appear a certain way on website. Or it may 34 00:02:01,840 --> 00:02:03,640 Speaker 1: just be to help lay it out a certain way. 35 00:02:04,280 --> 00:02:07,520 Speaker 1: And so, uh, there were a lot of tags that 36 00:02:07,560 --> 00:02:11,800 Speaker 1: were developed for HTML, and eventually, uh, it got to 37 00:02:11,840 --> 00:02:14,720 Speaker 1: the point where there needed to be a new implementation 38 00:02:14,800 --> 00:02:19,040 Speaker 1: of HTML because it was starting to get a little clunky, right, 39 00:02:19,120 --> 00:02:21,640 Speaker 1: you know, they had a lot of tags there and 40 00:02:21,720 --> 00:02:25,359 Speaker 1: it was not elegant and confusing for someone who was 41 00:02:25,440 --> 00:02:27,120 Speaker 1: just trying to start up a website. So there were 42 00:02:28,120 --> 00:02:32,360 Speaker 1: attempts to make that more streamlined. Yeah, just just for clarification, 43 00:02:32,360 --> 00:02:36,120 Speaker 1: when we're talking about tags, basically, uh, an HTML document 44 00:02:36,240 --> 00:02:40,959 Speaker 1: document is simply a text document um. So it's it's 45 00:02:41,000 --> 00:02:45,200 Speaker 1: basically your your your letters, your numbers, uh, all those 46 00:02:45,280 --> 00:02:50,320 Speaker 1: kinds of standard text characters with no formatting whatsoever. In fact, 47 00:02:50,440 --> 00:02:52,800 Speaker 1: you're the ones supplying the formatting. If you want something 48 00:02:52,919 --> 00:02:56,959 Speaker 1: in in bold in the current version of HTML, you 49 00:02:56,960 --> 00:02:59,480 Speaker 1: would type I want this text in bold, and before 50 00:02:59,520 --> 00:03:02,760 Speaker 1: that you would type of tag called strong, which is 51 00:03:02,800 --> 00:03:05,560 Speaker 1: put in between in between brackets, and at the end 52 00:03:05,600 --> 00:03:08,160 Speaker 1: of the text that you want bold, you would put 53 00:03:08,200 --> 00:03:09,880 Speaker 1: what they call a clothes tag, which is a slight 54 00:03:10,120 --> 00:03:12,960 Speaker 1: variant on that, basically to say, I want the following 55 00:03:13,000 --> 00:03:15,560 Speaker 1: in bold. I wanted to stop here, and it goes 56 00:03:15,600 --> 00:03:17,960 Speaker 1: in for that. It could be italic, it could be underlined, 57 00:03:18,000 --> 00:03:20,120 Speaker 1: it could be struck through or you That's how you 58 00:03:20,160 --> 00:03:22,440 Speaker 1: put in hyperlinks, that's how you put in images. Is 59 00:03:22,480 --> 00:03:26,160 Speaker 1: alway these little tags and it's all in uh more 60 00:03:26,240 --> 00:03:28,040 Speaker 1: or less plain English. You're not doing a lot of 61 00:03:28,040 --> 00:03:32,680 Speaker 1: calculation like you would in any a typical programming language, 62 00:03:32,680 --> 00:03:35,480 Speaker 1: like for example, see where you're actually putting in variables 63 00:03:35,480 --> 00:03:38,280 Speaker 1: and all that stuff. That's why HTML is is popular 64 00:03:39,000 --> 00:03:41,520 Speaker 1: for people who are sort of dabbling in the idea 65 00:03:41,680 --> 00:03:44,240 Speaker 1: of programming because it sort of gives you an idea 66 00:03:44,240 --> 00:03:46,400 Speaker 1: of what coding is like without a whole lot of 67 00:03:46,920 --> 00:03:50,400 Speaker 1: coding UM and you and it's very simple to do. 68 00:03:50,480 --> 00:03:55,280 Speaker 1: It's based on a standard page definition UM, which is 69 00:03:55,640 --> 00:03:59,960 Speaker 1: maintained by the UH the W three C, the World 70 00:04:00,000 --> 00:04:03,360 Speaker 1: Old Wide Web Consortium. Yeah, I love that word. Yep, 71 00:04:03,520 --> 00:04:06,920 Speaker 1: Web's great word. UM an consortium is also awesome. Oh 72 00:04:07,000 --> 00:04:09,520 Speaker 1: yeah that too. So yeah, if you were to go 73 00:04:09,600 --> 00:04:11,560 Speaker 1: and view a web page, if you were to view 74 00:04:11,600 --> 00:04:14,400 Speaker 1: the source of that web page, uh, the you can 75 00:04:14,440 --> 00:04:17,240 Speaker 1: look at the source code. It's essentially it's really just 76 00:04:17,360 --> 00:04:20,159 Speaker 1: a series of directions like what we said, that tell 77 00:04:20,200 --> 00:04:23,960 Speaker 1: the browser what how to lay that page out. And 78 00:04:24,040 --> 00:04:27,640 Speaker 1: so it's not software. HTML is not a programming language. 79 00:04:27,800 --> 00:04:30,760 Speaker 1: It's a markup language. And what happens is that the 80 00:04:30,839 --> 00:04:35,240 Speaker 1: companies that make the web browsers have to incorporate the 81 00:04:35,360 --> 00:04:39,760 Speaker 1: whatever the standard version of HTML happens to be into 82 00:04:39,760 --> 00:04:42,640 Speaker 1: the web browser so that when you access a website, 83 00:04:43,000 --> 00:04:47,800 Speaker 1: it uh it it displays that website the right way 84 00:04:48,000 --> 00:04:52,599 Speaker 1: asterisk asterisk and the asterisk there is that they don't 85 00:04:52,880 --> 00:04:55,719 Speaker 1: have to nobody's telling them. They have to abide by 86 00:04:55,800 --> 00:04:58,360 Speaker 1: all the laws, which has been a point of much 87 00:04:58,400 --> 00:05:02,120 Speaker 1: contention in the past, because UM, there will be a 88 00:05:02,200 --> 00:05:05,560 Speaker 1: standard release. There was HTML two and three, and now, 89 00:05:05,680 --> 00:05:08,719 Speaker 1: as of the time we're recording this in September two 90 00:05:08,720 --> 00:05:12,680 Speaker 1: thousand twelve, the official recognized version of HTML is HTML four. 91 00:05:13,680 --> 00:05:16,760 Speaker 1: UM it's it's been updated a couple of times, and 92 00:05:17,000 --> 00:05:19,480 Speaker 1: people thought that HTML wasn't going to be updated at 93 00:05:19,480 --> 00:05:23,120 Speaker 1: all anymore, that it was essentially dead. But leave that 94 00:05:23,160 --> 00:05:28,919 Speaker 1: for a minute. UM. The thing is UM these these specifications. 95 00:05:29,080 --> 00:05:34,360 Speaker 1: The browser manufacturers Google for Chrome, UH, Apple for Safari 96 00:05:34,400 --> 00:05:38,000 Speaker 1: Opera which is a Norwegian company, Microsoft for i E 97 00:05:38,800 --> 00:05:42,520 Speaker 1: UM Internet Explorer, and and and others. There are many others. UM. 98 00:05:42,560 --> 00:05:45,320 Speaker 1: They basically have to adopt the guts of this thing. 99 00:05:45,480 --> 00:05:47,280 Speaker 1: So if you wanted your text to be bold, you 100 00:05:47,320 --> 00:05:49,800 Speaker 1: can use the old B or you can use the 101 00:05:49,800 --> 00:05:52,960 Speaker 1: newer strong and they're they're all going to recognize that. 102 00:05:53,120 --> 00:05:56,680 Speaker 1: But they're they're usually backwards compatible, so that because if 103 00:05:56,720 --> 00:05:59,760 Speaker 1: they weren't backwards compatible, any web page that had been 104 00:05:59,800 --> 00:06:03,760 Speaker 1: does mine with the old tags would be unrecognizable and 105 00:06:03,760 --> 00:06:06,719 Speaker 1: would not display properly on your screen. So if you 106 00:06:06,960 --> 00:06:08,760 Speaker 1: need to get your MIDI file fixed, you can still 107 00:06:08,800 --> 00:06:12,520 Speaker 1: go back to a page from and observe that. Um. 108 00:06:13,040 --> 00:06:15,640 Speaker 1: But that was the thing for a while, was oh well, 109 00:06:16,200 --> 00:06:19,200 Speaker 1: filling the name of the company here isn't completely compliant 110 00:06:19,200 --> 00:06:22,680 Speaker 1: with the newest standard of HTML. And um, you know, 111 00:06:22,720 --> 00:06:25,719 Speaker 1: Microsoft went on their own for a while, and um 112 00:06:26,080 --> 00:06:28,760 Speaker 1: that was it wasn't the kind of thing that the 113 00:06:28,800 --> 00:06:31,760 Speaker 1: average person would notice. It was more of a tech 114 00:06:32,080 --> 00:06:34,520 Speaker 1: head thing where they were going, well, you know so 115 00:06:34,680 --> 00:06:39,040 Speaker 1: and so it was more compatible. Yeah, so the HTML 116 00:06:39,520 --> 00:06:44,640 Speaker 1: four and also x htmlor UM, which is another type 117 00:06:44,640 --> 00:06:52,039 Speaker 1: of market language, these languages. Well, HTML four anyway, that 118 00:06:52,160 --> 00:06:56,560 Speaker 1: was the latest version, the one that everyone is considered 119 00:06:56,600 --> 00:07:01,640 Speaker 1: the standard. The current standard was released in a late nineties. Yes, 120 00:07:01,880 --> 00:07:06,480 Speaker 1: so you've got this uh, this markup language that's over 121 00:07:06,560 --> 00:07:09,040 Speaker 1: a decade old. And here's the problem. The problem is 122 00:07:09,080 --> 00:07:12,440 Speaker 1: that the markup language as it was designed back then 123 00:07:13,000 --> 00:07:18,040 Speaker 1: could not support some of the more rich Internet UH 124 00:07:18,160 --> 00:07:21,600 Speaker 1: features that we've come to know and love over the years, 125 00:07:22,280 --> 00:07:25,480 Speaker 1: things like video and audio. Stuff that is a more 126 00:07:25,560 --> 00:07:29,360 Speaker 1: of a rich experience was not supported in HTML four. Yeah. 127 00:07:29,400 --> 00:07:31,320 Speaker 1: As a matter of fact, if you go to UH 128 00:07:31,520 --> 00:07:34,960 Speaker 1: many popular sites, um, you're going to and view the 129 00:07:35,000 --> 00:07:38,240 Speaker 1: source as Jonathan suggested a moment ago. You're gonna see HTML, 130 00:07:38,320 --> 00:07:41,240 Speaker 1: but you're also likely to see other stuff in there too, 131 00:07:41,280 --> 00:07:43,480 Speaker 1: And you're gonna say, but, Jonathan and Chris, you told 132 00:07:43,520 --> 00:07:45,760 Speaker 1: me that i'd pretty much be able to read the 133 00:07:45,840 --> 00:07:48,360 Speaker 1: text file in the back end. What's all this other 134 00:07:48,440 --> 00:07:53,000 Speaker 1: programming stuff? Well, it could be JavaScript, which popular, which 135 00:07:53,080 --> 00:07:57,080 Speaker 1: is UH a language, a very mild programming language that 136 00:07:57,120 --> 00:08:00,080 Speaker 1: you can use to add some interactivity to websites. And 137 00:08:00,080 --> 00:08:03,160 Speaker 1: you're also likely to see UH an embed code for 138 00:08:03,400 --> 00:08:08,480 Speaker 1: FLASH on a lot of interactive media sites. UM and 139 00:08:09,160 --> 00:08:12,400 Speaker 1: probably just about everybody listening to this US is UH 140 00:08:12,440 --> 00:08:14,840 Speaker 1: familiar with flash. But it was a technology developed by 141 00:08:14,920 --> 00:08:20,200 Speaker 1: the UH design software company Macromedia before it merged with Adobe, 142 00:08:21,000 --> 00:08:26,160 Speaker 1: UH slash acquired by Adobe, and UM. Basically, UH flash 143 00:08:26,160 --> 00:08:31,720 Speaker 1: has been the standard for many years for designing rich 144 00:08:32,240 --> 00:08:36,800 Speaker 1: Internet content, animations, embedding video and things not not YouTube 145 00:08:36,880 --> 00:08:40,240 Speaker 1: videos or things like that or vino. But you know, 146 00:08:40,440 --> 00:08:43,680 Speaker 1: special people would produce these things in house and put 147 00:08:43,720 --> 00:08:46,400 Speaker 1: them on their websites, or they would contract a designer 148 00:08:46,440 --> 00:08:49,280 Speaker 1: to put this kind of interactive content on there. A 149 00:08:49,280 --> 00:08:51,120 Speaker 1: lot of shopping sites like to use it so you 150 00:08:51,120 --> 00:08:54,560 Speaker 1: can customize your room or things the UM and and 151 00:08:54,600 --> 00:08:59,680 Speaker 1: so HTML itself doesn't have any way to do that 152 00:09:00,040 --> 00:09:02,719 Speaker 1: kind of content. Now, you can link to something, you 153 00:09:02,760 --> 00:09:06,800 Speaker 1: can embed an image, UM or or files on the site, 154 00:09:06,800 --> 00:09:08,600 Speaker 1: but you might if you click on that file, it 155 00:09:08,720 --> 00:09:13,400 Speaker 1: might just load in another UM another kind of application, 156 00:09:13,480 --> 00:09:16,400 Speaker 1: for example UM. So it really didn't support it the 157 00:09:16,440 --> 00:09:19,480 Speaker 1: way that it could be done if you used flash 158 00:09:19,760 --> 00:09:21,640 Speaker 1: for example. Right, So instead what you would have to 159 00:09:21,640 --> 00:09:24,920 Speaker 1: do is install these plug ins into your browser. So 160 00:09:24,960 --> 00:09:28,800 Speaker 1: these are plug ins or extensions that would make your 161 00:09:29,080 --> 00:09:33,400 Speaker 1: browser capable of seeing this kind of information, because again, 162 00:09:33,440 --> 00:09:36,160 Speaker 1: on their own, they might not necessarily be able to 163 00:09:36,160 --> 00:09:38,559 Speaker 1: do that. So if you've ever gone to a website 164 00:09:38,559 --> 00:09:40,960 Speaker 1: and it's prompted you to install a plug in, first 165 00:09:40,960 --> 00:09:44,520 Speaker 1: of all, be careful, yes, because that's a very common 166 00:09:44,559 --> 00:09:48,720 Speaker 1: technique of installing malware onto your computer. If it's if 167 00:09:48,720 --> 00:09:52,160 Speaker 1: it's a site that you trust, and you feel reasonably 168 00:09:52,200 --> 00:09:55,720 Speaker 1: sure that there's not any uh hanky nor panky going 169 00:09:55,800 --> 00:09:59,240 Speaker 1: on at that particular moment, then that might be what 170 00:09:59,360 --> 00:10:01,360 Speaker 1: you need. You might to install a plug in order 171 00:10:01,360 --> 00:10:03,560 Speaker 1: to view whatever that content is or interact with that 172 00:10:03,679 --> 00:10:07,360 Speaker 1: site in some way. So that was one of the 173 00:10:07,400 --> 00:10:11,440 Speaker 1: reasons why, uh, there there needed to be this update 174 00:10:11,480 --> 00:10:15,320 Speaker 1: to HTML was to design a markup language that was 175 00:10:16,440 --> 00:10:18,920 Speaker 1: backwards compatible so that you could still see those old sites, 176 00:10:18,960 --> 00:10:23,480 Speaker 1: but also more streamlined again, so that someone who's building 177 00:10:23,520 --> 00:10:27,280 Speaker 1: something from the ground up starting with HTML five would 178 00:10:27,280 --> 00:10:30,400 Speaker 1: be able to do so without it being too confusing. 179 00:10:30,480 --> 00:10:32,880 Speaker 1: They didn't want the barrier to be too high, and 180 00:10:32,920 --> 00:10:36,320 Speaker 1: also they wanted to be able to natively support these 181 00:10:36,440 --> 00:10:41,440 Speaker 1: rich Internet interactions without the requirement of some sort of 182 00:10:41,600 --> 00:10:45,680 Speaker 1: additional plug in. So this is what kind of prompted 183 00:10:46,280 --> 00:10:50,680 Speaker 1: companies like Apple in particular to push for HTML five 184 00:10:50,800 --> 00:10:55,960 Speaker 1: because the uh, the alternative is to support all these plugins, 185 00:10:56,120 --> 00:11:00,320 Speaker 1: and if there were just one type of plug for 186 00:11:00,400 --> 00:11:05,680 Speaker 1: each type of rich media kind of experience, maybe that 187 00:11:05,679 --> 00:11:07,880 Speaker 1: wouldn't be such a big deal. You know. It would 188 00:11:07,880 --> 00:11:10,520 Speaker 1: mean that perhaps the browser would be clunkier than it 189 00:11:10,559 --> 00:11:13,160 Speaker 1: needed to be, but you would have that one solution. 190 00:11:13,200 --> 00:11:16,320 Speaker 1: But the fact is, there's not just one solution. For 191 00:11:16,360 --> 00:11:19,319 Speaker 1: a while, there were there were a few different competing 192 00:11:19,400 --> 00:11:21,880 Speaker 1: technologies that we're all doing the same sort of thing. 193 00:11:22,400 --> 00:11:24,080 Speaker 1: But it would mean that, you know, you could be 194 00:11:24,080 --> 00:11:27,160 Speaker 1: watching video on one site and everything's fine, and then 195 00:11:27,200 --> 00:11:28,839 Speaker 1: you would go to a different site and suddenly it 196 00:11:28,840 --> 00:11:31,439 Speaker 1: would prompt you to get a different kind of plug 197 00:11:31,440 --> 00:11:34,080 Speaker 1: in because the plug and you were using does not 198 00:11:34,200 --> 00:11:36,880 Speaker 1: work with that particular video. So the two in particular, 199 00:11:36,920 --> 00:11:39,319 Speaker 1: I'm thinking of our flash and silver Light. Yes, a 200 00:11:39,360 --> 00:11:42,920 Speaker 1: silver light came from Microsoft, and uh, anyone who was 201 00:11:42,920 --> 00:11:46,480 Speaker 1: watching um I remember in the two thousand I think 202 00:11:46,480 --> 00:11:49,520 Speaker 1: it was a two thousand eight Olympics where if you 203 00:11:49,559 --> 00:11:51,959 Speaker 1: wanted to watch the stuff online you had to use 204 00:11:52,000 --> 00:11:55,040 Speaker 1: silver light, at least in the United States, And so 205 00:11:55,320 --> 00:11:58,320 Speaker 1: U that meant that I installed silver Light on my 206 00:11:58,360 --> 00:12:00,640 Speaker 1: computer because I wanted to watch some of the stuff. 207 00:12:01,080 --> 00:12:04,040 Speaker 1: And and you know, it's it's just not an ideal 208 00:12:04,080 --> 00:12:06,520 Speaker 1: solution in the sense that you know, you've got a 209 00:12:06,520 --> 00:12:09,800 Speaker 1: browser that's getting heavier and heavier as far as code 210 00:12:09,840 --> 00:12:12,040 Speaker 1: is going, because you're plugging in all this stuff. It 211 00:12:12,040 --> 00:12:14,480 Speaker 1: would be nicer if it were all built in from 212 00:12:14,520 --> 00:12:16,920 Speaker 1: the ground up and you didn't have to worry about that. 213 00:12:17,520 --> 00:12:19,520 Speaker 1: So that was one of the reasons for HTMO five. 214 00:12:19,600 --> 00:12:24,559 Speaker 1: Another was that we're slowly getting closer to this idea 215 00:12:24,559 --> 00:12:29,760 Speaker 1: of the semantic web, where the web is quote unquote 216 00:12:29,760 --> 00:12:32,440 Speaker 1: getting smarter. And what I mean by that is that 217 00:12:32,559 --> 00:12:36,600 Speaker 1: it's easier for you to access the information you are 218 00:12:36,640 --> 00:12:41,840 Speaker 1: particularly interested in. So if I'm doing a search for 219 00:12:42,760 --> 00:12:47,080 Speaker 1: a very specific type of information with the semantic Web, 220 00:12:47,440 --> 00:12:51,800 Speaker 1: I would ideally get precisely what I needed from that, 221 00:12:51,880 --> 00:12:54,440 Speaker 1: and not just a bunch of links to things that 222 00:12:54,600 --> 00:12:57,160 Speaker 1: may or may not have the answer to my question. 223 00:12:57,920 --> 00:13:02,400 Speaker 1: Uh So, h g mL five has organizational tags in it, 224 00:13:02,800 --> 00:13:07,000 Speaker 1: things like section or article or side or header that 225 00:13:07,120 --> 00:13:09,719 Speaker 1: can help when you're doing a search. It can help 226 00:13:09,760 --> 00:13:15,400 Speaker 1: identify things that are more important within the confines of 227 00:13:15,440 --> 00:13:17,719 Speaker 1: that web page than others. So that way, let's say 228 00:13:17,720 --> 00:13:20,280 Speaker 1: that you're a web page developer and you've used these 229 00:13:20,280 --> 00:13:23,960 Speaker 1: tags to kind of organize your web page. You've got 230 00:13:23,960 --> 00:13:27,200 Speaker 1: an entire section that's about the search terms that I'm 231 00:13:27,200 --> 00:13:30,040 Speaker 1: looking for. It's more likely that that's going to come 232 00:13:30,120 --> 00:13:32,360 Speaker 1: up for me when I'm using some sort of search tool, 233 00:13:32,880 --> 00:13:35,360 Speaker 1: because you have laid it out in such a way 234 00:13:35,400 --> 00:13:38,720 Speaker 1: that the search engine knows, hey, this is a section 235 00:13:38,800 --> 00:13:43,079 Speaker 1: that directly pertains to the search terms that were entered. Um, 236 00:13:43,200 --> 00:13:46,880 Speaker 1: so those were that's also another consideration. So HTML five 237 00:13:47,840 --> 00:13:51,120 Speaker 1: has really had a big push, particularly from companies like Apple, 238 00:13:51,240 --> 00:13:55,760 Speaker 1: over the last well several years, actually UH, and that 239 00:13:56,160 --> 00:13:58,400 Speaker 1: has been the battle cry for a lot of these 240 00:13:58,440 --> 00:14:02,520 Speaker 1: companies that HTML five is the future. You should stop 241 00:14:02,559 --> 00:14:06,400 Speaker 1: developing for things like flash and other plug ins because 242 00:14:06,520 --> 00:14:09,600 Speaker 1: that's just holding us back. Instead, put your energy toward 243 00:14:09,760 --> 00:14:13,360 Speaker 1: getting the HTML five to a complete standard, because as 244 00:14:13,360 --> 00:14:17,720 Speaker 1: it stands now, it's still being developed. Yeah, the UH 245 00:14:17,880 --> 00:14:22,040 Speaker 1: HTML five, for all of its uh prominence in the 246 00:14:22,080 --> 00:14:24,960 Speaker 1: tech news in the last couple of years, UM, you 247 00:14:24,960 --> 00:14:28,520 Speaker 1: you would think that it was fairly new. But an 248 00:14:28,600 --> 00:14:32,560 Speaker 1: organization called what would well Okay, that's my best guess 249 00:14:32,560 --> 00:14:35,000 Speaker 1: on how to pronounce it, w h A t w G. 250 00:14:35,200 --> 00:14:39,480 Speaker 1: That's the Web Hypertext Application Technology Working Group. Basically, it's 251 00:14:39,520 --> 00:14:45,840 Speaker 1: a group of companies or organizations that decided to UH 252 00:14:45,880 --> 00:14:51,280 Speaker 1: put their efforts together and update HTML. The idea is, UH, 253 00:14:51,280 --> 00:14:54,000 Speaker 1: you know, or behind it was, hey, we don't you know, 254 00:14:54,360 --> 00:14:59,120 Speaker 1: HTML by itself can't do what we wanted to do, 255 00:14:59,160 --> 00:15:01,320 Speaker 1: what we want to be able to make available to 256 00:15:01,360 --> 00:15:04,200 Speaker 1: our customers. So let's see if we can come up 257 00:15:04,240 --> 00:15:08,240 Speaker 1: with a new standard. And back in two thousand four, UM, 258 00:15:08,440 --> 00:15:13,680 Speaker 1: Apple Mozilla, which is the organization behind the Firefox browser 259 00:15:14,240 --> 00:15:19,080 Speaker 1: and opera software UM got together and said, let's UH, 260 00:15:19,120 --> 00:15:21,800 Speaker 1: you know, we're we don't really like this extensible h 261 00:15:21,920 --> 00:15:25,000 Speaker 1: t m L x HTML that W three C is 262 00:15:25,000 --> 00:15:28,320 Speaker 1: working on. Let's see if we can come up with 263 00:15:28,360 --> 00:15:31,240 Speaker 1: something we like better and then we'll present it um 264 00:15:31,320 --> 00:15:35,400 Speaker 1: And so for a while, X HTML and HTML five 265 00:15:35,720 --> 00:15:39,200 Speaker 1: were competing standards, with x t X h t m 266 00:15:39,320 --> 00:15:41,520 Speaker 1: L in the lead. It looks like that was going 267 00:15:41,560 --> 00:15:43,320 Speaker 1: to be the successor to h t m L four. 268 00:15:45,080 --> 00:15:49,880 Speaker 1: I think what eventually forced HTML five into prominence was 269 00:15:50,600 --> 00:15:53,800 Speaker 1: the uh that this was on the pre post PC era. 270 00:15:54,520 --> 00:15:57,280 Speaker 1: But now now that we're talking about tablets, so the 271 00:15:57,360 --> 00:15:59,680 Speaker 1: pre post PC era, that might just be the PC 272 00:16:00,080 --> 00:16:05,920 Speaker 1: RU stop messing with my head. Uh No. I said 273 00:16:05,960 --> 00:16:09,160 Speaker 1: that on purpose to see if you're I was listening 274 00:16:09,240 --> 00:16:13,480 Speaker 1: or if I was just so uh so, yeah, I 275 00:16:13,480 --> 00:16:15,240 Speaker 1: mean this is this is one of those things where 276 00:16:15,240 --> 00:16:17,000 Speaker 1: they said, okay, let's see what what we can come 277 00:16:17,080 --> 00:16:20,960 Speaker 1: up with. And so HTML five again isn't it hasn't 278 00:16:20,960 --> 00:16:24,560 Speaker 1: been ratified, it hasn't been standardized, but uh, it was 279 00:16:24,600 --> 00:16:28,160 Speaker 1: forced into the media when the I think when the 280 00:16:28,200 --> 00:16:33,280 Speaker 1: iPad came out in two thousand ten, because basically Apple 281 00:16:34,000 --> 00:16:37,120 Speaker 1: bet on HTML five. Now it's one of the members, 282 00:16:37,320 --> 00:16:41,360 Speaker 1: one of the founding members of what would So you 283 00:16:41,360 --> 00:16:44,280 Speaker 1: would say, well, okay, sure they're promoting their own standard. 284 00:16:44,880 --> 00:16:50,000 Speaker 1: Um Apple's argument and leaving flash off the iPad and 285 00:16:50,080 --> 00:16:54,400 Speaker 1: the iPhone and the iPod Touch. Um It's basically, look, 286 00:16:54,840 --> 00:16:57,040 Speaker 1: flash can be a resource hog. It takes a lot 287 00:16:57,280 --> 00:16:59,840 Speaker 1: of processing power to run this. It's gonna slow you down. 288 00:17:00,400 --> 00:17:04,280 Speaker 1: You're on, on on using these gadgets, and we're just 289 00:17:04,359 --> 00:17:07,200 Speaker 1: not gonna put flash on this. Also, it was going 290 00:17:07,240 --> 00:17:10,680 Speaker 1: to drain your battery because it was such a it 291 00:17:10,800 --> 00:17:13,199 Speaker 1: was taking up so many resources, which in turn required 292 00:17:13,200 --> 00:17:17,000 Speaker 1: more power that you would end up having a mobile 293 00:17:17,000 --> 00:17:19,119 Speaker 1: device that would have a useful battery life of a 294 00:17:19,160 --> 00:17:23,040 Speaker 1: few hours, which you know is not acceptable if you're 295 00:17:23,160 --> 00:17:26,120 Speaker 1: looking for something like a mobile phone. I mean, most 296 00:17:26,160 --> 00:17:28,800 Speaker 1: of us don't plug our phones in every couple of 297 00:17:28,800 --> 00:17:32,000 Speaker 1: hours to recharge, and if we had to, I think 298 00:17:32,000 --> 00:17:36,120 Speaker 1: most of us would be dissatisfied with that experience. Yeah. Now, 299 00:17:36,160 --> 00:17:39,440 Speaker 1: of course, uh, the the iPhone and iPod Touch predate 300 00:17:39,480 --> 00:17:41,760 Speaker 1: the iPad, and it was apparent that flash was not 301 00:17:41,840 --> 00:17:44,560 Speaker 1: going on those anytime soon. But I think the iPad really, 302 00:17:45,080 --> 00:17:47,159 Speaker 1: the launch of the iPad really brought it into relief. 303 00:17:47,200 --> 00:17:49,160 Speaker 1: They said Hey, if you got a device this big, 304 00:17:49,160 --> 00:17:51,280 Speaker 1: if you can look at web pages on this thing, 305 00:17:51,280 --> 00:17:55,560 Speaker 1: it's intended for surfing in part, why wouldn't you include flash? 306 00:17:55,600 --> 00:17:58,199 Speaker 1: Come on, Steve, But he said, nope, I'm not going 307 00:17:58,280 --> 00:17:59,800 Speaker 1: to do it. Apple is not going to do it. 308 00:18:00,119 --> 00:18:03,359 Speaker 1: You're on your own. And some other big companies have really, 309 00:18:03,880 --> 00:18:08,160 Speaker 1: uh at least at least capitulated to that sort of view, 310 00:18:08,200 --> 00:18:11,880 Speaker 1: if not like wholeheartedly thrown in, some of them have 311 00:18:12,800 --> 00:18:16,959 Speaker 1: have have started to to acquiesce to to say, all right, 312 00:18:17,000 --> 00:18:19,800 Speaker 1: you know the writings on the wall, this this has 313 00:18:19,880 --> 00:18:22,679 Speaker 1: to change. And there's so much momentum going forward that 314 00:18:22,720 --> 00:18:26,000 Speaker 1: we're going to back HTML five even if we're not 315 00:18:26,040 --> 00:18:28,640 Speaker 1: going to champion it. Um, there there are a lot 316 00:18:28,680 --> 00:18:32,360 Speaker 1: of examples out there. I mean, heck, YouTube has has 317 00:18:32,440 --> 00:18:36,160 Speaker 1: an opt in service where you can view the videos 318 00:18:36,280 --> 00:18:40,000 Speaker 1: via HTML five as opposed to flash based players. So 319 00:18:40,960 --> 00:18:42,720 Speaker 1: that was a big That was a big thing. I mean, 320 00:18:42,760 --> 00:18:44,840 Speaker 1: you think about how many videos are up on YouTube. 321 00:18:44,960 --> 00:18:48,119 Speaker 1: That's a massive undertaking. Yeah, yeah, that was that. That 322 00:18:48,280 --> 00:18:52,000 Speaker 1: actually is a good point because, um, you couldn't go 323 00:18:52,160 --> 00:18:58,240 Speaker 1: to YouTube and view videos on the iPad when it 324 00:18:58,280 --> 00:19:01,359 Speaker 1: first came out, because it was flash based players. Yeah, 325 00:19:01,600 --> 00:19:04,159 Speaker 1: and uh that that's one of the reasons that they've 326 00:19:04,880 --> 00:19:08,040 Speaker 1: that Apple has had that YouTube app that it recently 327 00:19:08,160 --> 00:19:10,600 Speaker 1: did away with from iOS six. There was a native 328 00:19:10,640 --> 00:19:15,639 Speaker 1: app on iOS that would allow you to access certain 329 00:19:15,800 --> 00:19:19,920 Speaker 1: YouTube videos that that we're compatible with that app, So 330 00:19:20,000 --> 00:19:22,760 Speaker 1: that would that was sort of Apple's answer and Google's answer, 331 00:19:23,680 --> 00:19:26,720 Speaker 1: uh in the short term, while there was this initiative 332 00:19:26,760 --> 00:19:30,400 Speaker 1: to try and convert videos from flash based to HTML 333 00:19:30,480 --> 00:19:35,199 Speaker 1: five based videos. So um so yeah, I mean that 334 00:19:35,320 --> 00:19:37,600 Speaker 1: this is when people started going, well, or you know, 335 00:19:37,720 --> 00:19:40,520 Speaker 1: which side are you on? Are you on the HTML 336 00:19:40,640 --> 00:19:42,919 Speaker 1: five side or are you on the flash side? Come on? 337 00:19:43,000 --> 00:19:45,640 Speaker 1: Flashes is lovely. It does all the things we needed 338 00:19:45,680 --> 00:19:48,600 Speaker 1: to do. There are so many flash games. Um. Facebook 339 00:19:48,680 --> 00:19:51,000 Speaker 1: was one of those companies in particular that was sort 340 00:19:51,040 --> 00:19:55,560 Speaker 1: of um, I think, uh sort of a battleground if 341 00:19:55,600 --> 00:19:59,680 Speaker 1: you will, because so much traffic on Facebook uh involves 342 00:19:59,760 --> 00:20:04,080 Speaker 1: rich media content, especially the games and other applications that 343 00:20:04,080 --> 00:20:07,520 Speaker 1: that people run on there. So um and of course 344 00:20:07,760 --> 00:20:12,760 Speaker 1: Facebook having uh you know, a billion people more or less. Uh, 345 00:20:12,840 --> 00:20:15,639 Speaker 1: that's a whole lot of web traffic and and and 346 00:20:15,840 --> 00:20:19,560 Speaker 1: organizations like YouTube and Facebook are going to be the 347 00:20:19,840 --> 00:20:23,000 Speaker 1: places where they're sort of litmus tests for the rest 348 00:20:23,000 --> 00:20:25,719 Speaker 1: of the web. You know, do you have rich media content? 349 00:20:25,840 --> 00:20:30,080 Speaker 1: If so, how are you displaying it? So yeah, YouTube 350 00:20:30,320 --> 00:20:34,120 Speaker 1: chose to make its pages render in HTML five, So 351 00:20:34,440 --> 00:20:38,000 Speaker 1: pointing Facebook, going back to Facebook, Facebook, this is an 352 00:20:38,080 --> 00:20:43,600 Speaker 1: interesting and somewhat I don't know if controversial is the 353 00:20:43,720 --> 00:20:46,280 Speaker 1: right word for it, but there are people have there 354 00:20:46,280 --> 00:20:49,960 Speaker 1: have been arguments that have broken out online about what 355 00:20:50,160 --> 00:20:54,920 Speaker 1: Mark Zuckerberg said in September two twelve about face Facebook 356 00:20:54,920 --> 00:20:58,320 Speaker 1: and HTML five. He actually said, essentially, our biggest mistake 357 00:20:58,359 --> 00:21:01,639 Speaker 1: was betting too much on h GML five and this 358 00:21:02,000 --> 00:21:07,440 Speaker 1: I read this originally in tech crunch Um. But the 359 00:21:07,440 --> 00:21:10,960 Speaker 1: the problem was that they Facebook had a choice. They 360 00:21:10,960 --> 00:21:15,920 Speaker 1: could either develop apps for HTML five, thinking well, this 361 00:21:16,000 --> 00:21:19,800 Speaker 1: is the ideal situation, because if this is the standard, 362 00:21:20,240 --> 00:21:23,879 Speaker 1: then everyone is going to incorporate HTML five in their products, 363 00:21:24,280 --> 00:21:27,080 Speaker 1: which means we don't have to sit there and create 364 00:21:27,160 --> 00:21:30,840 Speaker 1: a native application for each operating system that's on a 365 00:21:30,880 --> 00:21:34,359 Speaker 1: mobile device. Is primarily for mobile here that we're talking about. 366 00:21:35,240 --> 00:21:39,480 Speaker 1: So they thought, all right, let's throw let's throw all 367 00:21:39,560 --> 00:21:42,040 Speaker 1: we have into HTML five and start developing for it. 368 00:21:42,040 --> 00:21:44,560 Speaker 1: But then they discovered a problem and the problem is 369 00:21:44,600 --> 00:21:49,000 Speaker 1: that ht mm L five is not fully baked and 370 00:21:49,119 --> 00:21:52,840 Speaker 1: the implementation of it in hardware is not fully baked, 371 00:21:52,960 --> 00:21:57,880 Speaker 1: so it's not They were discovering that the the experience 372 00:21:57,920 --> 00:22:01,600 Speaker 1: that users were having on HTML i've based apps on 373 00:22:01,680 --> 00:22:06,200 Speaker 1: these devices was not ideal. That things were slow, certain 374 00:22:06,240 --> 00:22:11,640 Speaker 1: features weren't weren't supported through HTML five UM, and it 375 00:22:11,720 --> 00:22:14,399 Speaker 1: just was it was not a great experience. And so 376 00:22:14,440 --> 00:22:17,800 Speaker 1: people were like, this app is terrible, and people were 377 00:22:17,840 --> 00:22:20,800 Speaker 1: reviewing apps saying, this app is awful because it takes 378 00:22:20,840 --> 00:22:24,240 Speaker 1: forever considering what I'm asking it to do. I can't 379 00:22:24,280 --> 00:22:26,879 Speaker 1: believe it takes so long for me to accomplish these goals. 380 00:22:27,359 --> 00:22:29,200 Speaker 1: And so that was one of the issues. And then 381 00:22:29,359 --> 00:22:33,080 Speaker 1: they said, well, if we had instead spent all that 382 00:22:33,240 --> 00:22:38,919 Speaker 1: time and energy and thought on designing native applications for 383 00:22:39,080 --> 00:22:44,200 Speaker 1: these devices, they could take advantage of each devices UH 384 00:22:44,320 --> 00:22:48,479 Speaker 1: hardware capabilities and UH and their operating systems in a 385 00:22:48,520 --> 00:22:51,480 Speaker 1: way that would be a much more satisfying experience for 386 00:22:51,520 --> 00:22:55,400 Speaker 1: the user. Even though that means that we are contributing 387 00:22:55,400 --> 00:23:00,320 Speaker 1: to this sort of fragmented approach to developing apps. And 388 00:23:01,400 --> 00:23:04,239 Speaker 1: you know, this was a big This caused a lot 389 00:23:04,320 --> 00:23:06,399 Speaker 1: of Uh, it was a bit of a kerfuffle that 390 00:23:06,480 --> 00:23:08,520 Speaker 1: fall fell out about this, and I think part of 391 00:23:08,560 --> 00:23:12,920 Speaker 1: the problem is that HTML five is a little too 392 00:23:13,640 --> 00:23:17,120 Speaker 1: It's it's not ready for prime time yet, and that 393 00:23:17,320 --> 00:23:22,160 Speaker 1: the hardware and the the hardware is not really there 394 00:23:22,160 --> 00:23:26,160 Speaker 1: to support it. The markup language is not mature enough yet, 395 00:23:26,720 --> 00:23:29,680 Speaker 1: the implementation of it is not mature enough yet, so 396 00:23:30,119 --> 00:23:34,840 Speaker 1: the experience is not, uh, not going to be great 397 00:23:35,080 --> 00:23:38,760 Speaker 1: across the board, particularly in the mobile world, and that 398 00:23:39,080 --> 00:23:42,840 Speaker 1: perhaps a couple of years down the line, HTML five 399 00:23:42,880 --> 00:23:46,439 Speaker 1: will be the obvious answer, right but right now it's not. 400 00:23:46,560 --> 00:23:48,600 Speaker 1: And the problem is Facebook jumped on it a little 401 00:23:48,600 --> 00:23:55,879 Speaker 1: too early. Yeah, and people, of course, uh initially when 402 00:23:55,960 --> 00:23:58,159 Speaker 1: that comment came out, I think it it caused the 403 00:23:58,280 --> 00:24:02,879 Speaker 1: sturb because it was pretty strongly worded. I've seen several 404 00:24:02,920 --> 00:24:05,240 Speaker 1: commentaries and said, well, you know, it's probably not their 405 00:24:05,480 --> 00:24:10,639 Speaker 1: biggest mistake ever. Um, but yeah, I mean it's so 406 00:24:10,880 --> 00:24:13,800 Speaker 1: it's so hard to tell at this point what is 407 00:24:13,920 --> 00:24:17,160 Speaker 1: and what isn't going to be in the final implementation 408 00:24:17,200 --> 00:24:21,280 Speaker 1: of HTML five. But development has been steady on it 409 00:24:21,320 --> 00:24:26,080 Speaker 1: since it's been announced and adopted by so many companies. 410 00:24:26,119 --> 00:24:29,800 Speaker 1: So um, yeah, I think betting the farm on it 411 00:24:29,960 --> 00:24:33,680 Speaker 1: or betting the farmville. I see what you did there, 412 00:24:34,480 --> 00:24:38,240 Speaker 1: Uh might might be a bit extreme. Uh yeah, there 413 00:24:38,280 --> 00:24:41,040 Speaker 1: there There have been some HTML five games and things 414 00:24:41,040 --> 00:24:43,800 Speaker 1: that I've seen pop up on Facebook. The majority of 415 00:24:43,800 --> 00:24:47,680 Speaker 1: them are still baked in flash. UM. But yeah, I 416 00:24:47,720 --> 00:24:52,760 Speaker 1: mean even even Adobe whose product flash is um has 417 00:24:52,800 --> 00:24:55,880 Speaker 1: been backing off to some degree. I mean even even 418 00:24:56,080 --> 00:25:00,400 Speaker 1: h Flash for Android has been discontinued officially UM. And and 419 00:25:00,160 --> 00:25:04,240 Speaker 1: and it appears that they have gone into the business 420 00:25:04,280 --> 00:25:08,800 Speaker 1: of building HTML five encoding tools, which uh, you know 421 00:25:08,880 --> 00:25:13,959 Speaker 1: would seem to be the smart move. So yeah. Uh. 422 00:25:14,119 --> 00:25:16,440 Speaker 1: The thing is that it also goes into the whole 423 00:25:16,600 --> 00:25:19,560 Speaker 1: is it the web or is it mobile app? See 424 00:25:19,560 --> 00:25:23,240 Speaker 1: that's a That's another interesting point is that when the 425 00:25:23,280 --> 00:25:26,240 Speaker 1: when the when HTML five, when they were starting to 426 00:25:26,280 --> 00:25:29,920 Speaker 1: develop it for HTML five, that was pre mobile, I mean, 427 00:25:29,960 --> 00:25:34,000 Speaker 1: before smartphones had really hit the consumer market, before tablets 428 00:25:34,000 --> 00:25:37,000 Speaker 1: had really hit the consumer market. You're talking about, you know, 429 00:25:37,040 --> 00:25:42,000 Speaker 1: the original When first looking into HTML five, you're almost 430 00:25:42,080 --> 00:25:45,119 Speaker 1: looking at two different branches of the web. Because there's 431 00:25:45,160 --> 00:25:48,280 Speaker 1: the computer experience, which you know, a lot of us 432 00:25:48,320 --> 00:25:50,800 Speaker 1: are familiar with because that's how we learned to use 433 00:25:50,840 --> 00:25:53,320 Speaker 1: the web that was that was the way the main 434 00:25:53,359 --> 00:25:56,720 Speaker 1: way to use the web, and now mobile is increasingly 435 00:25:56,800 --> 00:25:59,399 Speaker 1: taking that over and becoming the dominant way that a 436 00:25:59,440 --> 00:26:02,560 Speaker 1: lot of people are rely upon in order to access 437 00:26:02,560 --> 00:26:06,480 Speaker 1: the web. So it means that while while the considerations 438 00:26:06,520 --> 00:26:09,439 Speaker 1: you made for this markup language might have made perfect 439 00:26:09,440 --> 00:26:13,520 Speaker 1: sense for a desktop or laptop computer that has access 440 00:26:13,560 --> 00:26:17,280 Speaker 1: to greater resources than your typical mobile device does, now 441 00:26:17,320 --> 00:26:21,639 Speaker 1: you have to rethink all that again because you're talking about, uh, 442 00:26:22,160 --> 00:26:25,399 Speaker 1: you know, the mobile approach, and it's not necessarily the 443 00:26:25,400 --> 00:26:27,919 Speaker 1: people behind HTML five that have to do the rethinking. 444 00:26:28,600 --> 00:26:32,040 Speaker 1: It's the hardware developers and the operating system developers who 445 00:26:32,080 --> 00:26:35,760 Speaker 1: have to really consider how to implement this in a 446 00:26:35,800 --> 00:26:39,359 Speaker 1: way that fits in the mobile world. And remember the 447 00:26:39,400 --> 00:26:43,520 Speaker 1: mobile world, you've got several challenges battery life, like we 448 00:26:43,560 --> 00:26:47,359 Speaker 1: mentioned as a challenge limited resources because in general, you 449 00:26:47,400 --> 00:26:50,640 Speaker 1: tend to have lower powered chips because lower powered chips 450 00:26:50,640 --> 00:26:54,040 Speaker 1: are going to drain a battery more slowly, and they 451 00:26:54,119 --> 00:26:56,920 Speaker 1: generate less heat, which is important for a mobile device. 452 00:26:57,600 --> 00:27:00,239 Speaker 1: And you're going to have a different form factor. So 453 00:27:01,040 --> 00:27:04,400 Speaker 1: all of those things play into designing the operating system 454 00:27:04,520 --> 00:27:07,960 Speaker 1: and its capabilities and features. In a mobile platform as 455 00:27:08,000 --> 00:27:11,360 Speaker 1: well as you know, how do we implement this HTML five, 456 00:27:11,400 --> 00:27:13,080 Speaker 1: what's it going to look like in the mobile space, 457 00:27:13,080 --> 00:27:15,200 Speaker 1: how's it going to behave, how's it going to access 458 00:27:15,880 --> 00:27:19,080 Speaker 1: the resources we have when we try to render a 459 00:27:19,160 --> 00:27:24,320 Speaker 1: web page that is um that has been built through 460 00:27:24,480 --> 00:27:28,199 Speaker 1: HTML five. So it's it's you know, it's not a 461 00:27:28,400 --> 00:27:31,440 Speaker 1: simple answer, because it's not oh well, you just need 462 00:27:31,480 --> 00:27:34,560 Speaker 1: to change this one aspect of HTML five and everything 463 00:27:34,560 --> 00:27:37,800 Speaker 1: works perfectly. No, it's it's more of that relationship of 464 00:27:37,800 --> 00:27:41,199 Speaker 1: operating system to hardware where there's going to be a 465 00:27:41,240 --> 00:27:43,880 Speaker 1: bit of a bottleneck, at least in the short term. 466 00:27:43,920 --> 00:27:46,480 Speaker 1: It may very well be that in a year or 467 00:27:46,520 --> 00:27:49,919 Speaker 1: two years will have some breakthroughs where the because of 468 00:27:50,280 --> 00:27:53,879 Speaker 1: architecture or because of operating system design, that no longer 469 00:27:53,920 --> 00:27:57,639 Speaker 1: becomes a real issue. And HTML five is the obvious answer. 470 00:27:57,720 --> 00:28:01,080 Speaker 1: But for right now, that native app approach looks like 471 00:28:01,160 --> 00:28:05,520 Speaker 1: that makes more sense, at least for Facebook. Yeah. Yeah, 472 00:28:05,600 --> 00:28:08,320 Speaker 1: and uh, you know, as Matta say said, you know, 473 00:28:08,359 --> 00:28:11,800 Speaker 1: it's also in the implementation too. It's not just the 474 00:28:11,960 --> 00:28:13,440 Speaker 1: h t m L five, it's the way it was 475 00:28:13,560 --> 00:28:15,720 Speaker 1: rolled out. I'm sure once they've had an opportunity to 476 00:28:15,760 --> 00:28:21,040 Speaker 1: you to retreat and regather uh their resources that you 477 00:28:21,080 --> 00:28:22,960 Speaker 1: know that will be able to do that. But you know, 478 00:28:23,040 --> 00:28:26,640 Speaker 1: it does affect so many people that you know, building 479 00:28:27,760 --> 00:28:31,080 Speaker 1: you know, building any architecture. We've talked about the many 480 00:28:31,119 --> 00:28:35,000 Speaker 1: times that there have been redesigns and outcries and whatnot. Sure, 481 00:28:35,280 --> 00:28:37,919 Speaker 1: so yes, there's at least a brew haha if not 482 00:28:38,000 --> 00:28:40,680 Speaker 1: a kerfuffle. Yes, yes, I would agree there is at 483 00:28:40,760 --> 00:28:43,400 Speaker 1: least a brew haha, which as you know, is three 484 00:28:43,400 --> 00:28:48,680 Speaker 1: brooms short of a kerfuffle, but six brooms more than shenanigans. 485 00:28:48,720 --> 00:28:52,360 Speaker 1: So um yeah, it's uh, it'll be interesting to see 486 00:28:52,400 --> 00:28:56,000 Speaker 1: how this develops. I'm sure we will continue to see 487 00:28:56,280 --> 00:29:00,880 Speaker 1: developments in HTML five as well as its implementation. Uh 488 00:29:00,960 --> 00:29:02,840 Speaker 1: and and like I said, maybe a couple of years 489 00:29:02,880 --> 00:29:05,160 Speaker 1: down the road, that will be what everyone develops in 490 00:29:05,240 --> 00:29:07,160 Speaker 1: because it saves so much time to do it through 491 00:29:07,280 --> 00:29:11,720 Speaker 1: HTML five as opposed to designing native apps for you know, however, 492 00:29:11,800 --> 00:29:14,400 Speaker 1: many operating systems are out there. Granted, it may very 493 00:29:14,400 --> 00:29:17,080 Speaker 1: well be that the operating systems that are out there 494 00:29:17,520 --> 00:29:22,440 Speaker 1: boiled down to uh you know, Windows eight, iOS and 495 00:29:22,440 --> 00:29:25,480 Speaker 1: and Android, but you never know, we could still see 496 00:29:25,760 --> 00:29:28,080 Speaker 1: one of the other operating systems rise up, or even 497 00:29:28,080 --> 00:29:30,160 Speaker 1: a new one take takes center stage. I mean, no 498 00:29:30,200 --> 00:29:33,560 Speaker 1: one thought that palm would go anywhere when it oh 499 00:29:33,840 --> 00:29:37,400 Speaker 1: wait yeah, um yeah, and and that that's that's a 500 00:29:37,440 --> 00:29:40,760 Speaker 1: good point too. I mean that, uhh, this is this 501 00:29:40,800 --> 00:29:43,640 Speaker 1: is one of those things that I think will will 502 00:29:43,680 --> 00:29:48,440 Speaker 1: play itself out in in the standards simply because, uh, 503 00:29:48,480 --> 00:29:52,400 Speaker 1: it will be more universal and give people an easier 504 00:29:53,160 --> 00:29:57,760 Speaker 1: and more enjoyable experience once assuming that it does get adopted. Yeah, 505 00:29:58,040 --> 00:30:00,320 Speaker 1: it looks like from most what I've seen most recently 506 00:30:00,480 --> 00:30:04,680 Speaker 1: we're talking about as far as an actual standard is adopted, 507 00:30:04,720 --> 00:30:07,320 Speaker 1: at least that's the proposed date at this point, so 508 00:30:07,400 --> 00:30:09,600 Speaker 1: it's it's still a couple of years off. Yeah. And 509 00:30:09,640 --> 00:30:11,320 Speaker 1: the nice thing is that when you think about one 510 00:30:11,320 --> 00:30:13,200 Speaker 1: of the nice things about this is is when you 511 00:30:13,240 --> 00:30:16,200 Speaker 1: get to a point where HTML five becomes the basis 512 00:30:16,280 --> 00:30:21,240 Speaker 1: for most apps, or at least a good selection of them. Uh, 513 00:30:21,320 --> 00:30:23,480 Speaker 1: the nice thing about that is you can sit there 514 00:30:23,520 --> 00:30:27,080 Speaker 1: and get to a point where you know that the 515 00:30:27,120 --> 00:30:30,280 Speaker 1: app version of a particular thing, or the app on 516 00:30:30,400 --> 00:30:33,320 Speaker 1: your smartphone is going to work more or less the 517 00:30:33,400 --> 00:30:35,640 Speaker 1: same way as the app on someone else's smartphone, even 518 00:30:35,640 --> 00:30:38,120 Speaker 1: if they have two different operating systems, which is kind 519 00:30:38,160 --> 00:30:40,880 Speaker 1: of nice because right now that is not the case. 520 00:30:41,520 --> 00:30:44,360 Speaker 1: There are so many apps out there that have dramatically 521 00:30:44,400 --> 00:30:47,640 Speaker 1: different sets of features from one operating system to another, 522 00:30:47,760 --> 00:30:50,840 Speaker 1: because one of them may support something natively and one 523 00:30:50,880 --> 00:30:56,200 Speaker 1: may not, or because maybe one company has a huge 524 00:30:56,200 --> 00:30:59,280 Speaker 1: amount of horsepower on their mobile device but only allows 525 00:30:59,320 --> 00:31:02,000 Speaker 1: their own apps to have access to that power, and 526 00:31:02,040 --> 00:31:05,200 Speaker 1: no one else's apps can access that power. I'm not 527 00:31:05,400 --> 00:31:09,400 Speaker 1: naming names, Okay, I just don't own one of those, 528 00:31:09,800 --> 00:31:15,200 Speaker 1: um anyway, I'm kidding. I actually do own one desk 529 00:31:15,320 --> 00:31:19,400 Speaker 1: right now. All right, So we're going to wrap this up. 530 00:31:19,520 --> 00:31:21,920 Speaker 1: This was, you know, really again we're looking at this 531 00:31:21,960 --> 00:31:27,520 Speaker 1: whole Facebook HTML five mistake. I think even Zuckerberg would say, yeah, 532 00:31:27,600 --> 00:31:29,760 Speaker 1: it was just too early to make that move. It 533 00:31:29,800 --> 00:31:32,400 Speaker 1: wasn't necessarily that it's the wrong move in the long run. 534 00:31:33,040 --> 00:31:36,520 Speaker 1: It's definitely the wrong move when they made it, so, 535 00:31:38,120 --> 00:31:40,880 Speaker 1: I don't know, yeah, biggest mistake, that's arguable. There have 536 00:31:40,920 --> 00:31:42,840 Speaker 1: been people who said, what about launching that I p 537 00:31:42,960 --> 00:31:45,920 Speaker 1: oh so quickly. Of course they were really pressured to 538 00:31:45,960 --> 00:31:47,480 Speaker 1: do that. There wasn't a whole lot of choice in 539 00:31:47,520 --> 00:31:51,120 Speaker 1: that either. But although they could have anyway, that's a 540 00:31:51,160 --> 00:31:53,520 Speaker 1: totally different podcast which I think I think we've actually 541 00:31:53,560 --> 00:31:56,520 Speaker 1: recorded it. So um. You guys, if you have any 542 00:31:56,560 --> 00:31:59,880 Speaker 1: suggestions for upcoming episodes of tech Stuff, something that you 543 00:32:00,160 --> 00:32:03,280 Speaker 1: want to know way more about, you should definitely drop 544 00:32:03,320 --> 00:32:05,280 Speaker 1: us a line let us know. We'll be happy to 545 00:32:05,360 --> 00:32:07,719 Speaker 1: talk about it in a future episode. You can get 546 00:32:07,760 --> 00:32:10,320 Speaker 1: in touch with us over email our addresses tech stuff 547 00:32:10,360 --> 00:32:13,560 Speaker 1: at Discovery dot com, or let us know on Facebook 548 00:32:13,640 --> 00:32:16,040 Speaker 1: or Twitter or handle at both of those locations as 549 00:32:16,160 --> 00:32:18,440 Speaker 1: tech Stuff, H. S W and Tris and I will 550 00:32:18,480 --> 00:32:22,280 Speaker 1: talk to you again really soon for more on this 551 00:32:22,440 --> 00:32:24,960 Speaker 1: and thousands of other topics because it has staff works 552 00:32:24,960 --> 00:32:29,400 Speaker 1: dot com