Honza Bambas schrieb:
Few reasons: - I really don't believe we will soon/ever have a good OOP Firefox implementation
AFAIK, the major reason why we did abandon doing that was because moving all our interaction with the content to be async was too much work for the moment. Isn't that same work required for what you propose?
If so, I don't see why we should go for that instead of taking another shot at moving content to a separate process - after all, we're using that process separation code in B2G quite heavily as well, so it's not that code itself that is problematic, it's making Firefox work well with the parallelization it brings.
Robert Kaiser _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
