Re:Asynchronous programming and cooperative multitasking
by greglindahl on Sunday February 10, 2019 @01:45PM
(#19129284)
I've learned (the hard way) that any in any project with more than one programmer, sometimes you don't have control over what the others are doing.
And on a bad day, I can do "the bad thing" to myself.
One way to help mitigate this is good tooling. A warning that a piece of async computation took longer than expected can be very useful if you expect everything to finish in a few tens of milliseconds.
It also have the benefit of making concurrent access much easier to reason about without having to resort to message passing or immutability, yet locks are rarely necessary.
As usual, it's a trade off.