To you and zemo's point, those are specific instantiations of the general point I'm making. I'm sure Go will get there, as long as it stays alive, but it shouldn't be a surprise that Erlang is more polished at the moment. That's not a criticism of Go per se, it's just an effect of where they are in their lifespans. Erlang is basically mature and just polishing, and Go's still a rambunctious early teen with a wide-open future.
I agree with this, however I'm specifically pointing out that this is not about polish of Go in general sense -- while there's a lot things to improve in the compiler, etc., in this instance, there's something wrong somewhere, perhaps in websockets library. It doesn't mean that there's something wrong with Go per se. Note that websockets is not included in the standard library yet.
