I used to be the lead dev at flock - I've not worked there for almost 2 years now, but I talk to several of the developers regularly. I don't know what their b

I used to be the lead dev at flock - I've not worked there for almost 2 years now, but I talk to several of the developers regularly. I don't know what their business plans are but: Most of the code isn't UI, it is JS. JS which is portable to other browsers and which would benefit from not running in a single thread. The IPC model of Chrome is much nicer for extension development. Porting many of the components is not as hard as you would think. Next, some of the GUI is XUL, some of it is HTML. Converting between XUL and HTML isn't as hard as you would think. The box models are different, but both use CSS for style. I have several extensions and had to convert between XUL and HTML and back when I cannot figure out how to override browser.js stuff. Not that big of a deal. There is a degree of "version 2, lets rebuild the whole thing," but I don't think they are going to change on the drop of the hat. Their open SVN repository shows that even while they have been working on new releases of the firefox based browser, they have been doing experiments with chrome to figure out how it would work. Their VP of E before building Flock lead the team that build Netscape 8/9 (it was outsourced), and I have faith that if he changes to Chromium it is because it is the smart thing to do.