The idea that a feature isn't that slow if you don't use it much isn't very persuasive.
You could also flip this argument on its head. What is go good at? Writing evented servers. If you're writing one of these you'll know it.
Also, I admit I was wrong; go doesn't have uniquely bad ffi. It's just worse than C++, rust, D, jvm, .net, and any compiler lisp I've ever used. Perhaps go is uniquely well suited to writing stuff other than evented servers in way I just can't see yet.
(And FWIW I am still baffled how python managed to be this slow without needing to switch stacks.)
You could also flip this argument on its head. What is go good at? Writing evented servers. If you're writing one of these you'll know it.
Also, I admit I was wrong; go doesn't have uniquely bad ffi. It's just worse than C++, rust, D, jvm, .net, and any compiler lisp I've ever used. Perhaps go is uniquely well suited to writing stuff other than evented servers in way I just can't see yet.
(And FWIW I am still baffled how python managed to be this slow without needing to switch stacks.)