[hallnoates]

> I don't understand your logic here. PG is talking about abstracting the problem away from the developer - you think the future of CS is that we will no longer make things abstract?!

I interpreted him as implying that writing code for parallel processing should happen in such a way that we don't have to think of it. But that is the whole problem. Developers are ignoring the complexity and opportunity that exists in understanding parallel computing. Development languages should evolve to embrace the opportunity that exists within understanding what is going on, not hide it. We didn't keep programming in BASIC since we were kids as our primary language, nor did we continue to use assembly. Things evolve, and, as developers, our thinking needs to evolve to support multiple CPUs and parallel computing; we don't need someone's help to wash over the fact that things have gotten more complex. We need to understand that complexity before attempting to abstract it.

[philwelch]

Concurrency and parallelism have been understood and abstracted for decades. There's new research to be done there for sure, but productizing what's already out there would be a massive win. We live in a world where people are still using locks and worrying about thread-safety in purportedly high-level languages.