Structured Concurrency 0 ▲ Stefan VanBuren · All Content 84 days ago · Tech · hide · Fediverse post Every time you write the statement go in a program, you should consider the question of how, and under what conditions, the goroutine you are about to start, will end. Never start a goroutine without knowing how it will stop So that’s the history of goto. Now, how much of this applies to go statements? Well… basically, all of it! The analogy turns out to be shockingly exact. Notes on structured concurrency, or: Go statement considered harmful In Go, an unstructured go is almost always an anti-pattern. Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town