And speaking of Firefox ...

I just went to an interesting, if lightning paced, talk by Robert O'Callahan, who works for the Mozilla Corporation. He showed some pretty damn impressive SVG stuff in the Firefox 3 beta that I haven't seen before. He stressed that the point of Mozilla is to promote an open web, and part of that mission is to try to encourage developers to move away from using proprietary plugin based architecture, such as Flash and Silverlight, to do their cool stuff. That's all very well, but there are powerful authoring tools for Flash (I don't know about Silverlight) and not many for SVG. I didn't manage to ask the question, but I wonder if Mozilla would consider a foray into the world of authoring tools.

John Gruber has switched back to Safari after a dalliance with Firefox 3, and outlined some of the reasons for switching back. It's a feature comparison, and I don't know some of the Safari features or care about some of the Firefox shortcomings he mentions, but there isn't anything in his post that I disagree with. I've used Firefox exclusively for a number of years, and while there are definitely things about it that shit me, I can't see myself using any other browser any time soon. Gruber mentions the reason himself.
Perhaps the biggest difference between Safari and ...
[read more]
Therefore I recommend not including the meta tag, or, if you are forced to include it, making sure it says "IE=7", even once IE8 ships. This seems to me to be the best way to show your support for an open, interoperable Web on the long term.
IE8 now renders the “Acid2 Face” correctly in IE8 standards mode.
Performance improvements such as: better data reliability for user profiles, architectural improvements to speed up page rendering, over 330 memory leak fixes, a new XPCOM cycle collector to reduce entire classes of leaks, and reductions in the memory footprint.
[read more]
To get a better future, not only do we need a return to “the browser wars”, we need to applaud and use the hell out of “non-standard” features until such time as there’s a standard to cover equivalent functionality. Non-standard features are the future, and suggesting that they are somehow “bad” is to work against your own self-interest.