Internet Explorer 9 is not available for XP users – you need to have Vista or Seven to get IE9
Upgrading to Vista was not really exciting enough for a lot of businesses when it came out
Upgrading to Seven normally means that you also need to upgrade the hardware (which is actually a very common happening – as a lot of users simply don’t know what a browser is or don’t get the rights to choose an own browser in a corporate environment IE only gets upgraded when they get a new computer)
A lot of Windows XP machines never got upgraded as they had a pirated OS. The Genuine Check of Vista told users “computer says no” and that was that.
Now, I personally want to have HTML5 and CSS3 and other new exciting technologies right now – I am tired of writing code for cool things that browsers should be doing for me.
As Microsoft is spending a lot of time and effort to promote just how cool IE9 is and glosses over the fact that XP users cannot get it, I thought it is time to advertise the fact that users have a choice – even when they stick with XP. For Microsoft this doesn’t make any business sense as they want to sell Seven, and they are right in telling people that systems need upgrades. However, if the upgrade means spending a lot of money on new hard and software then I can also understand people who don’t want to do that. With Apple products being very expensive and Linux just not being as “mom and dad end user friendly” as Windows is this is what we are stuck with.
This is why I built HTML5 for XP, the site that Microsoft should release themselves. Please tell people about it and send it to your clients.
Creating it was the fun part. I wrote it, created a simple web site (fighting the urge to use all kind of CSS3 awesome as it needs to work in IE6…) and then asked for translations and promotion on Twitter. I put up a Google Spreadsheet with the texts for translation and shared it with the world. This was a too hippy an idea as it meant people did the cool h4xx0rrrr! thing of deleting all the content (well done, lads, wait for Trinity to knock on your door really soon). So I made it an invite only document to submit translations and within a day I had 16 languages – now we are up to 20. I also have to thank Prisca for making the CSS pretty as of course the first feedback from designers was that “this is ugly”.
The saga continues – IE6 has to die! Spread the word.
If you followed my exploits lately in the realm of HTML5 video you’d know that I am a big fan of the video conversion servicevid.ly. This service automatically converts your videos to dozens of different formats and redirects your browsers and mobile devices to the correct format when you call up a single URL.
Being a paranoid developer, I also wanted to have a way to download the browser optimised versions of the videos, so I wrote a bookmarklet to allow you to do that.
I just got back from Heart and Sole in Portsmouth where I was asked to give an inspiring talk about HTML5. I thought it is high time to make an audience like the one at Heart and Sole (students and small business owners) aware that HTML5 is not only a plaything of large companies and “web development rockstars” but that everybody can be part of the cause and that we really need people’s input and real life implementations to make the new open tech revolution a reality. The feedback was very positive. Here are the slides and notes with links. The conference was filmed so keep your eyes open for the recording of the talk.
I am a big fan of open web technologies. Right now we are working on some great things that will make the web more responsive, allow for more creativity and extend the text based web to richer media like video, audio and 3D without resorting to closed development environments or having to pay licenses.
This is all great, but I really think it is time to take HTML5 out of the labs and into our day to day jobs. We should start now to make HTML5 part of our deliveries and get clients excited about the new opportunities there are. Instead of celebrating HTML5 rockstars we should celebrate the opportunity to make our work more predictable, open to everybody and easy to use.
Help promote HTML5
This change needs promotion – by you. If you work on the web you should help make new open technologies succeed by using them in real products.
Why should you care about this?
Well, first of all we have to make our work professional and be more accountable for what we do.
There should not be any magic in web development.
You should not have to use some technology you cut and paste and have no clue what it really does. “It works, just use it” is not a sustainable environment.
When things go bad, you should be able to trace the reason and fix it. Right now I get the feeling that a lot of web development is putting together random building blocks to build an interface that looks like a design we got handed down to us. That is the wrong way around. If we build from blocks we understand the interface can mutate and change to our needs and likes. If we start with a fixed idea any change later on will mean we need to replace everything. We’re not re-using enough.
Take pride in the invisible
Clients still don’t care much about our code and markup but we should. When I interview people I take a look at the source of the things they send me. The markup and CSS and JS code you leave behind is the message you give to the next developer. If it is unreadable or hard to maintain you come across as not caring. It is like a blog post with a very important message that gets lost because of abysmal grammar.
In the past we wrote browser specific code and omitted elements as the browser fixed it for us. Just because browsers are forgiving it shouldn’t mean it is OK to rely on them to do fix things. No other programming language allows you to write code like that. If we want to be taken seriously, we should take pride in our work. Not one browser will ever rule supreme, so if you rely on one for your product to work you add to the problem of people not upgrading their browsers. This is not innovation.
HTML5 is not perfect
There are a few things we should worry about. As with every change, we will have to face a lot of people who are against it.
Adversity to change
A lot of propaganda is being thrown around right now about HTML5 not being ready for prime time and open technologies being dangerous as you have no control over them and there is nobody to back them up. This has been a long-standing problem with any open source technology.
No one size fits all
The fact is that HTML5 and open technologies will not fit every problem out there. HTML5 is not there to replace Flash or Silverlight – it is there to offer an alternative.
Open media can be downloaded
A few days ago Serge Jespers of Adobe released an article about the problem of HTML5 that there is no DRM solution. The article had a good point, but the title “Stealing content was never easier than with HTML5” was very misleading. I have complained about this as it just heated the debate unnecessarily. Fact is that right now there is no file level protection of video in HTML5. If you want a protected stream that people can’t download, then you need to use Flash or Silverlight. The real question though is that if you want to protect something, why allow it to be in the open in the first place?
Open means you can fix without asking for permission
The great thing about any HTML5 issue like the ones above is though that the technology is open and everything can be analysed and fixed – if we can make it a priority. A closed system is a pain to patch and upgrade. Open systems are easier to fix and with the attack research being available we have the chance to patch problems before they get implemented in browsers. Security through obscurity was never a clever idea. If you commit a crime and plead in court that you didn’t know that what you did was illegal you won’t get away with it either.
Welcome to the sweet spot
The other great news about HTML5 is that you are in the sweet spot.
Take part in the process
First of all, it is not a secret club and you are invited to take part. The WHATWG Mailing List is where things happen and all you need to do is sign up.
Free and open documentation
How about learning HTML5? You don’t need fancy trainings or buy books (but there are some awesome ones out there). HTML5 Doctor is a great independent blog talking about everything HTML5. Mark Pilgrim’s book Dive into HTML5 is freely available on the web and if you want to meet a lot of enthusiasts of HTML5, just pop by on the IRC channel #html5 on freenet.
Tools to make your life easier
One of the main stumbling blocks for people to use for example HTML5 video instead of Flash is that you need to create the video in different formats. There are some services though that make it easy for you. I have listed a lot of them in my notes of my HTML5 multimedia talk at MIT but here is a reminder about two great services.
Archive.org for video hosting
Archive.org does not only store video for you when you release it under Creative Commons but also automatically creates an MP4 and OGG video from your movies for you.
Vid.ly for online conversion and dynamic redirection
A very new service by Encoding.com is Vid.ly which creates not only all the formats needed for different browsers for you, but also special versions for different mobile devices and HTTP streaming optimised versions for iOS devices. Furthermore, it creates one simple URL that redirects automatically to the right format. You can try it out yourself with the invite code HNY2011.
Modernizr to test for support
Polyfills to support legacy browsers
If you want to use the new features and make old browsers get the same functionality via other technologies, you can pick and choose from the selection of legacy browser polyfills available based on the same research.
We need you to make this work – you have the tools, your input is valuable and please drop by and say hello. Also, check out the Mozilla Developer network as we’ll be releasing some cool things you can be part of very soon!
I just released the notes of my “Using HTML5 sensibly” talk over on the Mozilla hacks blog and there are a few questions that need answering by anyone who wants to be part of publishing on the web in the future:
Can innovation be based on “people never did this correctly anyways”?
Is it HTML or BML? (HyperText Markup Language or Browser Markup Language)
Should HTML be there only for browsers? What about conversion Services? Search bots? Content scrapers?
Should we shoe-horn new technology into legacy browsers?
Do patches add complexity as we need to test their performance? (there is no point in giving an old browser functionality that simply looks bad or grinds it down to a halt)
How about moving IE fixes to the server side? Padding with DIVs with classes in PHP/Ruby/Python after checking the browser and no JS for IE?
Can we expect content creators to create video in many formats to support an open technology?
Can a service like vid.ly be trusted for content creation and storage?
Is HTML5 not applicable for premium content?
Check the detailed notes on the Mozilla blog, and – as a reminder – here are the slides and the video of the talk:
Especially the second talk was close to my heart as I think it is high time us developers take back HTML5 from the marketing people. HTML5 is the evolution of our web technologies, not another flashy add-on to already badly used outdated practices.