I got that impression with go a bit. It did feel like there were a couple of things omitted from the language simply because the authors had never experienced

I got that impression with go a bit. It did feel like there were a couple of things omitted from the language simply because the authors had never experienced them done correctly. Exceptions always comes up as the big one, but the more subtle part of a concurrent system that erlang did really well was allow you to monitor processes for crash. You can abort a goroutine early, but nobody can hear about it. Of course, you can also segfault the thing using a null pointer dereference, but you can't do anything other than have your entire application fail.