3 ms·
Exactly. Because the recorded history shows those constructs are nearly impossible to use correctly.
by felixgallo 8y ago
Exactly. Because the recorded history shows those constructs are nearly impossible to use correctly.
- Animats 8y agoYes. Having spent too much time debugging code by people who thought they were clever enough not to need language safety, I want language-level protection. (Did the Python crowd ever fix the race condition in CPickle?[1] They were in denial about this about eight years ago when I reported it. Doing multiple CPickle operations in separate threads can crash CPython. If you search for "CPickle thread crash" you find many reports of hard to reproduce problems in that area.) [1] https://bugs.python.org/issue23655 https://bugs.python.org/issue23655
- int_19h 8y agoI don't see a denial in that bug report - they're just saying that they don't have an actionable repro, and don't know how to get one.
- pizlonator 8y agoFalse. Lots of software uses pthreads and its direct wrappers. Correctly? What does anyone ever do correctly in software? Does anyone write GUIs correctly? Does anyone do databases correctly? Proving even simple software correct is an enormous endeavor that most pragmatic programmers simply never have the luxury to do. So proclaiming that threads are bad because nobody does them “correctly” is setting an arbitrarily high standard. Or maybe you just don’t know what that word means.
- felixgallo 8y agoAre you saying that buggy software is good because it’s widespread, and then trying to ad hominem me? Because that’s adorable both ways.