3 ms·
> We've had ways of doing multithreaded code that are easier to reason about for decades. They really do work quite well. Why people doggedly insist on pretendi
by Izkata 8y ago
> We've had ways of doing multithreaded code that are easier to reason about for decades. They really do work quite well. Why people doggedly insist on pretending they don't exist is a perennial mystery to me.
Not a single one was mentioned during my CS undergrad; shared-memory threads were, many times. I think simple ignorance is the answer.
- bunderbunder 8y agoI think a simple love of complexity is also part of it. It's fun to do things that make you feel clever. One experience I've had more often than I'd care to admit is diving into a multithreaded module with the intent of fixing a race condition bug, and finding that I could simultaneously remove the bug and realize a healthy performance improvement by making it single-threaded. Which, for that matter, is another reason to be wary of mutexes and shared mutable data: Memory barriers do really impolite things to pipelines and caches in a modern CPU.
- siscia 8y agoI don't believe this holds. We are suppose to be engineers, we need to do our research on design and methodologies before to code. And even if we really don't find simpler solutions, there is supposed to be a more senior engineer check our code and provide feedback. Ignorance should not be an excuse...