3 ms·
Misleading title. Reads like the bug was discovered 9 years ago but was not fixed until recently. However, the bug seems to have been fixed pretty fast. Thanks
by Kobajachi34222 6y ago
Misleading title. Reads like the bug was discovered 9 years ago but was not fixed until recently. However, the bug seems to have been fixed pretty fast. Thanks to the Go team!
- vlovich123 6y agoAnother way to read it is that 9 years worth of software could be susceptible. It’s patched now but how long will it take that all executables have been updated? How long for all projects to update their dependencies to one with a fix? Generally software deployment also varies wildly in terms of quality and speed.
- remexre 6y agoAnd, since people tend to link Go statically, it's not just like `apt-get upgrade libgo`, one has to do a full recompile. (Which, to be fair, Go makes a lot less painful than many languages.)
- shoo 6y agobugs objectively exist regardless of if they are discovered or not
- jacobush 6y agoFor it to be a bug, it must have a context where it matters, but basically, yes :)