> > Do you think it would be feasible that the browser fires events every time > > the number of cores available for a job changes? That might allow to build > > an efficient event-based worker pool. > > I think this will be very noisy and might cause a lot of confusion. > Also I'm unsure how we could even implement this since the operating > systems don't give us such information.
> > In the meantime, there are developers out there who are downloading > > micro-benchmarks on every client to stress-test the browser and determine > > the number of physical core. This is nonsense, we can all agree, but unless > > you give them a short-term alternative, they'll keep doing exactly that. > > And "native" will keep looking a lot more usable than the web. > > I agree. > Do you have pointers where people are describing this? I'm about to add a worker pool to Prototypo[1] and I'll have to use this script. Today it provides the most reliable source of info on how many jobs I can run concurrently. And it saddens me. [1] http://www.prototypo.io _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
