Re:A future for fork(2)
by pcwalton on Friday October 05, 2018 @02:22PM
(#18150456)
It may be "the root of all evil", but often there's no faster way to solve the problem. We need to accept that shared mutable state is sometimes necessary and work on how to tame it to be maintainable and usable.
[ Parent
| on HN ]
Re:A future for fork(2)
by a1369209993 on Saturday October 06, 2018 @02:28AM
(#18153838)
Shared mutable state is like goto; yes, it is sometimes necessary, but that only happens when there's a deficiency in your language's concurrency primitives.