Earlier quoted context omitted.
The issue may be, however, that the standards committees for HTML5 haven't defined how different implementations of these standards are supposed to play together. And the question is: does Apple have the right to define how HTML5 should be handled cross-browser? (In this case, by very simply denying all non-Safari browsers -- at least via that link -- the developer links work -- kind of.) In all fairness, I think the…
I’m sorry, but I am not sure what you are saying. Web standards circles agree that "browser sniffing" as opposed to "feature detection" is kind of evil. (See http://modernizr.com for one way to do it right.) This, however, is a very special case, where the whole point is showing what ones specific browser can do. Generally, the user's browser is irrelevant to the point of a website, and supporting as many browsers as…
On the other hand, browser sniffing, as you mention, is a slippery slope. Maybe all they might do is acknowledge that until other browsers have fully implemented 3D CSS, etc., they are only recommending Safari.
ETA: Never mind, I went back and read the page:
Not all browsers offer this support. But soon other modern browsers will take advantage of these same web standards — and the amazing things they enable web designers to do.
Good enough I suppose...