4 ms·
> Look up communicating sequential processes and never have a problem with multi-threading again. Go does that yet still need mutexes, has race conditions and
by camus2 10y ago
> Look up communicating sequential processes and never have a problem with multi-threading again.
Go does that yet still need mutexes, has race conditions and memory corruption.
- cel1ne 10y ago"never have a problem with multi-threading again" was not meant literally. Rather that grasping the concept of "sharing data by communicating" helps you structure your programs.