Re:The Great DOM Fuzz-Off of 2017
by microcolonel on Friday September 22, 2017 @02:41AM
(#15309889)
> you can’t boil the ocean.
Call me crazy, but it seems like we have a responsibility to boil this ocean. If we don't, the quality will continue to spiral down into the abyss.
Re:The Great DOM Fuzz-Off of 2017
by WhitneyLand on Monday September 25, 2017 @04:59PM
(#15334089)
Boil the ocean is an expression meaning do the impossible, so I don't think it matters much if we have a responsibility to do something we are incapable of. It does matter if we do the next best thing, and that's where the trade offs come in.
It’s a good question but I’m not sure the answer is clear. On small projects I’d make the case that 100% of reproducible crashes should be fixed, always. However when the “project” approaches operating system scale and complexity, most pure principle policies like that cease to exist for practical reasons. Most decisions, not just bug fixing, are about tradeoffs/cost benefit considerations due to the simple realization you can’t boil the ocean.