3 ms·
Since when is 40% "nearly half". Can we change the title to something like: "40% of Debian packages might break if GCC changes the way it handles undefined beh
by babuskov 11y ago
Since when is 40% "nearly half". Can we change the title to something like:
"40% of Debian packages might break if GCC changes the way it handles undefined behavior"
- deng 11y agoMore like: Code might break if it depends on undefined behavior. But of course, that might not make it to the front page.
- Dylan16807 11y ago> Since when is 40% "nearly half". ...always? > "40% of Debian packages might break if GCC changes the way it handles undefined behavior" A lot of them are silently broken today. That's the scary part.
- IvyMike 11y agoFrom the article: "(the figure of 40% is a lower bound since STACK doesn't do the same level of analysis that gcc does)." So he adds a fudge factor to estimate actual breakage and comes up with "nearly half". I dunno, seems fair to me.
- dalke 11y agoBecause the title is a direct quote from text on the linked-to page, which is the usual HN practice when there isn't a good title from the source itself.
- tedunangst 11y agoWhen has 40% not been nearly half? What is the minimum threshold for a quantity to quality as nearly half?
- GTP 11y ago"Nearly half" is a subjective concept so different people can give different answers if you ask them wich value "nearly half" has. I also think that it strongly depends on the absolute number we are talking about, not only percentage.
- babuskov 11y agoSo, following that logic. 90% is nearly 100%. 10% is nearly zero. And 40% and 60% are basically the same, because they are both nearly 50%.