Google Chrome: 20 processes and not counting…

When first released to public, it was touted to be a fast browser with emphasis on stability. Google Chrome is probably the first to have brought tab-process isolation to the browser market (or was it IE8? The preview got out at almost the same time). And it did live up to its name. Crashing plugin? No problem, the plugin container is killed, and browser resumes as usual. It's fast. It's stable. No cruft. Wait, this is some kind of déjà vu… wasn't Firebird like that too?

Handling Google Chrome (Chromium)'s sucky bookmark manager

Get Firefox. Register Xmarks account. Install XMarks extension on both browser. Sync on Chrome. Sync on Firefox. Edit bookmarks as you like in Firefox. Sync again, on Firefox, then on Chrome. Problem solved. Well, at least I have to do this until Chromium devs implement a better bookmarks manager.