← Back to context Comment by Unroasted6154 2 days ago Good luck re-writing 25 years of C++ though. 2 comments Unroasted6154 Reply tux3 2 days ago It was Google's study that showed almost all bugs are in new code (and this was also the case of this incident)You don't need to rewrite everything to prevent the majority of new bugs, it's enough to protect new code and keep the battle tested stuff around Unroasted6154 2 days ago You can do that for new binaries. For existing ones you can't really or you get in a worse place for a long time.
tux3 2 days ago It was Google's study that showed almost all bugs are in new code (and this was also the case of this incident)You don't need to rewrite everything to prevent the majority of new bugs, it's enough to protect new code and keep the battle tested stuff around Unroasted6154 2 days ago You can do that for new binaries. For existing ones you can't really or you get in a worse place for a long time.
Unroasted6154 2 days ago You can do that for new binaries. For existing ones you can't really or you get in a worse place for a long time.
It was Google's study that showed almost all bugs are in new code (and this was also the case of this incident)
You don't need to rewrite everything to prevent the majority of new bugs, it's enough to protect new code and keep the battle tested stuff around
You can do that for new binaries. For existing ones you can't really or you get in a worse place for a long time.