From the author's tone, it seemed clear to me that this was a case of him having an axe to grind rather than being actually stymied by a serious deficiency. Not particularly constructive.
“Works in pretty much any modern browser except IE (because IE doesn't have support for the <canvas> tag).”
Please explain to me where “tone“ is hiding in that sentence. I don’t see it. There is nothing at all judgmental about it. It’s matter of fact, I don’t even see so much as a word or phrase that could in any way be construed as a snide remark directed at IE. I can’t find any possible interpretation that would hint at any kind of axe the author might have to grind. Context doesn’t help, either.
The actual tone might help but the author sadly doesn’t provide an audiobook version of the webpage.
(Snap judgments. This is why we can’t have nice things.)
Second: It's context. There's no need to talk about deficiencies of browser on a page trying to illustrate bittorent. He could have just said "does not work with IE".
This was just a quick one-off hack that I did for fun. I had no idea how many people would find it interesting.
If anybody does want to fix the code so that it loads properly in IE (and doesn't break any other browsers) I'm more than willing to integrate the changes!
Well, there is the "PLAINTEXT" tag[1], but I don't know if that will actually get all of IE6's security issues, even if you put it at the very start of the document.
The attributes for it are pretty weird, too. Why would you put language="javascript" inside such a tag?
