> Around this time, Mozilla started paying serious attention to Chrome. Chrome had started with very different design guidelines than Firefox:
> * at the time, Chrome didn’t care about eating too much memory or system resources;
> * Chrome used many processes, which gave this browser heightened security and responsiveness by design;
> * Chrome had started without an add-on API, which meant that Chrome developers could get away with refactoring anything they wanted, without this development tax; as Chrome introduced their extension mechanism, they did it with a proper API, which could usually be maintained regardless of changes to the back-end;
Was it possible to do this inside Mozilla? Release a new browser with different branding that does not have these handicaps. Then, let the marketplace decide which browser to pick. If it won out, announce publicly that ongoing investment would be on the new browser.