Perhaps... But, if firefox is multithreaded, it's a very very sorry implementation. It sticks to one core like glue. I can watch a 20 tab firefox session not even bump the other 7 cores on my system at all. Yes, chrome tosses in the "multiprocessing" (coarse, versus fine grained multithreading), but it works like a charm; KUDOS of you to notice and correctly identify the difference
as so many people do not. I'm personally a "net head" (design HUGE network infrastructure) but spent two decades in both modest (20 processor?) and large massive parallel (think supercomputer) systems architecture, and would give the team an "D-" for results. The 64 bit model not being out (25 years after I started on 64 bit systems) in general (not nightly builds...) says a lot about a broken software development program (e.g. Agile!!)
Side by side, chrome handles 50+ (til I can't read the names on tabs!
) open tabs fine, while firefox is unbearable before I hit 20 tabs. I'm guessing much of the framework is utilized in their other products, and it shows....
I do admit, my use of tbird is extreme, but 15 years of email (my sent folder ~40k items? numerous list folders > 500k items) is tough on any client. It does work, but frequently gives up. Lasts longer than many other clients though
It is fun when a client from a decade ago calls and asks about an architecture/design/process document I produced for them (and they didn't follow, bad outcome as a result) and I'm able to find it in 30 seconds!).
Thanks though. Fun stuff all around!!!!