(I am not in favor of this feature but not strongly opposed neither but..) I think a similar analogy is:
$ make -jX #where X is the number of physically available cores. If I am working/browsing/text editing, etc and building say WebKit in the background, I really do not set X to actually number of cores. When I do, it actually slows my whole system. On Wed, May 7, 2014 at 5:47 PM, Oliver Hunt <oli...@apple.com> wrote: > > On May 7, 2014, at 2:41 PM, Rik Cabanier <caban...@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. > > --Oliver > > > _______________________________________________ > > webkit-dev mailing list > > webkit-dev@lists.webkit.org > > https://lists.webkit.org/mailman/listinfo/webkit-dev > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
