4 ms·
real killer and root cause is that Chromium is well suited to being embedded, and Gecko is not. I don't think that's really the key problem since you don't hav
by pvg 5y ago
real killer and root cause is that Chromium is well suited to being embedded, and Gecko is not.
I don't think that's really the key problem since you don't have to build a new browser out of FF by embedding Gecko. FF itself is a browser that was made out of another browser, much of the old core Mozilla technology is basically a cross-platform app-building framework with one of the 'apps' being a browser. Somewhat unobviously, this turned out not to be a great way to build a browser in the long run.
- toyg 5y ago> Somewhat unobviously, this turned out not to be a great way to build a browser It's actually great in the amount of flexibility and access it gives to 3rd-party developers to customize the browser itself. Unfortunately, the price seems to be complexity and rigidity in some critical areas (performance, embeddability).