For Apple, Web Standards Equals Safari Only

Apple's campaign to push HTML5 as the alternative to plug ins has taken a very odd turn. They've added a page to Apple.com to demo HTML5 with this particular twist:

You need to use Safari to access the demos.

Now, I'm browsing in the latest version of Chrome - which also uses WebKit for rendering and JavaScript. I'm sure there is a fork in the road from the Chromium project but they should be extremely close when it comes to features and standards.

And Apple won't even let me use that.

Instead of championing the supposedly future thinking open development that Jobs insists is superior to the "old ways" - the page highlights exactly what is wrong with the stance Apple has taken. First, net users have never really cared if a feature set is blessed by some committee - they want things to work in the browser of their choice. Second, Apple's concern for the use of these standards is directed in one direction: users of Safari ... and in reality, users of Mobile Safari.

Together and you can see that this is actually the same strategy Apple took with the cross-compilation issue. They're not concerned with creating content consumable across the net - if they did then they wouldn't block this demo down to Safari and conversely, developers would not need to worry about an iPad version of their website. No, they are concerned with content which falls under the umbrella of Apple software.