In what must be the fastest, most in-depth, distributed product review in history, Apple’s new browser, Safari is being bashed about all over the blogosphere. Last night I was less than overwhelmed, but this morning I’m a little more happy. [Ben Hammersley]
Ben is spot on. Based on the mob’s commentary (posts by Terrie Miller, Mark Pilgrim and myself provide numerous starting points) it would seem that tabbed browsing has been voted as the leading must-have missing feature from the new browser.
Equally as noteworthy is the distributed conversation regarding Apple’s selection of an HTML rending engine and the mass debugging of its standards compliance.
Apple’s use of the Konqueror/KHTML engine as opposed to Mozilla Gecko is a bit controversial (or more accurately intruiging), but in the long run will be beneficial to the space. Instead of one open source engine, developers will have more choice and the inheritent flexibility that two different efforts provide. (More specifically, these engines are likely to be essential in providing the basis to next generation Internet-aware microcontent applications.) There is some valid concern that another engine will divide the efforts of the community and introduce additional quirks and standards incompatabilites for designers concerned with universal access to work around. With Apple’s support and dedication, I’m optimistic that those issues will be surmounted — take David Hyatt and quick and open response to the community’s feedback.
Once again the network effects of the Internet delivers.
What are your thoughts on Safarai and its use of Konqueror instead of Gecko?