I'm not sure I understand the bad part you're objecting to.
Is it that webkit is implementing different parts of "HTML5" and related specs that haven't been finalized than other browsers? All the browsers do this, and it's a good thing. Not only are independent implementations required for w3c specs to even become finalized, it's also widely accepted that implementations of features (prefixed and possibly guarded by runtime flags or confined to non-stable versions of a browser) are often the strongest case you can make for adding something to a spec in the first place. This is a difficult tightrope to walk, as you can easily go too far out ahead of a working group, but it has served us pretty well in the last few years.
Or is it that this slide deck is using non-standard features to give a preview of what the standards working groups are working on? Here's a not very hypothetical hypothetical: if you were giving a talk on upcoming Javascript features in es6, and you wanted to talk about the yield keyword, a great way to show it in action is to add a 'type="application/javascript;version=1.8"' to your script tag, which allows the use of yield today in shipping Firefox browsers[1].
To be sure, you're not recommending that developers go out and build their apps around this right now, because it only works in one browser (maybe two if v8 has added yield behind their "Enable Experimental JavaScript", I'm not sure). But showing it in action is a powerful education tool.
Now, if you wanted to publish your slide deck afterwards, what would you do? A pdf of your slides is pretty lame, at least on its own. It was interactive during the presentation, there's no reason it shouldn't be interactive when playing with it online, but you'd have to warn that it only works in Firefox. You could add that static pdf version as well, but the code is already right there in the page, and this is a developer audience, so they almost certainly have Firefox installed no matter what browser they use for day-to-day browsing.
It's really not that big of a deal. Save the anger for actual attacks on the web.
I don't see any anger in my comments, simply disappointment. Let me explain it a last time in a very simple manner:
I'm no developer and I must use Chrome to see this website properly, and it's far from the only website with that issue. In fact, even if I was a developer, I should be able to view any site that's designed for production browsers properly, with any browser, as long as they're not buggy.
So, there's a standardization problem. You can keep trying to defend it and how it's all made in good faith - it might even be - but the end result is unfortunately, the same.
Is it that webkit is implementing different parts of "HTML5" and related specs that haven't been finalized than other browsers? All the browsers do this, and it's a good thing. Not only are independent implementations required for w3c specs to even become finalized, it's also widely accepted that implementations of features (prefixed and possibly guarded by runtime flags or confined to non-stable versions of a browser) are often the strongest case you can make for adding something to a spec in the first place. This is a difficult tightrope to walk, as you can easily go too far out ahead of a working group, but it has served us pretty well in the last few years.
Or is it that this slide deck is using non-standard features to give a preview of what the standards working groups are working on? Here's a not very hypothetical hypothetical: if you were giving a talk on upcoming Javascript features in es6, and you wanted to talk about the yield keyword, a great way to show it in action is to add a 'type="application/javascript;version=1.8"' to your script tag, which allows the use of yield today in shipping Firefox browsers[1].
To be sure, you're not recommending that developers go out and build their apps around this right now, because it only works in one browser (maybe two if v8 has added yield behind their "Enable Experimental JavaScript", I'm not sure). But showing it in action is a powerful education tool.
Now, if you wanted to publish your slide deck afterwards, what would you do? A pdf of your slides is pretty lame, at least on its own. It was interactive during the presentation, there's no reason it shouldn't be interactive when playing with it online, but you'd have to warn that it only works in Firefox. You could add that static pdf version as well, but the code is already right there in the page, and this is a developer audience, so they almost certainly have Firefox installed no matter what browser they use for day-to-day browsing.
It's really not that big of a deal. Save the anger for actual attacks on the web.
[1] https://developer.mozilla.org/en-US/docs/JavaScript/New_in_J...