WEBVTT - TechStuff Looks at HTML5

0:00:02.520 --> 0:00:05.760
<v Speaker 1>Get in touch with technology with tech Stuff from hof

0:00:06.120 --> 0:00:14.240
<v Speaker 1>dot com. Hello again, everyone, and welcome to tech Stuff.

0:00:14.280 --> 0:00:15.920
<v Speaker 1>My name is Chris Poulette and I'm an editor at

0:00:15.920 --> 0:00:18.040
<v Speaker 1>how Stuff Works dot com. Sitting here across from me

0:00:18.200 --> 0:00:24.959
<v Speaker 1>as usual as senior writer Jonathan Strick. I crave baked goods. Uh. Yeah,

0:00:25.000 --> 0:00:28.360
<v Speaker 1>you know, we don't really have a lot of outtakes

0:00:28.440 --> 0:00:31.480
<v Speaker 1>on this ship. I managed to say every bun last

0:00:31.520 --> 0:00:35.760
<v Speaker 1>time and another and then I referenced it and you

0:00:35.840 --> 0:00:39.120
<v Speaker 1>got it. Anyway, Thanks, You're welcome. So anyhow, we'll talk

0:00:39.120 --> 0:00:42.239
<v Speaker 1>a little bit about HTML five. Why don't we? Why not?

0:00:42.880 --> 0:00:45.680
<v Speaker 1>All right then, So, first of all, I would like

0:00:45.720 --> 0:00:48.519
<v Speaker 1>to tell everyone out there in the listening audience we

0:00:48.600 --> 0:00:52.239
<v Speaker 1>are currently recording this episode in the afternoon, in the

0:00:52.240 --> 0:00:54.640
<v Speaker 1>middle of the week. Now, the reason why that's interesting

0:00:54.680 --> 0:00:57.720
<v Speaker 1>to us is that we normally record on Friday mornings

0:00:58.080 --> 0:01:00.280
<v Speaker 1>at the end of a long week, but this is

0:01:00.320 --> 0:01:06.640
<v Speaker 1>a Tuesday afternoon and I'm feeling a little zany. So okay,

0:01:06.640 --> 0:01:10.480
<v Speaker 1>but HTML five, So HTML five, before we even get

0:01:10.520 --> 0:01:12.959
<v Speaker 1>into that, we need to talk about what hypertext markup

0:01:13.040 --> 0:01:17.400
<v Speaker 1>language is. Yes, Now, this is the stuff that essentially,

0:01:17.400 --> 0:01:20.600
<v Speaker 1>this language is what helps a web web developer design

0:01:20.640 --> 0:01:23.800
<v Speaker 1>a web page so that it appears a certain way

0:01:23.840 --> 0:01:26.520
<v Speaker 1>when you access it with a web browser. It's a

0:01:26.640 --> 0:01:30.800
<v Speaker 1>very basis of making stuff appear on a web page

0:01:31.080 --> 0:01:33.480
<v Speaker 1>the right way. And so this dates all the way

0:01:33.480 --> 0:01:37.360
<v Speaker 1>back to the early nineties. Do you remember the early nineties? Yes, yeah,

0:01:37.640 --> 0:01:40.440
<v Speaker 1>what a magical time that was. Huh No, no, you're right,

0:01:40.520 --> 0:01:43.800
<v Speaker 1>let's move on. So but but in general, this is

0:01:43.840 --> 0:01:45.959
<v Speaker 1>the stuff that has the tags in it that tell

0:01:46.640 --> 0:01:49.360
<v Speaker 1>you know, the tag is essentially a message to the

0:01:49.400 --> 0:01:53.040
<v Speaker 1>web browser saying, when you see this tag, you need

0:01:53.080 --> 0:01:57.800
<v Speaker 1>to take this action, uh and make whatever comes after

0:01:57.920 --> 0:02:01.760
<v Speaker 1>that appear a certain way on website. Or it may

0:02:01.840 --> 0:02:03.640
<v Speaker 1>just be to help lay it out a certain way.

0:02:04.280 --> 0:02:07.520
<v Speaker 1>And so, uh, there were a lot of tags that

0:02:07.560 --> 0:02:11.800
<v Speaker 1>were developed for HTML, and eventually, uh, it got to

0:02:11.840 --> 0:02:14.720
<v Speaker 1>the point where there needed to be a new implementation

0:02:14.800 --> 0:02:19.040
<v Speaker 1>of HTML because it was starting to get a little clunky, right,

0:02:19.120 --> 0:02:21.640
<v Speaker 1>you know, they had a lot of tags there and

0:02:21.720 --> 0:02:25.359
<v Speaker 1>it was not elegant and confusing for someone who was

0:02:25.440 --> 0:02:27.120
<v Speaker 1>just trying to start up a website. So there were

0:02:28.120 --> 0:02:32.360
<v Speaker 1>attempts to make that more streamlined. Yeah, just just for clarification,

0:02:32.360 --> 0:02:36.120
<v Speaker 1>when we're talking about tags, basically, uh, an HTML document

0:02:36.240 --> 0:02:40.959
<v Speaker 1>document is simply a text document um. So it's it's

0:02:41.000 --> 0:02:45.200
<v Speaker 1>basically your your your letters, your numbers, uh, all those

0:02:45.280 --> 0:02:50.320
<v Speaker 1>kinds of standard text characters with no formatting whatsoever. In fact,

0:02:50.440 --> 0:02:52.800
<v Speaker 1>you're the ones supplying the formatting. If you want something

0:02:52.919 --> 0:02:56.959
<v Speaker 1>in in bold in the current version of HTML, you

0:02:56.960 --> 0:02:59.480
<v Speaker 1>would type I want this text in bold, and before

0:02:59.520 --> 0:03:02.760
<v Speaker 1>that you would type of tag called strong, which is

0:03:02.800 --> 0:03:05.560
<v Speaker 1>put in between in between brackets, and at the end

0:03:05.600 --> 0:03:08.160
<v Speaker 1>of the text that you want bold, you would put

0:03:08.200 --> 0:03:09.880
<v Speaker 1>what they call a clothes tag, which is a slight

0:03:10.120 --> 0:03:12.960
<v Speaker 1>variant on that, basically to say, I want the following

0:03:13.000 --> 0:03:15.560
<v Speaker 1>in bold. I wanted to stop here, and it goes

0:03:15.600 --> 0:03:17.960
<v Speaker 1>in for that. It could be italic, it could be underlined,

0:03:18.000 --> 0:03:20.120
<v Speaker 1>it could be struck through or you That's how you

0:03:20.160 --> 0:03:22.440
<v Speaker 1>put in hyperlinks, that's how you put in images. Is

0:03:22.480 --> 0:03:26.160
<v Speaker 1>alway these little tags and it's all in uh more

0:03:26.240 --> 0:03:28.040
<v Speaker 1>or less plain English. You're not doing a lot of

0:03:28.040 --> 0:03:32.680
<v Speaker 1>calculation like you would in any a typical programming language,

0:03:32.680 --> 0:03:35.480
<v Speaker 1>like for example, see where you're actually putting in variables

0:03:35.480 --> 0:03:38.280
<v Speaker 1>and all that stuff. That's why HTML is is popular

0:03:39.000 --> 0:03:41.520
<v Speaker 1>for people who are sort of dabbling in the idea

0:03:41.680 --> 0:03:44.240
<v Speaker 1>of programming because it sort of gives you an idea

0:03:44.240 --> 0:03:46.400
<v Speaker 1>of what coding is like without a whole lot of

0:03:46.920 --> 0:03:50.400
<v Speaker 1>coding UM and you and it's very simple to do.

0:03:50.480 --> 0:03:55.280
<v Speaker 1>It's based on a standard page definition UM, which is

0:03:55.640 --> 0:03:59.960
<v Speaker 1>maintained by the UH the W three C, the World

0:04:00.000 --> 0:04:03.360
<v Speaker 1>Old Wide Web Consortium. Yeah, I love that word. Yep,

0:04:03.520 --> 0:04:06.920
<v Speaker 1>Web's great word. UM an consortium is also awesome. Oh

0:04:07.000 --> 0:04:09.520
<v Speaker 1>yeah that too. So yeah, if you were to go

0:04:09.600 --> 0:04:11.560
<v Speaker 1>and view a web page, if you were to view

0:04:11.600 --> 0:04:14.400
<v Speaker 1>the source of that web page, uh, the you can

0:04:14.440 --> 0:04:17.240
<v Speaker 1>look at the source code. It's essentially it's really just

0:04:17.360 --> 0:04:20.159
<v Speaker 1>a series of directions like what we said, that tell

0:04:20.200 --> 0:04:23.960
<v Speaker 1>the browser what how to lay that page out. And

0:04:24.040 --> 0:04:27.640
<v Speaker 1>so it's not software. HTML is not a programming language.

0:04:27.800 --> 0:04:30.760
<v Speaker 1>It's a markup language. And what happens is that the

0:04:30.839 --> 0:04:35.240
<v Speaker 1>companies that make the web browsers have to incorporate the

0:04:35.360 --> 0:04:39.760
<v Speaker 1>whatever the standard version of HTML happens to be into

0:04:39.760 --> 0:04:42.640
<v Speaker 1>the web browser so that when you access a website,

0:04:43.000 --> 0:04:47.800
<v Speaker 1>it uh it it displays that website the right way

0:04:48.000 --> 0:04:52.599
<v Speaker 1>asterisk asterisk and the asterisk there is that they don't

0:04:52.880 --> 0:04:55.719
<v Speaker 1>have to nobody's telling them. They have to abide by

0:04:55.800 --> 0:04:58.360
<v Speaker 1>all the laws, which has been a point of much

0:04:58.400 --> 0:05:02.120
<v Speaker 1>contention in the past, because UM, there will be a

0:05:02.200 --> 0:05:05.560
<v Speaker 1>standard release. There was HTML two and three, and now,

0:05:05.680 --> 0:05:08.719
<v Speaker 1>as of the time we're recording this in September two

0:05:08.720 --> 0:05:12.680
<v Speaker 1>thousand twelve, the official recognized version of HTML is HTML four.

0:05:13.680 --> 0:05:16.760
<v Speaker 1>UM it's it's been updated a couple of times, and

0:05:17.000 --> 0:05:19.480
<v Speaker 1>people thought that HTML wasn't going to be updated at

0:05:19.480 --> 0:05:23.120
<v Speaker 1>all anymore, that it was essentially dead. But leave that

0:05:23.160 --> 0:05:28.919
<v Speaker 1>for a minute. UM. The thing is UM these these specifications.

0:05:29.080 --> 0:05:34.360
<v Speaker 1>The browser manufacturers Google for Chrome, UH, Apple for Safari

0:05:34.400 --> 0:05:38.000
<v Speaker 1>Opera which is a Norwegian company, Microsoft for i E

0:05:38.800 --> 0:05:42.520
<v Speaker 1>UM Internet Explorer, and and and others. There are many others. UM.

0:05:42.560 --> 0:05:45.320
<v Speaker 1>They basically have to adopt the guts of this thing.

0:05:45.480 --> 0:05:47.280
<v Speaker 1>So if you wanted your text to be bold, you

0:05:47.320 --> 0:05:49.800
<v Speaker 1>can use the old B or you can use the

0:05:49.800 --> 0:05:52.960
<v Speaker 1>newer strong and they're they're all going to recognize that.

0:05:53.120 --> 0:05:56.680
<v Speaker 1>But they're they're usually backwards compatible, so that because if

0:05:56.720 --> 0:05:59.760
<v Speaker 1>they weren't backwards compatible, any web page that had been

0:05:59.800 --> 0:06:03.760
<v Speaker 1>does mine with the old tags would be unrecognizable and

0:06:03.760 --> 0:06:06.719
<v Speaker 1>would not display properly on your screen. So if you

0:06:06.960 --> 0:06:08.760
<v Speaker 1>need to get your MIDI file fixed, you can still

0:06:08.800 --> 0:06:12.520
<v Speaker 1>go back to a page from and observe that. Um.

0:06:13.040 --> 0:06:15.640
<v Speaker 1>But that was the thing for a while, was oh well,

0:06:16.200 --> 0:06:19.200
<v Speaker 1>filling the name of the company here isn't completely compliant

0:06:19.200 --> 0:06:22.680
<v Speaker 1>with the newest standard of HTML. And um, you know,

0:06:22.720 --> 0:06:25.719
<v Speaker 1>Microsoft went on their own for a while, and um

0:06:26.080 --> 0:06:28.760
<v Speaker 1>that was it wasn't the kind of thing that the

0:06:28.800 --> 0:06:31.760
<v Speaker 1>average person would notice. It was more of a tech

0:06:32.080 --> 0:06:34.520
<v Speaker 1>head thing where they were going, well, you know so

0:06:34.680 --> 0:06:39.040
<v Speaker 1>and so it was more compatible. Yeah, so the HTML

0:06:39.520 --> 0:06:44.640
<v Speaker 1>four and also x htmlor UM, which is another type

0:06:44.640 --> 0:06:52.039
<v Speaker 1>of market language, these languages. Well, HTML four anyway, that

0:06:52.160 --> 0:06:56.560
<v Speaker 1>was the latest version, the one that everyone is considered

0:06:56.600 --> 0:07:01.640
<v Speaker 1>the standard. The current standard was released in a late nineties. Yes,

0:07:01.880 --> 0:07:06.480
<v Speaker 1>so you've got this uh, this markup language that's over

0:07:06.560 --> 0:07:09.040
<v Speaker 1>a decade old. And here's the problem. The problem is

0:07:09.080 --> 0:07:12.440
<v Speaker 1>that the markup language as it was designed back then

0:07:13.000 --> 0:07:18.040
<v Speaker 1>could not support some of the more rich Internet UH

0:07:18.160 --> 0:07:21.600
<v Speaker 1>features that we've come to know and love over the years,

0:07:22.280 --> 0:07:25.480
<v Speaker 1>things like video and audio. Stuff that is a more

0:07:25.560 --> 0:07:29.360
<v Speaker 1>of a rich experience was not supported in HTML four. Yeah.

0:07:29.400 --> 0:07:31.320
<v Speaker 1>As a matter of fact, if you go to UH

0:07:31.520 --> 0:07:34.960
<v Speaker 1>many popular sites, um, you're going to and view the

0:07:35.000 --> 0:07:38.240
<v Speaker 1>source as Jonathan suggested a moment ago. You're gonna see HTML,

0:07:38.320 --> 0:07:41.240
<v Speaker 1>but you're also likely to see other stuff in there too,

0:07:41.280 --> 0:07:43.480
<v Speaker 1>And you're gonna say, but, Jonathan and Chris, you told

0:07:43.520 --> 0:07:45.760
<v Speaker 1>me that i'd pretty much be able to read the

0:07:45.840 --> 0:07:48.360
<v Speaker 1>text file in the back end. What's all this other

0:07:48.440 --> 0:07:53.000
<v Speaker 1>programming stuff? Well, it could be JavaScript, which popular, which

0:07:53.080 --> 0:07:57.080
<v Speaker 1>is UH a language, a very mild programming language that

0:07:57.120 --> 0:08:00.080
<v Speaker 1>you can use to add some interactivity to websites. And

0:08:00.080 --> 0:08:03.160
<v Speaker 1>you're also likely to see UH an embed code for

0:08:03.400 --> 0:08:08.480
<v Speaker 1>FLASH on a lot of interactive media sites. UM and

0:08:09.160 --> 0:08:12.400
<v Speaker 1>probably just about everybody listening to this US is UH

0:08:12.440 --> 0:08:14.840
<v Speaker 1>familiar with flash. But it was a technology developed by

0:08:14.920 --> 0:08:20.200
<v Speaker 1>the UH design software company Macromedia before it merged with Adobe,

0:08:21.000 --> 0:08:26.160
<v Speaker 1>UH slash acquired by Adobe, and UM. Basically, UH flash

0:08:26.160 --> 0:08:31.720
<v Speaker 1>has been the standard for many years for designing rich

0:08:32.240 --> 0:08:36.800
<v Speaker 1>Internet content, animations, embedding video and things not not YouTube

0:08:36.880 --> 0:08:40.240
<v Speaker 1>videos or things like that or vino. But you know,

0:08:40.440 --> 0:08:43.680
<v Speaker 1>special people would produce these things in house and put

0:08:43.720 --> 0:08:46.400
<v Speaker 1>them on their websites, or they would contract a designer

0:08:46.440 --> 0:08:49.280
<v Speaker 1>to put this kind of interactive content on there. A

0:08:49.280 --> 0:08:51.120
<v Speaker 1>lot of shopping sites like to use it so you

0:08:51.120 --> 0:08:54.560
<v Speaker 1>can customize your room or things the UM and and

0:08:54.600 --> 0:08:59.680
<v Speaker 1>so HTML itself doesn't have any way to do that

0:09:00.040 --> 0:09:02.719
<v Speaker 1>kind of content. Now, you can link to something, you

0:09:02.760 --> 0:09:06.800
<v Speaker 1>can embed an image, UM or or files on the site,

0:09:06.800 --> 0:09:08.600
<v Speaker 1>but you might if you click on that file, it

0:09:08.720 --> 0:09:13.400
<v Speaker 1>might just load in another UM another kind of application,

0:09:13.480 --> 0:09:16.400
<v Speaker 1>for example UM. So it really didn't support it the

0:09:16.440 --> 0:09:19.480
<v Speaker 1>way that it could be done if you used flash

0:09:19.760 --> 0:09:21.640
<v Speaker 1>for example. Right, So instead what you would have to

0:09:21.640 --> 0:09:24.920
<v Speaker 1>do is install these plug ins into your browser. So

0:09:24.960 --> 0:09:28.800
<v Speaker 1>these are plug ins or extensions that would make your

0:09:29.080 --> 0:09:33.400
<v Speaker 1>browser capable of seeing this kind of information, because again,

0:09:33.440 --> 0:09:36.160
<v Speaker 1>on their own, they might not necessarily be able to

0:09:36.160 --> 0:09:38.559
<v Speaker 1>do that. So if you've ever gone to a website

0:09:38.559 --> 0:09:40.960
<v Speaker 1>and it's prompted you to install a plug in, first

0:09:40.960 --> 0:09:44.520
<v Speaker 1>of all, be careful, yes, because that's a very common

0:09:44.559 --> 0:09:48.720
<v Speaker 1>technique of installing malware onto your computer. If it's if

0:09:48.720 --> 0:09:52.160
<v Speaker 1>it's a site that you trust, and you feel reasonably

0:09:52.200 --> 0:09:55.720
<v Speaker 1>sure that there's not any uh hanky nor panky going

0:09:55.800 --> 0:09:59.240
<v Speaker 1>on at that particular moment, then that might be what

0:09:59.360 --> 0:10:01.360
<v Speaker 1>you need. You might to install a plug in order

0:10:01.360 --> 0:10:03.560
<v Speaker 1>to view whatever that content is or interact with that

0:10:03.679 --> 0:10:07.360
<v Speaker 1>site in some way. So that was one of the

0:10:07.400 --> 0:10:11.440
<v Speaker 1>reasons why, uh, there there needed to be this update

0:10:11.480 --> 0:10:15.320
<v Speaker 1>to HTML was to design a markup language that was

0:10:16.440 --> 0:10:18.920
<v Speaker 1>backwards compatible so that you could still see those old sites,

0:10:18.960 --> 0:10:23.480
<v Speaker 1>but also more streamlined again, so that someone who's building

0:10:23.520 --> 0:10:27.280
<v Speaker 1>something from the ground up starting with HTML five would

0:10:27.280 --> 0:10:30.400
<v Speaker 1>be able to do so without it being too confusing.

0:10:30.480 --> 0:10:32.880
<v Speaker 1>They didn't want the barrier to be too high, and

0:10:32.920 --> 0:10:36.320
<v Speaker 1>also they wanted to be able to natively support these

0:10:36.440 --> 0:10:41.440
<v Speaker 1>rich Internet interactions without the requirement of some sort of

0:10:41.600 --> 0:10:45.680
<v Speaker 1>additional plug in. So this is what kind of prompted

0:10:46.280 --> 0:10:50.680
<v Speaker 1>companies like Apple in particular to push for HTML five

0:10:50.800 --> 0:10:55.960
<v Speaker 1>because the uh, the alternative is to support all these plugins,

0:10:56.120 --> 0:11:00.320
<v Speaker 1>and if there were just one type of plug for

0:11:00.400 --> 0:11:05.680
<v Speaker 1>each type of rich media kind of experience, maybe that

0:11:05.679 --> 0:11:07.880
<v Speaker 1>wouldn't be such a big deal. You know. It would

0:11:07.880 --> 0:11:10.520
<v Speaker 1>mean that perhaps the browser would be clunkier than it

0:11:10.559 --> 0:11:13.160
<v Speaker 1>needed to be, but you would have that one solution.

0:11:13.200 --> 0:11:16.320
<v Speaker 1>But the fact is, there's not just one solution. For

0:11:16.360 --> 0:11:19.319
<v Speaker 1>a while, there were there were a few different competing

0:11:19.400 --> 0:11:21.880
<v Speaker 1>technologies that we're all doing the same sort of thing.

0:11:22.400 --> 0:11:24.080
<v Speaker 1>But it would mean that, you know, you could be

0:11:24.080 --> 0:11:27.160
<v Speaker 1>watching video on one site and everything's fine, and then

0:11:27.200 --> 0:11:28.839
<v Speaker 1>you would go to a different site and suddenly it

0:11:28.840 --> 0:11:31.439
<v Speaker 1>would prompt you to get a different kind of plug

0:11:31.440 --> 0:11:34.080
<v Speaker 1>in because the plug and you were using does not

0:11:34.200 --> 0:11:36.880
<v Speaker 1>work with that particular video. So the two in particular,

0:11:36.920 --> 0:11:39.319
<v Speaker 1>I'm thinking of our flash and silver Light. Yes, a

0:11:39.360 --> 0:11:42.920
<v Speaker 1>silver light came from Microsoft, and uh, anyone who was

0:11:42.920 --> 0:11:46.480
<v Speaker 1>watching um I remember in the two thousand I think

0:11:46.480 --> 0:11:49.520
<v Speaker 1>it was a two thousand eight Olympics where if you

0:11:49.559 --> 0:11:51.959
<v Speaker 1>wanted to watch the stuff online you had to use

0:11:52.000 --> 0:11:55.040
<v Speaker 1>silver light, at least in the United States, And so

0:11:55.320 --> 0:11:58.320
<v Speaker 1>U that meant that I installed silver Light on my

0:11:58.360 --> 0:12:00.640
<v Speaker 1>computer because I wanted to watch some of the stuff.

0:12:01.080 --> 0:12:04.040
<v Speaker 1>And and you know, it's it's just not an ideal

0:12:04.080 --> 0:12:06.520
<v Speaker 1>solution in the sense that you know, you've got a

0:12:06.520 --> 0:12:09.800
<v Speaker 1>browser that's getting heavier and heavier as far as code

0:12:09.840 --> 0:12:12.040
<v Speaker 1>is going, because you're plugging in all this stuff. It

0:12:12.040 --> 0:12:14.480
<v Speaker 1>would be nicer if it were all built in from

0:12:14.520 --> 0:12:16.920
<v Speaker 1>the ground up and you didn't have to worry about that.

0:12:17.520 --> 0:12:19.520
<v Speaker 1>So that was one of the reasons for HTMO five.

0:12:19.600 --> 0:12:24.559
<v Speaker 1>Another was that we're slowly getting closer to this idea

0:12:24.559 --> 0:12:29.760
<v Speaker 1>of the semantic web, where the web is quote unquote

0:12:29.760 --> 0:12:32.440
<v Speaker 1>getting smarter. And what I mean by that is that

0:12:32.559 --> 0:12:36.600
<v Speaker 1>it's easier for you to access the information you are

0:12:36.640 --> 0:12:41.840
<v Speaker 1>particularly interested in. So if I'm doing a search for

0:12:42.760 --> 0:12:47.080
<v Speaker 1>a very specific type of information with the semantic Web,

0:12:47.440 --> 0:12:51.800
<v Speaker 1>I would ideally get precisely what I needed from that,

0:12:51.880 --> 0:12:54.440
<v Speaker 1>and not just a bunch of links to things that

0:12:54.600 --> 0:12:57.160
<v Speaker 1>may or may not have the answer to my question.

0:12:57.920 --> 0:13:02.400
<v Speaker 1>Uh So, h g mL five has organizational tags in it,

0:13:02.800 --> 0:13:07.000
<v Speaker 1>things like section or article or side or header that

0:13:07.120 --> 0:13:09.719
<v Speaker 1>can help when you're doing a search. It can help

0:13:09.760 --> 0:13:15.400
<v Speaker 1>identify things that are more important within the confines of

0:13:15.440 --> 0:13:17.719
<v Speaker 1>that web page than others. So that way, let's say

0:13:17.720 --> 0:13:20.280
<v Speaker 1>that you're a web page developer and you've used these

0:13:20.280 --> 0:13:23.960
<v Speaker 1>tags to kind of organize your web page. You've got

0:13:23.960 --> 0:13:27.200
<v Speaker 1>an entire section that's about the search terms that I'm

0:13:27.200 --> 0:13:30.040
<v Speaker 1>looking for. It's more likely that that's going to come

0:13:30.120 --> 0:13:32.360
<v Speaker 1>up for me when I'm using some sort of search tool,

0:13:32.880 --> 0:13:35.360
<v Speaker 1>because you have laid it out in such a way

0:13:35.400 --> 0:13:38.720
<v Speaker 1>that the search engine knows, hey, this is a section

0:13:38.800 --> 0:13:43.079
<v Speaker 1>that directly pertains to the search terms that were entered. Um,

0:13:43.200 --> 0:13:46.880
<v Speaker 1>so those were that's also another consideration. So HTML five

0:13:47.840 --> 0:13:51.120
<v Speaker 1>has really had a big push, particularly from companies like Apple,

0:13:51.240 --> 0:13:55.760
<v Speaker 1>over the last well several years, actually UH, and that

0:13:56.160 --> 0:13:58.400
<v Speaker 1>has been the battle cry for a lot of these

0:13:58.440 --> 0:14:02.520
<v Speaker 1>companies that HTML five is the future. You should stop

0:14:02.559 --> 0:14:06.400
<v Speaker 1>developing for things like flash and other plug ins because

0:14:06.520 --> 0:14:09.600
<v Speaker 1>that's just holding us back. Instead, put your energy toward

0:14:09.760 --> 0:14:13.360
<v Speaker 1>getting the HTML five to a complete standard, because as

0:14:13.360 --> 0:14:17.720
<v Speaker 1>it stands now, it's still being developed. Yeah, the UH

0:14:17.880 --> 0:14:22.040
<v Speaker 1>HTML five, for all of its uh prominence in the

0:14:22.080 --> 0:14:24.960
<v Speaker 1>tech news in the last couple of years, UM, you

0:14:24.960 --> 0:14:28.520
<v Speaker 1>you would think that it was fairly new. But an

0:14:28.600 --> 0:14:32.560
<v Speaker 1>organization called what would well Okay, that's my best guess

0:14:32.560 --> 0:14:35.000
<v Speaker 1>on how to pronounce it, w h A t w G.

0:14:35.200 --> 0:14:39.480
<v Speaker 1>That's the Web Hypertext Application Technology Working Group. Basically, it's

0:14:39.520 --> 0:14:45.840
<v Speaker 1>a group of companies or organizations that decided to UH

0:14:45.880 --> 0:14:51.280
<v Speaker 1>put their efforts together and update HTML. The idea is, UH,

0:14:51.280 --> 0:14:54.000
<v Speaker 1>you know, or behind it was, hey, we don't you know,

0:14:54.360 --> 0:14:59.120
<v Speaker 1>HTML by itself can't do what we wanted to do,

0:14:59.160 --> 0:15:01.320
<v Speaker 1>what we want to be able to make available to

0:15:01.360 --> 0:15:04.200
<v Speaker 1>our customers. So let's see if we can come up

0:15:04.240 --> 0:15:08.240
<v Speaker 1>with a new standard. And back in two thousand four, UM,

0:15:08.440 --> 0:15:13.680
<v Speaker 1>Apple Mozilla, which is the organization behind the Firefox browser

0:15:14.240 --> 0:15:19.080
<v Speaker 1>and opera software UM got together and said, let's UH,

0:15:19.120 --> 0:15:21.800
<v Speaker 1>you know, we're we don't really like this extensible h

0:15:21.920 --> 0:15:25.000
<v Speaker 1>t m L x HTML that W three C is

0:15:25.000 --> 0:15:28.320
<v Speaker 1>working on. Let's see if we can come up with

0:15:28.360 --> 0:15:31.240
<v Speaker 1>something we like better and then we'll present it um

0:15:31.320 --> 0:15:35.400
<v Speaker 1>And so for a while, X HTML and HTML five

0:15:35.720 --> 0:15:39.200
<v Speaker 1>were competing standards, with x t X h t m

0:15:39.320 --> 0:15:41.520
<v Speaker 1>L in the lead. It looks like that was going

0:15:41.560 --> 0:15:43.320
<v Speaker 1>to be the successor to h t m L four.

0:15:45.080 --> 0:15:49.880
<v Speaker 1>I think what eventually forced HTML five into prominence was

0:15:50.600 --> 0:15:53.800
<v Speaker 1>the uh that this was on the pre post PC era.

0:15:54.520 --> 0:15:57.280
<v Speaker 1>But now now that we're talking about tablets, so the

0:15:57.360 --> 0:15:59.680
<v Speaker 1>pre post PC era, that might just be the PC

0:16:00.080 --> 0:16:05.920
<v Speaker 1>RU stop messing with my head. Uh No. I said

0:16:05.960 --> 0:16:09.160
<v Speaker 1>that on purpose to see if you're I was listening

0:16:09.240 --> 0:16:13.480
<v Speaker 1>or if I was just so uh so, yeah, I

0:16:13.480 --> 0:16:15.240
<v Speaker 1>mean this is this is one of those things where

0:16:15.240 --> 0:16:17.000
<v Speaker 1>they said, okay, let's see what what we can come

0:16:17.080 --> 0:16:20.960
<v Speaker 1>up with. And so HTML five again isn't it hasn't

0:16:20.960 --> 0:16:24.560
<v Speaker 1>been ratified, it hasn't been standardized, but uh, it was

0:16:24.600 --> 0:16:28.160
<v Speaker 1>forced into the media when the I think when the

0:16:28.200 --> 0:16:33.280
<v Speaker 1>iPad came out in two thousand ten, because basically Apple

0:16:34.000 --> 0:16:37.120
<v Speaker 1>bet on HTML five. Now it's one of the members,

0:16:37.320 --> 0:16:41.360
<v Speaker 1>one of the founding members of what would So you

0:16:41.360 --> 0:16:44.280
<v Speaker 1>would say, well, okay, sure they're promoting their own standard.

0:16:44.880 --> 0:16:50.000
<v Speaker 1>Um Apple's argument and leaving flash off the iPad and

0:16:50.080 --> 0:16:54.400
<v Speaker 1>the iPhone and the iPod Touch. Um It's basically, look,

0:16:54.840 --> 0:16:57.040
<v Speaker 1>flash can be a resource hog. It takes a lot

0:16:57.280 --> 0:16:59.840
<v Speaker 1>of processing power to run this. It's gonna slow you down.

0:17:00.400 --> 0:17:04.280
<v Speaker 1>You're on, on on using these gadgets, and we're just

0:17:04.359 --> 0:17:07.200
<v Speaker 1>not gonna put flash on this. Also, it was going

0:17:07.240 --> 0:17:10.680
<v Speaker 1>to drain your battery because it was such a it

0:17:10.800 --> 0:17:13.199
<v Speaker 1>was taking up so many resources, which in turn required

0:17:13.200 --> 0:17:17.000
<v Speaker 1>more power that you would end up having a mobile

0:17:17.000 --> 0:17:19.119
<v Speaker 1>device that would have a useful battery life of a

0:17:19.160 --> 0:17:23.040
<v Speaker 1>few hours, which you know is not acceptable if you're

0:17:23.160 --> 0:17:26.120
<v Speaker 1>looking for something like a mobile phone. I mean, most

0:17:26.160 --> 0:17:28.800
<v Speaker 1>of us don't plug our phones in every couple of

0:17:28.800 --> 0:17:32.000
<v Speaker 1>hours to recharge, and if we had to, I think

0:17:32.000 --> 0:17:36.120
<v Speaker 1>most of us would be dissatisfied with that experience. Yeah. Now,

0:17:36.160 --> 0:17:39.440
<v Speaker 1>of course, uh, the the iPhone and iPod Touch predate

0:17:39.480 --> 0:17:41.760
<v Speaker 1>the iPad, and it was apparent that flash was not

0:17:41.840 --> 0:17:44.560
<v Speaker 1>going on those anytime soon. But I think the iPad really,

0:17:45.080 --> 0:17:47.159
<v Speaker 1>the launch of the iPad really brought it into relief.

0:17:47.200 --> 0:17:49.160
<v Speaker 1>They said Hey, if you got a device this big,

0:17:49.160 --> 0:17:51.280
<v Speaker 1>if you can look at web pages on this thing,

0:17:51.280 --> 0:17:55.560
<v Speaker 1>it's intended for surfing in part, why wouldn't you include flash?

0:17:55.600 --> 0:17:58.199
<v Speaker 1>Come on, Steve, But he said, nope, I'm not going

0:17:58.280 --> 0:17:59.800
<v Speaker 1>to do it. Apple is not going to do it.

0:18:00.119 --> 0:18:03.359
<v Speaker 1>You're on your own. And some other big companies have really,

0:18:03.880 --> 0:18:08.160
<v Speaker 1>uh at least at least capitulated to that sort of view,

0:18:08.200 --> 0:18:11.880
<v Speaker 1>if not like wholeheartedly thrown in, some of them have

0:18:12.800 --> 0:18:16.959
<v Speaker 1>have have started to to acquiesce to to say, all right,

0:18:17.000 --> 0:18:19.800
<v Speaker 1>you know the writings on the wall, this this has

0:18:19.880 --> 0:18:22.679
<v Speaker 1>to change. And there's so much momentum going forward that

0:18:22.720 --> 0:18:26.000
<v Speaker 1>we're going to back HTML five even if we're not

0:18:26.040 --> 0:18:28.640
<v Speaker 1>going to champion it. Um, there there are a lot

0:18:28.680 --> 0:18:32.360
<v Speaker 1>of examples out there. I mean, heck, YouTube has has

0:18:32.440 --> 0:18:36.160
<v Speaker 1>an opt in service where you can view the videos

0:18:36.280 --> 0:18:40.000
<v Speaker 1>via HTML five as opposed to flash based players. So

0:18:40.960 --> 0:18:42.720
<v Speaker 1>that was a big That was a big thing. I mean,

0:18:42.760 --> 0:18:44.840
<v Speaker 1>you think about how many videos are up on YouTube.

0:18:44.960 --> 0:18:48.119
<v Speaker 1>That's a massive undertaking. Yeah, yeah, that was that. That

0:18:48.280 --> 0:18:52.000
<v Speaker 1>actually is a good point because, um, you couldn't go

0:18:52.160 --> 0:18:58.240
<v Speaker 1>to YouTube and view videos on the iPad when it

0:18:58.280 --> 0:19:01.359
<v Speaker 1>first came out, because it was flash based players. Yeah,

0:19:01.600 --> 0:19:04.159
<v Speaker 1>and uh that that's one of the reasons that they've

0:19:04.880 --> 0:19:08.040
<v Speaker 1>that Apple has had that YouTube app that it recently

0:19:08.160 --> 0:19:10.600
<v Speaker 1>did away with from iOS six. There was a native

0:19:10.640 --> 0:19:15.639
<v Speaker 1>app on iOS that would allow you to access certain

0:19:15.800 --> 0:19:19.920
<v Speaker 1>YouTube videos that that we're compatible with that app, So

0:19:20.000 --> 0:19:22.760
<v Speaker 1>that would that was sort of Apple's answer and Google's answer,

0:19:23.680 --> 0:19:26.720
<v Speaker 1>uh in the short term, while there was this initiative

0:19:26.760 --> 0:19:30.400
<v Speaker 1>to try and convert videos from flash based to HTML

0:19:30.480 --> 0:19:35.199
<v Speaker 1>five based videos. So um so yeah, I mean that

0:19:35.320 --> 0:19:37.600
<v Speaker 1>this is when people started going, well, or you know,

0:19:37.720 --> 0:19:40.520
<v Speaker 1>which side are you on? Are you on the HTML

0:19:40.640 --> 0:19:42.919
<v Speaker 1>five side or are you on the flash side? Come on?

0:19:43.000 --> 0:19:45.640
<v Speaker 1>Flashes is lovely. It does all the things we needed

0:19:45.680 --> 0:19:48.600
<v Speaker 1>to do. There are so many flash games. Um. Facebook

0:19:48.680 --> 0:19:51.000
<v Speaker 1>was one of those companies in particular that was sort

0:19:51.040 --> 0:19:55.560
<v Speaker 1>of um, I think, uh sort of a battleground if

0:19:55.600 --> 0:19:59.680
<v Speaker 1>you will, because so much traffic on Facebook uh involves

0:19:59.760 --> 0:20:04.080
<v Speaker 1>rich media content, especially the games and other applications that

0:20:04.080 --> 0:20:07.520
<v Speaker 1>that people run on there. So um and of course

0:20:07.760 --> 0:20:12.760
<v Speaker 1>Facebook having uh you know, a billion people more or less. Uh,

0:20:12.840 --> 0:20:15.639
<v Speaker 1>that's a whole lot of web traffic and and and

0:20:15.840 --> 0:20:19.560
<v Speaker 1>organizations like YouTube and Facebook are going to be the

0:20:19.840 --> 0:20:23.000
<v Speaker 1>places where they're sort of litmus tests for the rest

0:20:23.000 --> 0:20:25.719
<v Speaker 1>of the web. You know, do you have rich media content?

0:20:25.840 --> 0:20:30.080
<v Speaker 1>If so, how are you displaying it? So yeah, YouTube

0:20:30.320 --> 0:20:34.120
<v Speaker 1>chose to make its pages render in HTML five, So

0:20:34.440 --> 0:20:38.000
<v Speaker 1>pointing Facebook, going back to Facebook, Facebook, this is an

0:20:38.080 --> 0:20:43.600
<v Speaker 1>interesting and somewhat I don't know if controversial is the

0:20:43.720 --> 0:20:46.280
<v Speaker 1>right word for it, but there are people have there

0:20:46.280 --> 0:20:49.960
<v Speaker 1>have been arguments that have broken out online about what

0:20:50.160 --> 0:20:54.920
<v Speaker 1>Mark Zuckerberg said in September two twelve about face Facebook

0:20:54.920 --> 0:20:58.320
<v Speaker 1>and HTML five. He actually said, essentially, our biggest mistake

0:20:58.359 --> 0:21:01.639
<v Speaker 1>was betting too much on h GML five and this

0:21:02.000 --> 0:21:07.440
<v Speaker 1>I read this originally in tech crunch Um. But the

0:21:07.440 --> 0:21:10.960
<v Speaker 1>the problem was that they Facebook had a choice. They

0:21:10.960 --> 0:21:15.920
<v Speaker 1>could either develop apps for HTML five, thinking well, this

0:21:16.000 --> 0:21:19.800
<v Speaker 1>is the ideal situation, because if this is the standard,

0:21:20.240 --> 0:21:23.879
<v Speaker 1>then everyone is going to incorporate HTML five in their products,

0:21:24.280 --> 0:21:27.080
<v Speaker 1>which means we don't have to sit there and create

0:21:27.160 --> 0:21:30.840
<v Speaker 1>a native application for each operating system that's on a

0:21:30.880 --> 0:21:34.359
<v Speaker 1>mobile device. Is primarily for mobile here that we're talking about.

0:21:35.240 --> 0:21:39.480
<v Speaker 1>So they thought, all right, let's throw let's throw all

0:21:39.560 --> 0:21:42.040
<v Speaker 1>we have into HTML five and start developing for it.

0:21:42.040 --> 0:21:44.560
<v Speaker 1>But then they discovered a problem and the problem is

0:21:44.600 --> 0:21:49.000
<v Speaker 1>that ht mm L five is not fully baked and

0:21:49.119 --> 0:21:52.840
<v Speaker 1>the implementation of it in hardware is not fully baked,

0:21:52.960 --> 0:21:57.880
<v Speaker 1>so it's not They were discovering that the the experience

0:21:57.920 --> 0:22:01.600
<v Speaker 1>that users were having on HTML i've based apps on

0:22:01.680 --> 0:22:06.200
<v Speaker 1>these devices was not ideal. That things were slow, certain

0:22:06.240 --> 0:22:11.640
<v Speaker 1>features weren't weren't supported through HTML five UM, and it

0:22:11.720 --> 0:22:14.399
<v Speaker 1>just was it was not a great experience. And so

0:22:14.440 --> 0:22:17.800
<v Speaker 1>people were like, this app is terrible, and people were

0:22:17.840 --> 0:22:20.800
<v Speaker 1>reviewing apps saying, this app is awful because it takes

0:22:20.840 --> 0:22:24.240
<v Speaker 1>forever considering what I'm asking it to do. I can't

0:22:24.280 --> 0:22:26.879
<v Speaker 1>believe it takes so long for me to accomplish these goals.

0:22:27.359 --> 0:22:29.200
<v Speaker 1>And so that was one of the issues. And then

0:22:29.359 --> 0:22:33.080
<v Speaker 1>they said, well, if we had instead spent all that

0:22:33.240 --> 0:22:38.919
<v Speaker 1>time and energy and thought on designing native applications for

0:22:39.080 --> 0:22:44.200
<v Speaker 1>these devices, they could take advantage of each devices UH

0:22:44.320 --> 0:22:48.479
<v Speaker 1>hardware capabilities and UH and their operating systems in a

0:22:48.520 --> 0:22:51.480
<v Speaker 1>way that would be a much more satisfying experience for

0:22:51.520 --> 0:22:55.400
<v Speaker 1>the user. Even though that means that we are contributing

0:22:55.400 --> 0:23:00.320
<v Speaker 1>to this sort of fragmented approach to developing apps. And

0:23:01.400 --> 0:23:04.239
<v Speaker 1>you know, this was a big This caused a lot

0:23:04.320 --> 0:23:06.399
<v Speaker 1>of Uh, it was a bit of a kerfuffle that

0:23:06.480 --> 0:23:08.520
<v Speaker 1>fall fell out about this, and I think part of

0:23:08.560 --> 0:23:12.920
<v Speaker 1>the problem is that HTML five is a little too

0:23:13.640 --> 0:23:17.120
<v Speaker 1>It's it's not ready for prime time yet, and that

0:23:17.320 --> 0:23:22.160
<v Speaker 1>the hardware and the the hardware is not really there

0:23:22.160 --> 0:23:26.160
<v Speaker 1>to support it. The markup language is not mature enough yet,

0:23:26.720 --> 0:23:29.680
<v Speaker 1>the implementation of it is not mature enough yet, so

0:23:30.119 --> 0:23:34.840
<v Speaker 1>the experience is not, uh, not going to be great

0:23:35.080 --> 0:23:38.760
<v Speaker 1>across the board, particularly in the mobile world, and that

0:23:39.080 --> 0:23:42.840
<v Speaker 1>perhaps a couple of years down the line, HTML five

0:23:42.880 --> 0:23:46.439
<v Speaker 1>will be the obvious answer, right but right now it's not.

0:23:46.560 --> 0:23:48.600
<v Speaker 1>And the problem is Facebook jumped on it a little

0:23:48.600 --> 0:23:55.879
<v Speaker 1>too early. Yeah, and people, of course, uh initially when

0:23:55.960 --> 0:23:58.159
<v Speaker 1>that comment came out, I think it it caused the

0:23:58.280 --> 0:24:02.879
<v Speaker 1>sturb because it was pretty strongly worded. I've seen several

0:24:02.920 --> 0:24:05.240
<v Speaker 1>commentaries and said, well, you know, it's probably not their

0:24:05.480 --> 0:24:10.639
<v Speaker 1>biggest mistake ever. Um, but yeah, I mean it's so

0:24:10.880 --> 0:24:13.800
<v Speaker 1>it's so hard to tell at this point what is

0:24:13.920 --> 0:24:17.160
<v Speaker 1>and what isn't going to be in the final implementation

0:24:17.200 --> 0:24:21.280
<v Speaker 1>of HTML five. But development has been steady on it

0:24:21.320 --> 0:24:26.080
<v Speaker 1>since it's been announced and adopted by so many companies.

0:24:26.119 --> 0:24:29.800
<v Speaker 1>So um, yeah, I think betting the farm on it

0:24:29.960 --> 0:24:33.680
<v Speaker 1>or betting the farmville. I see what you did there,

0:24:34.480 --> 0:24:38.240
<v Speaker 1>Uh might might be a bit extreme. Uh yeah, there

0:24:38.280 --> 0:24:41.040
<v Speaker 1>there There have been some HTML five games and things

0:24:41.040 --> 0:24:43.800
<v Speaker 1>that I've seen pop up on Facebook. The majority of

0:24:43.800 --> 0:24:47.680
<v Speaker 1>them are still baked in flash. UM. But yeah, I

0:24:47.720 --> 0:24:52.760
<v Speaker 1>mean even even Adobe whose product flash is um has

0:24:52.800 --> 0:24:55.880
<v Speaker 1>been backing off to some degree. I mean even even

0:24:56.080 --> 0:25:00.400
<v Speaker 1>h Flash for Android has been discontinued officially UM. And and

0:25:00.160 --> 0:25:04.240
<v Speaker 1>and it appears that they have gone into the business

0:25:04.280 --> 0:25:08.800
<v Speaker 1>of building HTML five encoding tools, which uh, you know

0:25:08.880 --> 0:25:13.959
<v Speaker 1>would seem to be the smart move. So yeah. Uh.

0:25:14.119 --> 0:25:16.440
<v Speaker 1>The thing is that it also goes into the whole

0:25:16.600 --> 0:25:19.560
<v Speaker 1>is it the web or is it mobile app? See

0:25:19.560 --> 0:25:23.240
<v Speaker 1>that's a That's another interesting point is that when the

0:25:23.280 --> 0:25:26.240
<v Speaker 1>when the when HTML five, when they were starting to

0:25:26.280 --> 0:25:29.920
<v Speaker 1>develop it for HTML five, that was pre mobile, I mean,

0:25:29.960 --> 0:25:34.000
<v Speaker 1>before smartphones had really hit the consumer market, before tablets

0:25:34.000 --> 0:25:37.000
<v Speaker 1>had really hit the consumer market. You're talking about, you know,

0:25:37.040 --> 0:25:42.000
<v Speaker 1>the original When first looking into HTML five, you're almost

0:25:42.080 --> 0:25:45.119
<v Speaker 1>looking at two different branches of the web. Because there's

0:25:45.160 --> 0:25:48.280
<v Speaker 1>the computer experience, which you know, a lot of us

0:25:48.320 --> 0:25:50.800
<v Speaker 1>are familiar with because that's how we learned to use

0:25:50.840 --> 0:25:53.320
<v Speaker 1>the web that was that was the way the main

0:25:53.359 --> 0:25:56.720
<v Speaker 1>way to use the web, and now mobile is increasingly

0:25:56.800 --> 0:25:59.399
<v Speaker 1>taking that over and becoming the dominant way that a

0:25:59.440 --> 0:26:02.560
<v Speaker 1>lot of people are rely upon in order to access

0:26:02.560 --> 0:26:06.480
<v Speaker 1>the web. So it means that while while the considerations

0:26:06.520 --> 0:26:09.439
<v Speaker 1>you made for this markup language might have made perfect

0:26:09.440 --> 0:26:13.520
<v Speaker 1>sense for a desktop or laptop computer that has access

0:26:13.560 --> 0:26:17.280
<v Speaker 1>to greater resources than your typical mobile device does, now

0:26:17.320 --> 0:26:21.639
<v Speaker 1>you have to rethink all that again because you're talking about, uh,

0:26:22.160 --> 0:26:25.399
<v Speaker 1>you know, the mobile approach, and it's not necessarily the

0:26:25.400 --> 0:26:27.919
<v Speaker 1>people behind HTML five that have to do the rethinking.

0:26:28.600 --> 0:26:32.040
<v Speaker 1>It's the hardware developers and the operating system developers who

0:26:32.080 --> 0:26:35.760
<v Speaker 1>have to really consider how to implement this in a

0:26:35.800 --> 0:26:39.359
<v Speaker 1>way that fits in the mobile world. And remember the

0:26:39.400 --> 0:26:43.520
<v Speaker 1>mobile world, you've got several challenges battery life, like we

0:26:43.560 --> 0:26:47.359
<v Speaker 1>mentioned as a challenge limited resources because in general, you

0:26:47.400 --> 0:26:50.640
<v Speaker 1>tend to have lower powered chips because lower powered chips

0:26:50.640 --> 0:26:54.040
<v Speaker 1>are going to drain a battery more slowly, and they

0:26:54.119 --> 0:26:56.920
<v Speaker 1>generate less heat, which is important for a mobile device.

0:26:57.600 --> 0:27:00.239
<v Speaker 1>And you're going to have a different form factor. So

0:27:01.040 --> 0:27:04.400
<v Speaker 1>all of those things play into designing the operating system

0:27:04.520 --> 0:27:07.960
<v Speaker 1>and its capabilities and features. In a mobile platform as

0:27:08.000 --> 0:27:11.360
<v Speaker 1>well as you know, how do we implement this HTML five,

0:27:11.400 --> 0:27:13.080
<v Speaker 1>what's it going to look like in the mobile space,

0:27:13.080 --> 0:27:15.200
<v Speaker 1>how's it going to behave, how's it going to access

0:27:15.880 --> 0:27:19.080
<v Speaker 1>the resources we have when we try to render a

0:27:19.160 --> 0:27:24.320
<v Speaker 1>web page that is um that has been built through

0:27:24.480 --> 0:27:28.199
<v Speaker 1>HTML five. So it's it's you know, it's not a

0:27:28.400 --> 0:27:31.440
<v Speaker 1>simple answer, because it's not oh well, you just need

0:27:31.480 --> 0:27:34.560
<v Speaker 1>to change this one aspect of HTML five and everything

0:27:34.560 --> 0:27:37.800
<v Speaker 1>works perfectly. No, it's it's more of that relationship of

0:27:37.800 --> 0:27:41.199
<v Speaker 1>operating system to hardware where there's going to be a

0:27:41.240 --> 0:27:43.880
<v Speaker 1>bit of a bottleneck, at least in the short term.

0:27:43.920 --> 0:27:46.480
<v Speaker 1>It may very well be that in a year or

0:27:46.520 --> 0:27:49.919
<v Speaker 1>two years will have some breakthroughs where the because of

0:27:50.280 --> 0:27:53.879
<v Speaker 1>architecture or because of operating system design, that no longer

0:27:53.920 --> 0:27:57.639
<v Speaker 1>becomes a real issue. And HTML five is the obvious answer.

0:27:57.720 --> 0:28:01.080
<v Speaker 1>But for right now, that native app approach looks like

0:28:01.160 --> 0:28:05.520
<v Speaker 1>that makes more sense, at least for Facebook. Yeah. Yeah,

0:28:05.600 --> 0:28:08.320
<v Speaker 1>and uh, you know, as Matta say said, you know,

0:28:08.359 --> 0:28:11.800
<v Speaker 1>it's also in the implementation too. It's not just the

0:28:11.960 --> 0:28:13.440
<v Speaker 1>h t m L five, it's the way it was

0:28:13.560 --> 0:28:15.720
<v Speaker 1>rolled out. I'm sure once they've had an opportunity to

0:28:15.760 --> 0:28:21.040
<v Speaker 1>you to retreat and regather uh their resources that you

0:28:21.080 --> 0:28:22.960
<v Speaker 1>know that will be able to do that. But you know,

0:28:23.040 --> 0:28:26.640
<v Speaker 1>it does affect so many people that you know, building

0:28:27.760 --> 0:28:31.080
<v Speaker 1>you know, building any architecture. We've talked about the many

0:28:31.119 --> 0:28:35.000
<v Speaker 1>times that there have been redesigns and outcries and whatnot. Sure,

0:28:35.280 --> 0:28:37.919
<v Speaker 1>so yes, there's at least a brew haha if not

0:28:38.000 --> 0:28:40.680
<v Speaker 1>a kerfuffle. Yes, yes, I would agree there is at

0:28:40.760 --> 0:28:43.400
<v Speaker 1>least a brew haha, which as you know, is three

0:28:43.400 --> 0:28:48.680
<v Speaker 1>brooms short of a kerfuffle, but six brooms more than shenanigans.

0:28:48.720 --> 0:28:52.360
<v Speaker 1>So um yeah, it's uh, it'll be interesting to see

0:28:52.400 --> 0:28:56.000
<v Speaker 1>how this develops. I'm sure we will continue to see

0:28:56.280 --> 0:29:00.880
<v Speaker 1>developments in HTML five as well as its implementation. Uh

0:29:00.960 --> 0:29:02.840
<v Speaker 1>and and like I said, maybe a couple of years

0:29:02.880 --> 0:29:05.160
<v Speaker 1>down the road, that will be what everyone develops in

0:29:05.240 --> 0:29:07.160
<v Speaker 1>because it saves so much time to do it through

0:29:07.280 --> 0:29:11.720
<v Speaker 1>HTML five as opposed to designing native apps for you know, however,

0:29:11.800 --> 0:29:14.400
<v Speaker 1>many operating systems are out there. Granted, it may very

0:29:14.400 --> 0:29:17.080
<v Speaker 1>well be that the operating systems that are out there

0:29:17.520 --> 0:29:22.440
<v Speaker 1>boiled down to uh you know, Windows eight, iOS and

0:29:22.440 --> 0:29:25.480
<v Speaker 1>and Android, but you never know, we could still see

0:29:25.760 --> 0:29:28.080
<v Speaker 1>one of the other operating systems rise up, or even

0:29:28.080 --> 0:29:30.160
<v Speaker 1>a new one take takes center stage. I mean, no

0:29:30.200 --> 0:29:33.560
<v Speaker 1>one thought that palm would go anywhere when it oh

0:29:33.840 --> 0:29:37.400
<v Speaker 1>wait yeah, um yeah, and and that that's that's a

0:29:37.440 --> 0:29:40.760
<v Speaker 1>good point too. I mean that, uhh, this is this

0:29:40.800 --> 0:29:43.640
<v Speaker 1>is one of those things that I think will will

0:29:43.680 --> 0:29:48.440
<v Speaker 1>play itself out in in the standards simply because, uh,

0:29:48.480 --> 0:29:52.400
<v Speaker 1>it will be more universal and give people an easier

0:29:53.160 --> 0:29:57.760
<v Speaker 1>and more enjoyable experience once assuming that it does get adopted. Yeah,

0:29:58.040 --> 0:30:00.320
<v Speaker 1>it looks like from most what I've seen most recently

0:30:00.480 --> 0:30:04.680
<v Speaker 1>we're talking about as far as an actual standard is adopted,

0:30:04.720 --> 0:30:07.320
<v Speaker 1>at least that's the proposed date at this point, so

0:30:07.400 --> 0:30:09.600
<v Speaker 1>it's it's still a couple of years off. Yeah. And

0:30:09.640 --> 0:30:11.320
<v Speaker 1>the nice thing is that when you think about one

0:30:11.320 --> 0:30:13.200
<v Speaker 1>of the nice things about this is is when you

0:30:13.240 --> 0:30:16.200
<v Speaker 1>get to a point where HTML five becomes the basis

0:30:16.280 --> 0:30:21.240
<v Speaker 1>for most apps, or at least a good selection of them. Uh,

0:30:21.320 --> 0:30:23.480
<v Speaker 1>the nice thing about that is you can sit there

0:30:23.520 --> 0:30:27.080
<v Speaker 1>and get to a point where you know that the

0:30:27.120 --> 0:30:30.280
<v Speaker 1>app version of a particular thing, or the app on

0:30:30.400 --> 0:30:33.320
<v Speaker 1>your smartphone is going to work more or less the

0:30:33.400 --> 0:30:35.640
<v Speaker 1>same way as the app on someone else's smartphone, even

0:30:35.640 --> 0:30:38.120
<v Speaker 1>if they have two different operating systems, which is kind

0:30:38.160 --> 0:30:40.880
<v Speaker 1>of nice because right now that is not the case.

0:30:41.520 --> 0:30:44.360
<v Speaker 1>There are so many apps out there that have dramatically

0:30:44.400 --> 0:30:47.640
<v Speaker 1>different sets of features from one operating system to another,

0:30:47.760 --> 0:30:50.840
<v Speaker 1>because one of them may support something natively and one

0:30:50.880 --> 0:30:56.200
<v Speaker 1>may not, or because maybe one company has a huge

0:30:56.200 --> 0:30:59.280
<v Speaker 1>amount of horsepower on their mobile device but only allows

0:30:59.320 --> 0:31:02.000
<v Speaker 1>their own apps to have access to that power, and

0:31:02.040 --> 0:31:05.200
<v Speaker 1>no one else's apps can access that power. I'm not

0:31:05.400 --> 0:31:09.400
<v Speaker 1>naming names, Okay, I just don't own one of those,

0:31:09.800 --> 0:31:15.200
<v Speaker 1>um anyway, I'm kidding. I actually do own one desk

0:31:15.320 --> 0:31:19.400
<v Speaker 1>right now. All right, So we're going to wrap this up.

0:31:19.520 --> 0:31:21.920
<v Speaker 1>This was, you know, really again we're looking at this

0:31:21.960 --> 0:31:27.520
<v Speaker 1>whole Facebook HTML five mistake. I think even Zuckerberg would say, yeah,

0:31:27.600 --> 0:31:29.760
<v Speaker 1>it was just too early to make that move. It

0:31:29.800 --> 0:31:32.400
<v Speaker 1>wasn't necessarily that it's the wrong move in the long run.

0:31:33.040 --> 0:31:36.520
<v Speaker 1>It's definitely the wrong move when they made it, so,

0:31:38.120 --> 0:31:40.880
<v Speaker 1>I don't know, yeah, biggest mistake, that's arguable. There have

0:31:40.920 --> 0:31:42.840
<v Speaker 1>been people who said, what about launching that I p

0:31:42.960 --> 0:31:45.920
<v Speaker 1>oh so quickly. Of course they were really pressured to

0:31:45.960 --> 0:31:47.480
<v Speaker 1>do that. There wasn't a whole lot of choice in

0:31:47.520 --> 0:31:51.120
<v Speaker 1>that either. But although they could have anyway, that's a

0:31:51.160 --> 0:31:53.520
<v Speaker 1>totally different podcast which I think I think we've actually

0:31:53.560 --> 0:31:56.520
<v Speaker 1>recorded it. So um. You guys, if you have any

0:31:56.560 --> 0:31:59.880
<v Speaker 1>suggestions for upcoming episodes of tech Stuff, something that you

0:32:00.160 --> 0:32:03.280
<v Speaker 1>want to know way more about, you should definitely drop

0:32:03.320 --> 0:32:05.280
<v Speaker 1>us a line let us know. We'll be happy to

0:32:05.360 --> 0:32:07.719
<v Speaker 1>talk about it in a future episode. You can get

0:32:07.760 --> 0:32:10.320
<v Speaker 1>in touch with us over email our addresses tech stuff

0:32:10.360 --> 0:32:13.560
<v Speaker 1>at Discovery dot com, or let us know on Facebook

0:32:13.640 --> 0:32:16.040
<v Speaker 1>or Twitter or handle at both of those locations as

0:32:16.160 --> 0:32:18.440
<v Speaker 1>tech Stuff, H. S W and Tris and I will

0:32:18.480 --> 0:32:22.280
<v Speaker 1>talk to you again really soon for more on this

0:32:22.440 --> 0:32:24.960
<v Speaker 1>and thousands of other topics because it has staff works

0:32:24.960 --> 0:32:29.400
<v Speaker 1>dot com