I don't understand this comment, are you implying that it's the first time you see a runtime with a bug?
This is not a unique occurrence.
It's also possibly a subtle dig at go, because unlike other languages go does not use dynamic linking, meaning bugs in libraries require recompilation (has positive effects too).
It just isn't the default compilation mode, you have to explicitly enable it.