Re:Ask HN: Why is concurrent programming so hard ?
by ErrantX on Monday August 17, 2009 @11:01AM
(#768229)
> So we tend to 'break up' our programs into sequential pieces of code, each running in parallel with the rest, and the spots where they meet, like trains using a railroad track, have to be scheduled to make things execute in the proper sequence.
Dead on. We've been working on single threads for SO long and then just adapted that onto multi-threaded architecture now that we have to scale outwards.
I spent the last year of university writing a research project (final year project) trying to come up with a viable form of concurrent programming that didnt just look like a fancy way to multi thread.
But no luck :D
The best I can think of is to create some rock solid standard and an underlying architecture. With the idea being you can write your basic code and the compiler, vm, interpreter does the parallel work for you. But that's basically the same thing and not really solving the problem :)
Dead on. We've been working on single threads for SO long and then just adapted that onto multi-threaded architecture now that we have to scale outwards.
I spent the last year of university writing a research project (final year project) trying to come up with a viable form of concurrent programming that didnt just look like a fancy way to multi thread.
But no luck :D
The best I can think of is to create some rock solid standard and an underlying architecture. With the idea being you can write your basic code and the compiler, vm, interpreter does the parallel work for you. But that's basically the same thing and not really solving the problem :)