You used JavaScript to write WHAT?
I think it's an interesting article. In particular, the author's comments about JS performance on page 2. Oh, I really want to get my hands on Tamarin inside Firefox...
There's a thought that's been rumbling around my head for a few weeks, and I just want to throw it out there. Wouldn't it be nice, as Tamarin stabilizes, to have a Firefox 3.1 which was the same as Firefox 3.0, but using the Tamarin engine instead of the current JS interpreter? The first fruits of Mozilla 2.0, so to speak, and a preview of what's in store for JavaScript-land. We could even call it Firefox 3.14159. :-)
I have no idea if this is technically feasible or not. Hopefully one or two of the Tamarin hackers can chime in here.
I know I'm going to get flamed for this, but...
Everybody on p.m.o is ranting hard about Microsoft's decision to include a third mode for web standards rendering. They're all calling on Microsoft to Tell The Non-Compliant Web To Take A Hike.
What makes me chuckle is that, in one sense, the p.m.o community is telling Microsoft to act like the monopolist the community hates. The community is telling Microsoft to dictate to the Web (again) how the Web should be, to throw its massive market share around and do something that might break the Web. Bear in mind that massive market share, the ecosystem of the Web, isn't just about the browsers. It's also about the portals, sites we visit all the time, like CNN, NBC, MySpace, Wikipedia, etc.
You know what? Someday we're just going to have to learn not to give a damn what Microsoft does with their browser. Let the evolution of the Web decide what's best. Let Firefox be Firefox, let Opera be Opera, and if Microsoft doesn't want to come to the table, fine. Then the W3C might mean something again - or the WHATWG will just replace it. (Just as long as people don't cheat and make sneaky side agreements to install their browser as the default... oh, wait, ummm...)
On second thought, they're just feeding authors' addictions to bad code. I really ranted about that a few weeks ago. Let them (bit)rot. :-)
Update: A few people seem to think that I want to dictate to Microsoft how they should build their browser. I want to strongly suggest they do certain things (where's my DOM 2 TreeWalker?), but I am not going to scream bloody murder about it.
Personally, I do think three rendering modes is a bad idea. But then again, I don't have a website. I'm pretty sure if I did, I'd have to think long and hard about supporting Internet Explorer with more than basic HTML. IE's users are rarely my target audience anyway.
Seriously, people, this blog post is about two words: Lighten up.