News for hackers. Stuff that matters.

A comment on Why Concurrency Is Hard. Parent comment

Re:Why Concurrency Is Hard by lloeki on Tuesday November 10, 2020 @05:58AM (#25044595)
> "do it as simply as possible, don't break certain rules, don't try to be too clever,"

This has to be a universal rule of programming. It's equally true for Ruby and Perl, which are extremely effective languages, but devolve quickly because of their uncanny ability to power cleverness. It's the whole premise of Go, by being boring by design.

Complex is easy, simple is hard, but it seems mostly because we fail to be able to resist the allure of cleverness.

[ Parent | on HN ]
Re:Why Concurrency Is Hard by roryrjb on Tuesday November 10, 2020 @06:54AM (#25044946)
I will argue that Go's concurrency model is fundamentally flawed[0] precisely because its underlying mechanism is hidden from the user. If it wasn't for this model I would be using Go instead of C and probably instead of a lot of other alternatives.

Yes Go the language is boring and I like this idea, but the runtime is a black box, that I don't like so much.

[0]. For example: https://github.com/golang/go/issues/14592.

[ Parent | on HN ]
Re:Why Concurrency Is Hard by ampdepolymerase on Tuesday November 10, 2020 @01:04PM (#25048943)
Managed concurrency like Node.js and Go are fundamentally different from Rust and C/C++'s minimal runtime concurrency.
[ Parent | on HN ]