There's a single benchmark for measuring how long it takes to compile Chrome. That doesn't tell, say, the average IDE user how well it'll handle their interactive experience – it's reasonable to expect that to multithread well – or what the workload the original poster specifically mentioned will be like. Many web developers have e.g databases, redis, CSS/JS compilers, etc. running (directly, in Docker, etc.) in addition to the app, and many of those bottleneck on single-threaded performance, and so it's quite reasonable to ask whether that kind of workload benefits from the extra parallelism which is the main selling point for this processor design.