News for hackers. Stuff that matters.
Re:The way Microsoft patched a recent bug raised some eyebrows by reacweb on Tuesday November 21, 2017 @04:15AM (#15746735)
A comment below says that Microsoft didn't write it (but Design Science). Maybe the C++ patch was rejected because the source code did not follow Microsoft coding rules mandating a complete rewrite of the code. To avoid a huge development cost, one rule has to be violated: either the binary patch or bad code. We can speculate many reasonable scenarios to explain what happened. I do not see any shame on Microsoft.
Re:The way Microsoft patched a recent bug raised some eyebrows by eesmith on Tuesday November 21, 2017 @06:37AM (#15747199)
In your scenario, Microsoft is making a probabilistic statement ("a bet") that there will not be many future changes to the code.

That is, the binary patch path is more expensive than code patches, because it requires more specialized skills. At some point, with enough patches, it would have been worthwhile to update the source and rebuild than to modify the binary.