at least the dark don’t hide it — roblord.org : Chrome vs Chromeless

Fri, 20 Feb 2009 08:47:28 +0000

One of the reasons that so-called site specific browsers are attractive is that they run in a separate process from your main browser. This means you get to use both the cores in your cpu - one for Firefox and one for your SSB. Chrome's inherently multi-process architecture is designed for the modern computers of the past couple of years and foreseeable future which are increasingly parallel. Chrome's lack of features is disruptive. It rejects the conventional flawed model of software development that we've seen coming out of Redmond and Cupertino for thirty years - adding features to sell the new version. Chrome isn't trying to sell itself because it isn't the feature - the web is the feature. People want to interact with web pages and chrome is just there to let them do that. In Unix XWindows terms Chrome is just the window manager for your web applications. Also, by all accounts the Chromium project is actually welcoming to non-employee contributors. That's refreshing. The WebKit side of the fence seems to be doing a better job of that these days than the other guys. Ian PS: I used to believe that evolving and extending the web browser user experience was the right way to go. Now I think we just need to burn it down and throw it away. Make every feature, every button, every pixel justify itself, fight for its right to exist.

ianloic's Comments

at least the dark don’t hide it — roblord.org : Chrome vs Chromeless