3 ms·
Because it takes time to write a fix, test it, test it some more to make sure it doesn't break any of you 1 billion users, then ship it, then wait some more bec
by user5994461 10y ago
Because it takes time to write a fix, test it, test it some more to make sure it doesn't break any of you 1 billion users, then ship it, then wait some more because people ain't updating that often.
That's in total contrast to web development where you can deploy a fix in ~ 1 hour to all your users simultaneously.
- bArray 10y ago> Because it takes time to write a fix, test it, test it some more to make sure it doesn't break any of you 1 billion users, then ship it, Hasn't stopped Microsoft pushing bad updates in the past. > then wait some more because people ain't updating that often. That's a problem with their update model, security waits for nobody.
- ballenf 10y agoMS could have also chosen to push a fix that crippled CSS on table header rows or whatnot. Web rendering would break and users would complain, but at least users wouldn't have been intentionally exposed. It's a false dichotomy to suggest that MS's only options were an actual fix vs. do nothing. There are always other options.
- wdr1 10y ago> Because it takes time to write a fix, test it, test it some more to make sure it doesn't break any of you 1 billion users, then ship it, then wait some more because people ain't updating that often. Why does IE have a problem with this whereas other popular browsers do not?