If you want to see some of the most complex multithreading systems, take a look inside modern browsers. That's what he means by "browser scale".
I have some knowledge into working with Chromium's internals, and it is crazy what's going on inside there. Several different job and message queue systems interlocking with each other, tasks spread across multiple processes getting split and regrouped and synced and recombined, practically everything running async, just so a few pixels are rendered a little faster when your multicore machine updates a small section of a website.
Browsers are indeed idling a lot, but if you want them to do something, they must be as crazy fast as possible. The competition in that space is ridiculous.
I have some knowledge into working with Chromium's internals, and it is crazy what's going on inside there. Several different job and message queue systems interlocking with each other, tasks spread across multiple processes getting split and regrouped and synced and recombined, practically everything running async, just so a few pixels are rendered a little faster when your multicore machine updates a small section of a website.
Browsers are indeed idling a lot, but if you want them to do something, they must be as crazy fast as possible. The competition in that space is ridiculous.