> Most of the things that go into squandering CPU don't parallelize well That's not true. We just aren't trying very hard to parallelize our code. I work on pa

> Most of the things that go into squandering CPU don't parallelize well That's not true. We just aren't trying very hard to parallelize our code. I work on parallelizing browsers and there's a lot that can be done. For example, libpng leaves 2x potential performance on the table by not pipelining the Huffman decode with the defiltering. That said, I do agree that a better use of our time in most cases would be to improve the sequential performance of our software, because usually you shouldn't start parallelizing until you've exhausted the potential sequential improvements.