3 ms·
Chrome was designed with multi-core processors in mind. Firefox wasn't, since obviously multi-core processors weren't really a thing when Firefox was initially
by Sylos 10y ago
Chrome was designed with multi-core processors in mind. Firefox wasn't, since obviously multi-core processors weren't really a thing when Firefox was initially released. As a result, Mozilla had to tear up a big chunk of the architecture to implement it. That's why it took so long. A simple case of technical debt.
- c0nducktr 10y agoAnd they also didn't work on it for the entire six years since Chrome was released. The project was shelved temporarily while development was focused on other things. I have been running Firefox Nightly along side Chrome for the past year or so, and have been using it as my main browser for a few months now, and I've been really happy with its performance.
- gcp 10y agoNot only tear up the architecture, but also accept that a major competitive advantage (the add-on ecosystem) would be for some part collateral damage in the transition.