Ready, Fire, Aim
Apple released Safari, their new web browser from the same ancestral code as Konqueror, today, and many people are reviewing it already. I don’t use OS X often, so I’m not likely to use Safari often, but even during my occasional bouts of insanity when I boot into OS X, I’ll be looking elsewhere for my browsing goodness, because of one absolutely critical feature that my preferred browser has that Safari doesn’t: the ability to set cookies to expire when the browser is quit. I loathe cookies. I don’t like being tracked. But control-freak site developers will often make sites that are impossible to use without them. Mozilla and Opera cater to paranoid people like me by allowing me to accept their cookies, then trash them at the end of the session. This feature alone would keep me from adopting Safari.
I guess now I’ll have to work on whatever it is that causes Konqueror (and Safari) to choke on my genealogy weblog (written in valid XHTML, so it should render fine like it does everywhere else) now, since market share for this buggy renderer just jumped significantly. Bleah.
Posted at 7:06 PM
Hey, thanks for the ping :).
I’m hoping the opposite will happen - Apple will realise that a good proportion of perfectly good pages don’t render in the browser (which of course undermines its claims of being standards-compliant), and make some effort to get the pages to render.
After all, major sites like Wired and ezBoard are now moving to XHTML/CSS, and I imagine this could be the start of a trend. If these sites won’t render then I don’t think people will use it. At least, I hope they won’t, though I can’t imagine that many people use IE out of choice either.
Posted by Neil T. at 5:59 AM, January 8, 2003 [Link]