Why Are We Moving to HTML5
Why are we moving to HTML5? is HTML4 just not good enough? Fair enough, before we really start digging deeper into the world of HTML5 let's understand why we are making this move.
Video Transcript
00:00Alright, so I think we're ready to get rolling and started.
00:04So first of all, we really have to go and understand that the web is evolving and I'm
00:09sure you know it every single year when we go onto the web, the web is a little bit different.
00:14And the web is really changing really, really fastly.
00:19One thing that hasn't changed fastly and hasn't changed really at all for quite a while,
00:24and I'm not going to go into this long spiel about the history.
00:27If it interests you, you could always do a Wikipedia search on it or send me an email and
00:31I'll tell you a little bit more about the history.
00:33I really want this to be a more hands-on, let's get dirty and start building.
00:38So the shortest version of history that I could give you is HTML4 was the fourth version of
00:43the specifications from the W3C that basically said this is how you build websites in HTML.
00:51Now that was the recommendation of the W3C at 1997.
00:56The different browsers started implementing them, it was kind of like one of those things
01:00that after it was created then the browsers were starting to only back in those days they
01:05started to actually conform to the specifications.
01:08These days were in a bit of a different age, so now we're in the year 2012, it's been quite
01:15a while since 1997 and a lot of things have changed from websites that were mainly textual.
01:21We got into a web that was very, very graphically heavy.
01:25And then the different specifications for CSS evolved and all these other specifications
01:30that really made a little bit of a separation where we're not going to dig too deep into
01:36all these different topics, really the main focus is that HTML4 itself hasn't changed
01:41at all in a very long time.
01:44And the question lies is does HTML4 today, is it able to provide all the things that
01:49we need in a modern browser experience?
01:52And the answer is no, because as you know there's the Flash Player, there's Silverlight,
01:56there's a lot of third party tools today that enable us to get that full experience of
02:01the web.
02:02And even some rudimentary core things that we really would hope that the browser would
02:06support such as video playback or music playing are just not supported.
02:12So HTML4 has been really lagging behind for a very long time and that's which brings
02:18us into our topic of today which is HTML5.
02:20Now HTML5 is still a draft, they started working on this draft in 2004 so it's a very
02:26long draft, it's been eight years in the working.
02:30This draft though is as we're talking about in the year 2012 which we're at right now,
02:37it's still a draft, it's a working draft.
02:40And it's a little bit different than previous versions of the HTML specifications and one
02:46of the stuff is in HTML4 the coin, well every single version of HTML basically came to improve
02:52the last version of HTML and remove previous tags.
02:58Now already the rules of the tagging have been already, kind of already defined, we want
03:03to put our visual things in CSS, we want to put our structural stuff in our HTML, we
03:09want to put our coding in our JavaScript, we want to put some of our external data
03:13maybe in XML or databases.
03:17So the changes in the core of this really is that the word deprecated is one of the coolest
03:24things of the new updates of this goal was the idea was, and this is a really cool idea
03:33and a very, very smart version, a very smart idea in the world of HTML5 is the idea is
03:38that deprecations have been deprecated.
03:41This does not mean that you should start using now old tags that are relevant to HTML3 like
03:46the font tag, although they're still supported.
03:51Obviously one thing that the World Wide Web Consortium, the W3C Consortium really realized
03:56was that there's no point in deprecating things that are being used on the web.
04:01You can't say from now on these tags are not going to work because they need to be
04:06backward compatible.
04:07It's that every single website could be updated as soon as a specification or browser updates.
04:13So the idea behind it is whatever was already agreed upon, browsers need to continue and
04:18support.
04:19So even if the font tag is been for a very, very long deprecated, for now on they're
04:24not deprecated anymore.
04:25Now what does that mean?
04:26Does that mean we could do whatever we want whenever we want?
04:29In theory, yes.
04:31In theory, you could definitely use stuff that are now allowed to.
04:34You're not going to pass through an HTML5 validator because these tags don't exist in
04:38HTML5 anymore.
04:40There's tags that have been removed from the specification.
04:43But the browser itself is still in charge of making sure that these tags still work,
04:49which is really a cool part of this whole thing.
04:51So basically what we're saying is there's actually two different specifications.
04:55There's a specification for us as the developers telling us, okay, from now on these stuff
04:59don't use them anymore.
05:00And there's a specification for the browser companies, basically tell them, well, you have
05:05to continue implementing this because it's part of the specification of the previous specifications.
05:10So that's what's really, really cool about this new version of HTML5.
05:13The goal of it is not to terminate HTML4 websites.
05:17And contrary to the popular notion of it's the flash killer, it as itself as a technology
05:23is not there to kill anything.
05:25It's there to add more features and add more capabilities to the browser.
05:29With that said, it is throwing out a few features saying, well, we really don't recommend
05:34you using them because we have now new solutions and use those new solutions.
05:39But in the real world, if you get into a scenario where you feel like you have to
05:42use it, you're trying to do a quick fix, it will still work because all the browsers
05:45are meant to make sure that they continue and support the previous specifications.
05:51So that's our long short story about the history of HTML4.
05:57We're not going too much far in the past, and we're talking about HTML5.
06:00Now, it's a working draft.
06:02The last thing I want to say about this is what does a working draft actually mean?
06:06It means that the specification is still evolving, there's still going to be tweaks and changes
06:09to it.
06:10A lot of stuff are very solidified already at this stage, as it's been eight years
06:14in the running.
06:16Browsers are already implementing the HTML5 specification.
06:20Some of them are more complete, some of them are less complete, but the specification
06:26will change, and it's going to change basically based on the feedback from the browser manufacturers.
06:31So this is actually a really interesting way that W3C decided to do it this time around
06:36where previous versions of HTML, they first made the final recommendation, and then the
06:43recommendation was then sent basically to be implemented by all the browsers.
06:48Well, the HTML5 specification is a working document, and it's kind of a living document
06:53that's basically going to be updated based on the needs of the different browsers, making
06:57sure that this works and everything is implementable, and when they reach the conclusion that everything
07:02is good, they're going to lock it up and say, okay, all browsers don't support all
07:05these features, which is a wonderful, wonderful idea.
07:08I'm really, really excited about that, and that's it.
07:11We're done with history, we're done with theory.
07:13It's time for us to get our hands dirty and actually see in action all the different
07:17things that we could start doing in HTML5.
