3 ms·
My two cents for mozilla, and im sure they will be sort of offended by this, but the best strategy, one that should be pursuit years ago, is to get the chrome e
by oscargrouch 12y ago
My two cents for mozilla, and im sure they will be sort of offended by this, but the best strategy, one that should be pursuit years ago, is to get the chrome engine, and replace the webkit/blink layer with the mozilla web rendering engine..
That way, they would have the multi-process architecture, they need badly, but with their core, the web layer intact..
The chrome architecture is good enough, that you can replace the webkit layer without mess with other core parts
Dont know why they are procrastinating with servo instead, and doing the same mistakes netscape did years ago, to rewrite the whole engine, while IE was capable to take the lead in the browser wars back than.. the same mistake!!
Theres a good Joel Spolsky article about this (from 2000):
Things You Should Never Do [http://www.joelonsoftware.com/articles/fog0000000069.html http://www.joelonsoftware.com/articles/fog0000000069.html]
- kryptiskt 12y agoThey have multiprocess in the nightlies (https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis), but it is only used in FirefoxOS releases currently.
- doublec 12y agoIf you have a nightly desktop build you should see a "New E10s Window" in the menu. This starts up a multiprocess browser window allowing you to test the feature.
- doublec 12y agoServo is a research project exploring the design space of writing a modern browser from the ground up in a language designed for it. It's not being developed as a Gecko (Firefox internal framework) replacement. So I don't think they are making the mistake of restarting from scratch for their core product. The Servo project is done by a different team and Gecko development continues uninterrupted. No procrastination in that area is going on.