4 ms·
I don't understand this comment, are you implying that it's the first time you see a runtime with a bug?
by Thaxll 10y ago
I don't understand this comment, are you implying that it's the first time you see a runtime with a bug?
- 0x0 10y agoWell usually you can just update whatever library has the bug and restart your applications, but as I understand this bug will be statically linked in all application binaries so they will all have to be recompiled and redeployed?
- Manishearth 10y agoYes, that's what the grandparent is saying, this is a bug in the runtime, which you can't fix by updating libraries, you have to update the compiler/interpreter (depending on the language). This is not a unique occurrence.
- wonko1 10y agoI think the original question was querying if the runtime is statically or dynamically linked. 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).
- pjmlp 10y agoYes it does, since Go 1.6. It just isn't the default compilation mode, you have to explicitly enable it.
- zigzigzag 10y agoRuntimes have bugs but normally you just download a new one and swap it out.