News for hackers. Stuff that matters.

A comment on Ask HN: Why is concurrent programming so hard ?.

Re:Ask HN: Why is concurrent programming so hard ? by alexgartrell on Monday August 17, 2009 @02:03PM (#768678)
We all learned to program in a non-concurrent manner and we're trying to reuse knowledge from that. Instead, we should focus on re-learning programming, namely what it means to have side-effects and global memory and what we should use instead to operate on those things in a safe way.

Concurrent programming isn't hard, debugging concurrent programming is hard. Eliminate side effects, use Software Transactional Memory, and figure out how easy concurrent programming _can_ be.

obvious Clojure plug

[ Parent | on HN ]
Re:Ask HN: Why is concurrent programming so hard ? by andyleclair on Monday August 17, 2009 @04:10PM (#768965)
Yes. I hear many a person bitch about concurrent programming. Concurrency is hard ONLY when you have mutable state. Otherwise, you just (call/cc ...) your continuations.

I thank my lucky stars every day that I go to a school where the first thing you learn is Scheme. Thanks, Matthias!

[ Parent | on HN ]