This is something I always wanted to implement within Voyager but it was too difficult because of GUI issues (the toolkit used was a mess to use from threads). As far as I know, the first browser implementing rendering in its own process was Internet Explorer but when they implemented tabs, they left that out. Apparently they fixed that in IE 8. The advantage to such a design is that the main GUI isn’t locked anymore when rendering CPU hungry website, and you can even switch to other tabs meanwhile. It is tricky to implement such design and I noticed some refresh problems in Chrome when writing in TEXTAREA fields for example. Scrolling speed can also become slow because the refresh is asynchronous then. But overall this is a very good idea.
The tabs drag & drop, search in the address bar (without search words being recognized as URLs or other nonsense), uncluttered GUI, automatic fullscreen mode, URL completion that actually works, all plugins working without hassle.
Not a single crash as of yet. Perfectly usable as a main browser.
So there, Chrome is now my default browser. I was getting fed up with Firefox’ bloat and MSIE had too many annoyances. Nice job Google. Chrome is how I always wanted to make Voyager like. Now good luck fixing all the quirks 🙂
Author: David Gerber
CEO of Zapek Software Engineering