2 ms·
I’ve always found it better to avoid concurrent mutability as much as possible. That has worked very well for me, and I don’t generally have the negative experi
by throwaway894345 6y ago
I’ve always found it better to avoid concurrent mutability as much as possible. That has worked very well for me, and I don’t generally have the negative experiences other Go programmers have complained about. Not as nice as static type system guarantees, but it’s available today.
- tapirl 6y agoIt is not always feasible. Even if sometimes it is possible, it isn't without any cost.
- throwaway894345 6y agoYeah, you’re absolutely right that there is always some situation where some amount of shared mutable state is necessary, but there’s still a lot of fat to trim in most cases.