Hacker News new | ask | show | jobs
by AIMunchkin 3411 days ago
Well, why don't you learn a concurrent language like Go, CUDA, or OpenCL and do something about that?

From my vantage point, I remain amazed that people have fled concurrent programming in an age where the hardware for doing so has not only thrived, but which may also be the only path forward from here.

3 comments

I write plenty of multithreaded code of my own. What I am grieving is our CS education teaching new programmers that they should avoid concurrency because it's "too hard." I don't have time to make Thunderbird use more CPU cores so that its user interface doesn't block at times.
That never happened to me and my machine is nearly ten years old. You must be a really heavy Thunderbird user.
Go isn't comparable to CUDA or OpenCL in terms of parallelism, which is what matters here. Go doesn't even have SIMD available without writing assembly.
I write multi threaded code, but many of the tools I use are not multi threaded.