My take: If browser makers commonly use the same rendering engine it doesn’t really matter. Everyone could pour there efforts into making the best engine possible instead of both webkit and gecko.
Of course I think Webkit should be that common rendering engine.
Knowing this will never happen, all browsers should just embrace standards, and the standards should be quick to advance, then it really doesn’t matter all that much.
(via Google, Apple, and Firefox)
Matt Asay argues that Apple and Google should abandon WebKit, Safari, and Chrome, and instead get behind Firefox:
For this same reason, however, both would do better to invest in Firefox, the “Linux of browsers.” In some ways, the browser efforts of Apple and Google are much like the Unix efforts of IBM, Hewlett-Packard, and Sun Microsystems: they threaten to splinter the browser counterattack on Microsoft rather than solidify it.
This would be reasonable advice if Apple and Google were in the browser racket primarily to “attack IE”. But they aren’t. They’re simply in it to make as good a browser as they can, to suit their own needs. For Apple, that means top-notch native browsers for the Mac and iPhone (and who knows what other future devices). For Google, that means a top-notch runtime environment for their own web applications.
