3 ms·
"Process-based concurrency is relatively simple (especially if your programming language has good async support)" You can have "process-based concurrency... si
by jerf 11y ago
"Process-based concurrency is relatively simple (especially if your programming language has good async support)"
You can have "process-based concurrency... simple" or "good async support" but you can't have both... good async support becomes not simple. "Good async support" in a single process just means you pretty much have virtual threads anyhow, you just don't formally label them. That's why all the "good async" languages are basically structuring all their "good async" support so that you can write code that looks and behaves... virtually exactly like threads.
The problem with threads isn't the threads... it's the sharing patterns. Lots of nested locks is insane. But that's not the only way to do it. Even in Go it isn't that hard to do things sanely, and things like Erlang and Rust make it even easier.
If you've still only used those languages with "good async support", you really ought to try one of the modern languages that are the real competition. I have not heard very many people become fluent in one of those and then want to go back.
- sportanova 11y agowhat are the modern languages that are the real competition?
- woah 11y agoWondering what your opinion on JavaScript's async support is? Huge amounts of flawlessly async single threaded code have been written in js.