3 ms·
Considering that chromium is an opensource project and has many contributors... if Google ever did drop Chrome it's not it'll just collect dust.
by thejosh 13y ago
Considering that chromium is an opensource project and has many contributors... if Google ever did drop Chrome it's not it'll just collect dust.
- k__ 13y agoTrue story. But FFox has made major progress the last few years :) And I would like the give Google a good reason to continuing their support of Mozilla: a userbase.
- edoloughlin 13y agoAt the risk of making a facetious comment, surely support for web standards is de facto support for Mozilla? Or do you mean monetary support?
- k__ 13y agoMonetary
- bzbarsky 13y agoThe problem with a modern web browser project is it's expensive to operate. All the ones I know of have extensive regression test suites, both correctness and performance, that get run from continuous integration systems in multiple configurations and on multiple platforms. That's not to mention the continuous fuzz testing farms looking for security bugs. I'm most familiar with the Firefox case: according to https://etherpad.mozilla.org/InfraLoadIdeas https://etherpad.mozilla.org/InfraLoadIdeas a full correctness test run across all platforms is about 120 hours of machine time. Adding performance tests raises that to 177 hours. Combined with the pace of development, that means a build+test farm of 3000+ machines (according to http://oduinn.com/blog/2013/03/27/at-mozilla-releaseengineering-release-automation-continuous-integration/ http://oduinn.com/blog/2013/03/27/at-mozilla-releaseengineer... ) and infrastructure load is still a problem. So any serious project picking up Chromium development would need financial resources to at the very least maintain basic test infrastructure...