When will the next version of HTML be ready? Apparently, we have 4859 days to go before HTML5 reaches the “Proposed Recommendation” status. That’s 13 years, according to Ian Hickson, editor of the HTML5 specification.
It’s been 10 years since HTML4 came out. And it will take a total of 19 years for HTML5 to come to fruition. Here’s staggering journey HTML5 has gone and will go through:
- First W3C Working Draft in October 2007.
- Last Call Working Draft in October 2009.
- Call for contributions for the test suite in 2011.
- Candidate Recommendation in 2012.
- First draft of test suite in 2012.
- Second draft of test suite in 2015.
- Final version of test suite in 2019.
- Reissued Last Call Working Draft in 2020.
- Proposed Recommendation in 2022.
So what do we do about this excruciating piece of information? Jeff Croft says we should just go back to work. And ignore HTML5 until we absolute don’t have to.
If and when HTML 5 becomes something that can help me serve my clients and the users of their websites, then I will absolutely learn all there is to know about it and incorporate it into my arsenal. Until then, I don’t see the point.
It’s only a bit disappointing since the knowledge of the beautiful things one can achieve with HTML5 has been coming and going for the past few years now. But the thing is, as Kroc Camen said, “HTML5 is doable in the here and now”—his site is excellent proof of that. Except, of course, it will take extra work for it to work properly as not even the standards-compliant browsers support it. Which brings us back to Jeff Croft’s point.
In an interesting development regarding web standards and the browser wars, Ars Technica reports that Mozilla is taking Internet Explorer’s problematic webpage rendering into its own hands starting with a plugin for HTML5’s canvas element.
IE’s shortcomings won’t hold back the Internet for much longer, however, because Mozilla plans to drag IE into the next generation of open web technologies without Microsoft’s help. One of the first steps towards achieving this goal is a new experimental plugin that adapts Mozilla’s implementation of the HTML5 Canvas element so that it can be used in Internet Explorer.
Vladimir Vukićević says it’s “a very direct way of getting 2D (and soon 3D) graphics into web pages, and removes many of the barriers between developers and graphics rendering.” Here’s a screenshot of how it works:
HTML5 Canvas on IE, by Vladimir Vukićević
Mozilla doesn’t stop there, though. It plans bring its “next-generation JavaScript engine directly into Microsoft’s web browser” through a project called ScreamingMonkey. The plugin strategy will also be employed here.
Mixed reactions
Reactions from the crowd range from amusement to confusion to outrage. On the one hand, this move from the makers of the record-making Firefox browser is commendable. It shows that in the midst of IE’s dominating market share and FF’s sheer drive to beat it, Mozilla still wants the Web to work, one way or the other. Even if it means having to “drag IE” itself. Indeed:
Is it a sad or happy day for Microsoft, when their competitors get bored with beating them, and instead try to improve the Microsoft products to make them competitive - for free?
And what does Microsoft have to say about this? Isn’t this an insult wrapped inside a well-meaning gesture since it is coming from a competitor? Anything that gets Microsoft’s attention to hurry things up in the web standards compliance department is okay by me.
Try Adobe
But it’s not just about the browser vendors but the users themselves. How many of them will take the time to install this not-so-popular plugin? Do they care enough to see the advantages? Ars Technica thus wonders if Adobe could have been the better messenger, since Flash is ultimately indispensable these days:
This is purely speculation, but If Adobe decided to ship Screaming Monkey and the Canvas functionality as part of the next major iteration of the Flash plugin, it would rapidly accelerate adoption and get it onto lots of computers.
Cross-browser nirvana? Not quite
News of this plugin suggests that it’s taking a so much effort to make IE play nice that even competing browsers have to step in. And we’re only talking about the HTML5 canvas element here, a far less common feature, or should we say issue, than things like the double-margin bug or pixel font sizes.
A few weeks ago Google announced that it can now extract and index textual content from Adobe Flash files. We all know that creating websites in pure Flash is a big no-no if you care about being found through search engines. So is there nothing left that’s stopping web designers from switching from plain old HTML and CSS to rich interactive Flash? I have yet to find somebody who agrees with a resounding “yes!”
Rand Fishkin, CEO of SEOmoz, believes that this new development isn’t compelling enough to start building sites with Flash.
Flash content is fundamentally different from HTML on webpage URLs and being able to parse links in the Flash code and text snippets does not make Flash search-engine friendly. I think it’s great that Google’s digging deeper into Flash, but I don’t believe web developers should be any less wary than they’ve been in the past about Flash-based websites or Flash-embedded content.
If anything, I commend Google for continuing to convince web designers and search engine marketers alike to embrace web standards by pushing for the best practices in coding websites. Of course it’s the most logical thing both parties: search spiders need to parse content properly so that they can index it, and a well-formed webpage makes this possible; webmasters need not wade through nested tables and unnecessary tag soup when there’s a better way. And Google should, since it’s way more influential than Opera or any other web company out there.
However, Google’s efforts to read Flash still seem to be in the premature stages. Typical Google, they always release their products in beta without being wary of the consequences.
By consequences I mean clients who are now running around telling their web designers to create animated intros and the extravagant interfaces for their websites. I can’t really shoot down this little achievement by Google—except that it’s getting scarily smarter everyday and should try to have more features than issues when they launch a product.
More importantly, I can only continue to condemn those who misuse Flash without any regard for accessibility, much less usability, whatsoever.
The Opera Web Standards Curriculum is a comprehensive online course that teaches you standards-based web design. This includes not only coding in the web’s foundational languages, HTML, CSS, Javascript, but also design theory.
One of the authors, Chris Heilmann, describes it as “probably the most thorough and up-to-date web standards curriculum on the web”. He writes:
During the whole course the main focus is on usability, accessibility and writing maintainable code. We deliberately left out browser hacks and backward facing solutions and build on the ideas of progressive enhancement and unobtrusive JavaScript.
I must also point out that WSC is part of Opera Education, an initiative that pushes for web standards awareness and enthusiasm for the internet industry, specifically in schools and universities. I think it’s important for these two parties—browser software makers and educational institutions—to work together rather than apart in developing the Web. In this regard, Molly Holzschlag believes the course is an A+:
The impressive aspect of the curriculum as it is now is that it’s comprehensive, including foundational topics such as Internet and Web history and evolution. Educators understand that history provides context for real learning. Sadly, this is an area often not available in books and online tutorials because readers typically want to dive right in and learn a given technique.
It’s difficult to find a course that focuses solely on creating things through the internet. It’s almost always integrated with either graphic design (see MTV Engine Room) or computer science. Because of this, there is no focus on employing the best practices in creating beautiful, functional websites. And it will continue to be that way—all the way into the workplace—without those two entities joining forces.
This is why I continue to admire Opera. (Mozilla does, too.) It pushes projects that are interesting and beneficial to the web community. Here’s another example: Opera Dragonfly. Firefox’s FireBug wasn’t created by Mozilla (although Safari’s Debugger is a native feature).
And unlike other browser vendors out there, Opera shows it cares about web standards not by saying but by doing.
According to the latest episode from the Boagworld podcast, “you might be wasting your time designing with CSS” because now that Flash is open source, it’s “going to be everywhere and is the platform we should now be developing on”.
Flash versus CSS? What?
Let’s backtrack a bit. Adobe recently announced the Open Screen Project, which will implement a “consistent runtime environment” for Flash (and AIR) across all platforms. All, as in every medium imaginable: computers, mobile devices, TVs, and everything in between. Adobe working hand in hand with some of the biggest names in media and electronics to make this possible. For a company that’s always created proprietary technologies, moving to an open mindset is a bold move. But this will cement the popularity and innovativeness of Flash.
So how does Flash compete with CSS? We shouldn’t take the Flash vs. CSS part literally. It should be more like Flash vs. HTML and CSS. Or HTML and CSS and JavaScript. Wait, what about AJAX? And Silverlight?
See how silly this bout has become? All these web technologies are not direct competitors. (Except for Silverlight, perhaps, but I’m not even sure if it still stands a chance.)
But there’s a very real question being posed here. Should HTML/CSS coders move on to what seems to be the greener pasture that is Flash?
I firmly believe that not every website in the world has to be done in Flash for it to be jaw-droppingly awesome. There will be Flash developers who believe exactly the opposite. There will be hybrid web designers who can straddle between both and don’t really feel the pressure. Any of the three will prevail in the future, but from the looks of it right now, there’s still a place for plain old HTML and CSS no matter how big Flash has become.
Besides, both camps are still considerably immature. The web in general is, actually. It’s just that with all the effort spent into creating websites and the money that can be made from them, web technologies seem complete already. But they are just as dynamic and unpredictable as the web itself.
