[webkit-dev] support for navigator.cores or navigator.hardwareConcurrency
cabanier at gmail.com
Wed May 7 15:20:50 PDT 2014
On Wed, May 7, 2014 at 2:57 PM, Benjamin Poulain <benjamin at webkit.org>wrote:
> On 5/7/14, 2:47 PM, Oliver Hunt wrote:
>> On May 7, 2014, at 2:41 PM, Rik Cabanier <cabanier at gmail.com> wrote:
>>> When would I as a user, not want a page or web application to be as fast
>>> as possible? Has a user ever complained about a desktop app that uses too
>>> many of his CPU's? I think Oliver's point was that other processes might
>>> fight for the same CPU resources but that is not unexpected for users.
>> What happen if i go to your website while i'm doing something else in the
>> background? What if i'm playing a game while waiting for my machine to do
>> something else? What if your page is in the background? Or my battery is
>> running low.
>> You need to stop thinking in terms of a user wanting only one thing to
>> happen at a time.
> And there are actually many bug reports about native apps using too much
> CPU when the user is not expecting it (simple tasks and/or the process is
> not frontmost).
If a simple task is using a lot of CPU, that is a bug and users will move
to an application that is more efficient. If my calendar were to drain my
battery, I would switch to a calendar app that doesn't do that.
As for background tasks making foreground tasks slow, this is something
that could be handled by the operating system/browser process (ie
Most users would expect that if one tab mines bitcoins, the tab that runs a
game would be slower.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev