I agree. Just answering the question in the thread!

It is still important in compilation. That means it affect developers work many many times per day.

Compiling has generally been easier to parallelize I thought? Using make -j<whatever> has been around for a long time. If you're only compiling one file then it's harder to get an improvement, but a single file should be quick anyway so there's not a huge need to speed it up. It's not like you're doing something silly and including boost are you?

In large projects, that are multiple dependency chains, that cannot be fully parallelized. There's a critical, often a bit long path, for which single threaded is still very important. Another thing is that various platforms like nodejs, etc. may not be able to utilize parallelism much, adding to the ST importance.

Web browsing is still single threaded. Games still have a very busy main thread.

1 UI thread !== only 1 thread

Firefox and chrome use a half-dozen or so threads parsing and compiling JS code so it loads quickly. Firefox's Quantum work adds a lot of threads for rendering as well. In addition, service workers, web workers, and Wasm all spawn additional processes which serve the same purpose if you aren't sharing memory directly.

That said, the Phoronix Selenium tests show AMD ahead by quite a bit. (source)[https://www.phoronix.com/scan.php?page=article&item=ryzen-37...]

So Servo is just snake-oil?

Firefox's quantum work comes from their servo work, so I'd say it's been valuable.

Firefox Kraken is faster on the 3700X, for example. It'll come down more to which browser you use than the processor.

> Web browsing is still single threaded.

Only in the narrow sense that processes are not threads. See `Window > Task Manager` in Chrome.