> https://stackoverflow.com/questions/55273965/how-to-know-if-...
Q&A's like this have contributed to me avoiding Go.
Q&A's like this have contributed to me avoiding Go.
Goroutines are purely managed by the Go runtime in userspace. They never ‘just disappear’.
I can't speak to the accuracy. I didn't imply that the answers somehow affect my opinion of Go, but both the questions AND accepted answers.
Somehow Go managed to release with a fork that was worse than PHP's first stab, and that's impressively incompetent. Goroutines are the same as js promises without the native state management...and the detachment of declaration and startup? Jesus that's prone to abuse/bugs. Coroutines are a horrific display of the base language on their own. Yes you can create a custom/library wrapper, but that's a leaky abstraction, at best.
There are things to be admired about Go's choices, as a language, but there is enough to deride that I avoid bothering to even toy with it.