6 ms·
Since when has Apple supported open standards simply because it makes sense to do so? Apple almost invariably chooses closed over open.
by redthrowaway 16y ago
Since when has Apple supported open standards simply because it makes sense to do so? Apple almost invariably chooses closed over open.
- rradu 16y agoApple is fully behind HTML5 - http://www.apple.com/html5/ http://www.apple.com/html5/
- jarek 16y agoYes, in spirit too: "This demo was designed with the latest web standards supported by Safari. If you’d like to experience this demo, simply download Safari. It’s free for Mac and PC, and it only takes a few minutes." Come see web standards! Using a specific browser.
- joubert 16y agoHum, because they're showing the latest HTML features that Safari supports? Not all browsers support the same range of features for a particular HTML standard.
- jarek 16y agoAny organization which denies access to its HTML5 pages to browsers that support them is not fully behind the spirit of HTML. The reason is clear and understandable — marketing their browser — but so are the implications.
- jarek 16y agoA couple of days later, I found this: How much HTML5 is there in Apple's HTML5 demos? http://blog.marcoos.com/2010/06/09/is-html5-by-apple-really-html5/ http://blog.marcoos.com/2010/06/09/is-html5-by-apple-really-...
- ZeroGravitas 16y agoYet the number one reason there isn't a codec specified in HTML5 is because Apple blocked it.
- ZeroGravitas 16y agoAlso, Apple used to be fully behind royalty-free standards for the web: http://lists.w3.org/Archives/Public/www-patentpolicy-comment/2001Oct/1488 http://lists.w3.org/Archives/Public/www-patentpolicy-comment... Apple believes that it is essential to continued interoperability and development of the Web that fundamental W3C standards be available on a royalty-free basis. In line with the W3C's mission to "lead the Web to its full potential," Apple supports a W3C patent policy with an immutable commitment to royalty-free licensing for fundamental Web standards. Apple offers this statement in support of its position. It's powerful and persuasive stuff, worth reading in full. They only removed this statement from their website about 6 months ago.
- extension 16y agoHave they said or done something that conflicts with this statement?
- mbrubeck 16y agoTheir implementations of the HTML5 <video> and <audio> draft standards work only with royalty-encumbered codecs. (The licensing is currently royalty-free for publishers and end users, but not for device manufacturers or browser vendors.)
- extension 16y agoHave they ever proposed that those codecs be part of the standard?
- rmc 16y agoGoogle were also opposed to a format in the spec, they claimed ogg theora was too large in file size. Why do you think they bought On2 and released WebM in the first place? There already was a free video code theora before.
- sid0 16y agoYou call this being "fully behind HTML5"? http://grab.by/grabs/0b694089e83975c385627b134ee8ece7.png http://grab.by/grabs/0b694089e83975c385627b134ee8ece7.png Even Microsoft's better than this. edit: could whoever downvoted me explain why he did so?
- tzs 16y agoThat's not inconsistent with being "fully behind HTML5". That page is meant to show off how Safari handles various HTML5 features. If you view it in a different browser, it is not showing you how Safari handles those features. Hence, it makes perfect sense for it to try to limit itself to people using Safari.
- sid0 16y agoThat page is meant to show off how Safari handles various HTML5 features. Isn't the point of HTML that all browsers handle it similarly? If that link is restricted to one browser, it isn't better than all the "Designed for IE6" sites you used to see in the early '00s, and absolutely no evidence of Apple being "fully behind HTML5".
- tzs 16y agoHTML5 is not a standard. It does not yet behave the same in all browsers that implement it. Different browsers implement different subsets of it. The site you cite is meant specifically to show how Apple is doing with their HTML5 implementation. There is simply no point in viewing it in another browser. Viewing it in, say, Firefox would tell you nothing at all about how well Apple has implemented HTML5 in Safari. This is completely different from the "Designed for IE6" sites. Those sites were generally presenting information that was useful to people regardless of which browser they were using.
- sid0 16y agoHTML5 is not a standard. It does not yet behave the same in all browsers that implement it. Different browsers implement different subsets of it. And yet they're converging to implementing all of it. The site you cite is meant specifically to show how Apple is doing with their HTML5 implementation. Then it's a Safari demo, not an HTML5 demo. The Microsoft demos use HTML5 and yet work just fine in other browsers. Those sites were generally presenting information that was useful to people regardless of which browser they were using. How is seeing HTML5 working in Firefox or Chrome not useful to people?
- hexley 16y agoComment of the year right here, folks. +4 already too. Thank heavens its a throwaway, how embarrassing.
- andybak 16y agoIt's not exactly insightful but it does have some merit. Apple's approach is an odd mix of open and closed. You could describe it as 'strategically open'... (of course - this applies to Google too to a slightly lesser degree). No company supports open-source if it directly conflicts with their perceived interests. Some companies just take a wider view than others.
- hexley 16y agoI'd like to see a compiled list of open technologies Apple has chosen vs closed. "invariably closed" my arse.
- drivebyacct2 16y agoI love to hate on Apple's decisions, but this is just ludicrous.