On Fri, Jul 4, 2014 at 3:25 PM, Domenic Denicola < domenic@domenicdenicola.com> wrote: > Rick, Chromium has a multi-process architecture, whereas Firefox in > general keeps most things in a single process. Thus Firefox has the ability > to implement many more things synchronously than Chromium does. > Implementation experience based on a single vendor > There are two implementations. Firefox and Tizen. > is not terribly valuable in guiding API surface, especially in questions > of sync vs. async, and especially when that vendor is Firefox (the only > single-process modern browser, from what I understand). > Battery status, especially a consolidated "virtual" status, doesn't change depending on number of processes used by an application. Rick
Received on Friday, 4 July 2014 21:13:40 UTC