"There have been mutterings about taking the chromium network stack wholesale (replacing necko, basically). This may or may not be the fastest path to success: it really depends on how hard it is to map the APIs together and how much we're willing to change callers versus re-implementing the XPCOM API on top of the chromium stack....needs discussion and a decision within a month or so. If we take chromium networking, we should probably do it on Mozilla-central in parallel with phase I, says a .

Mozilla's problem is that its main rivals , and Google's Chrome, are ahead of it in the multi-threading stakes, both of which implemented tab threading. As some developers have pointed out, this architecture can, in certain circumstances, be less efficient when working on less capable processors. Quad core processors, for instance, will be the exception rather than the rule for at least another year.