> Javascript benchmarks could test multithreading via Web Workers but for whatever reasons they don't seem to.
Well, like I said, JavaScript has a long history and therefore a predilection for single-threading. Yes, you could write tests that exercise Web Workers, but Web Workers are still infrequently used in the wild, let alone in benchmarking suites. I've used Web Workers in a few projects and I'm underwhelmed by their current features. I can't really blame the JavaScript community at large for not using them much yet.
The DOM and other elements of browsers also have single-threaded assumptions or behaviors.
More multi-threaded capability is a first step, and then we'll need to take advantage of that capability.
Well, like I said, JavaScript has a long history and therefore a predilection for single-threading. Yes, you could write tests that exercise Web Workers, but Web Workers are still infrequently used in the wild, let alone in benchmarking suites. I've used Web Workers in a few projects and I'm underwhelmed by their current features. I can't really blame the JavaScript community at large for not using them much yet.
The DOM and other elements of browsers also have single-threaded assumptions or behaviors.
More multi-threaded capability is a first step, and then we'll need to take advantage of that capability.