[BGCOLOR=transparent]I found that C is pretty awkward (and more importantly, unsafe) when it comes to writing parallel code.[/BGCOLOR]
[BGCOLOR=transparent][/BGCOLOR]
C and C++ do not naturally have a way to express parallelism, nor to express locking to force serialization where parallelism is harmful. It is very easy to add locking to C/C++ code, and there is more than one way to do it. But all these ways require care and discipline, and good training of all software developers.
[BGCOLOR=transparent]At least with the popularity of C we have a shed-load of debugging tools for parallel code.[/BGCOLOR]
[BGCOLOR=transparent][/BGCOLOR]
Similar things exist for other languages too, definitely Java and Python. A while ago (perhaps a year), a Python program I had written for fun at home (roughly 12KLOC) kept deadlocking on me. Which is embarrassing, because I do this kind of stuff professionally, so stupid mistakes like that shouldn't happen. So I looked around a bit, and within half an hour I had tracing, debugging and deadlock detection tools downloaded, and the problem found. It was really dumb; that's what happens when you think a problem is easy and you write code for it in the evening after dinner.
... [BGCOLOR=transparent]Isn't that a garbage collected Java JVM frontend? I cannot see how that can map to hardware any better.[/BGCOLOR]
[BGCOLOR=transparent][/BGCOLOR]
Having a programming language that exactly exposes the hardware does not imply that it is the only efficient way of using the hardware. Expressing your program in a higher-level language (in the style of the bytecode that go into a JVM) can actually give the execution engine more semantic hints for running it efficiently, by mapping larger concepts onto the facilities that the hardware happens to provide, without each engineer having to deal with the low-level stuff all the time.
[BGCOLOR=transparent]Sure, it might apparently make dealing with lots of threads pretty easy but interacting with the hardware (i.e for an OS) is not entirely possible in pure JVM (thats why JVM was itself written in C/C++).[/BGCOLOR]
[BGCOLOR=transparent][/BGCOLOR]
[BGCOLOR=transparent]In the late 90s and early 00s we had various Java CPU and Java OS, which all executed Java natively. That turned out to be a really dumb idea, and a great waste of money. But amusing.[/BGCOLOR]
[BGCOLOR=transparent]Perhaps if we cannot correctly "wrangle" parallel programming, we should give up and look for another way to make processors faster. Perhaps this whole parallel thing is Intel's design plateauing.[/BGCOLOR]
[BGCOLOR=transparent][/BGCOLOR]
[BGCOLOR=transparent]Sadly, given the unfortunate real-world limitations of chip design and power consumption, CPUs will get more massively parallel as time goes on: more cores, more parallel execution within cores. Right now, I don't see a way out of that. This means that we all need to get better at efficiently and correctly expressing our programs in a way that can be executed on the hardware we'll have.[/BGCOLOR]
