4 ms·
I write Go daily, and I don't think CSP really panned out. For most applications, I find it's much easier to use a mutex and standard threading tooling than cha
by throwaway894345 7y ago
I write Go daily, and I don't think CSP really panned out. For most applications, I find it's much easier to use a mutex and standard threading tooling than channels/CSP. That might be an artifact of how channels are implemented and their many hidden error cases--perhaps a better channel implementation could change the calculus. There are lots of reasons to prefer Go to Rust IMO, but I don't think CSP is among them.
- dnautics 7y ago> For most applications, I find it's much easier to use a mutex and standard threading tooling than channels/CSP It's easier to write code with standard threading tooling but I think CSP is much, much easier to debug and avoid deadlocks.
- throwaway894345 7y agoThat has not been my experience with CSP via Go channels after 8 years of solid use (I still use channels here and there, but not in a CSP pattern). Different strokes, I suppose.
- morelisp 7y ago> I think CSP is much, much easier to debug and avoid deadlocks. This has (still to my surprise) not borne out in real-world cases, at least to the extent Go channels "do CSP". https://blog.acolyer.org/2019/05/17/understanding-real-world-concurrency-bugs-in-go/ https://blog.acolyer.org/2019/05/17/understanding-real-world...