Go's approach to concurrency exposes Go's lack of memory safety. When you couple this with a (mostly) bunch of noob devs who have been told Go is super safe be

Go's approach to concurrency exposes Go's lack of memory safety. When you couple this with a (mostly) bunch of noob devs who have been told Go is super safe because of it's type safety, you have a recipe for disaster. The combination of language features and surrounding social effects means, once you pursue concurrency, Go abruptly becomes one of the most dangerous languages to use for any industry where subtle errors of value are a problem ... like anything to do with money. p.s. No slight intended to Elixir, it avoids all these risks.