By: Michael S (already5chosen.delete@this.yahoo.com), May 13, 2013 1:13 am
Room: Moderated Discussions
Gabriele Svelto (gabriele.svelto.delete@this.gmail.com) on May 13, 2013 12:53 am wrote:
> Doug S (foo.delete@this.bar.bar) on May 12, 2013 8:22 pm wrote:
> > You still need to be actually doing something that maxes out your four real cores while still needing
> > more resources. On a phone. I'm talking a real world task that would be done more than a fraction of
> > the userbase, so no talk about a couple games that can theoretically be a tiny bit faster with 4C/8T
> > versus 4C, or people running a browser with >4 tabs in a process-per-tab model where even the inactive
> > ones are maxing out the CPU (Flash could do this, but luckily that abomination is rapidly dying)
>
> Modern JavaScript code can be every bit as bad as Flash if misused.
Exactly.
> Nowadays you can even spawn multiple threads from a single page:
>
> https://developer.mozilla.org/en-US/docs/DOM/Using_web_workers
> Doug S (foo.delete@this.bar.bar) on May 12, 2013 8:22 pm wrote:
> > You still need to be actually doing something that maxes out your four real cores while still needing
> > more resources. On a phone. I'm talking a real world task that would be done more than a fraction of
> > the userbase, so no talk about a couple games that can theoretically be a tiny bit faster with 4C/8T
> > versus 4C, or people running a browser with >4 tabs in a process-per-tab model where even the inactive
> > ones are maxing out the CPU (Flash could do this, but luckily that abomination is rapidly dying)
>
> Modern JavaScript code can be every bit as bad as Flash if misused.
Exactly.
> Nowadays you can even spawn multiple threads from a single page:
>
> https://developer.mozilla.org/en-US/docs/DOM/Using_web_workers