| ▲ | dgrin91 9 hours ago | ||||||||||||||||||||||
Doesn't the article state the opposite? The low end was not the problem. It was high end that was the problem. I like ragging on Microsoft as much as the next guy, but honestly this problem sounds complex & hard to predict. AI or not, this feels like the type of bug that would have slipped by me as well. The response clearly could have been stronger though. | |||||||||||||||||||||||
| ▲ | thesuitonym 9 hours ago | parent | next [-] | ||||||||||||||||||||||
The point they were making is that had Microsoft used high-end equipment in testing they may have found this issue before it hit production. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | zdragnar 9 hours ago | parent | prev [-] | ||||||||||||||||||||||
I read "more than one low end" as "more testing environments than one low end" rather than "more low end environments than one". It's a snarky way of saying they should have been testing high end environments for no more reason than they had the money to do it, rather than saying they should have been testing the low end more. | |||||||||||||||||||||||