Hacker News Reader

>it just 99% of programmers wouldn't know what to do with more cores

Fixed that for you. Remember that every time you experience an unresponsive GUI anywhere, and that's the easy case.

Beyond that, parallelization is generally not easy.

I think the vast majority of the time unresponsive GUI are because of blocking network or IO calls. A faster CPU won't do anything. I rarely max out my CPU.

A UI shouldn't be unresponsive in that case. It should present a progress bar, or other visual indicator that the UI [thread/actor/process] is waiting for the IO [thread/actor/process]. A UI should only become unresponsive when only one [thread/actor/process] is trying to do everything (I.e. both IO and UI), which should only occur if your application is not written with concurrency in mind.

Reply on news.ycombinator.com