3 ms·
I think it's just a very public example of shitty coding. No decent code review should have allowed a catch-all condition to default to Windows 8.1 instead of "
by yid 13y ago
I think it's just a very public example of shitty coding. No decent code review should have allowed a catch-all condition to default to Windows 8.1 instead of "Unknown" or "Other" or some such. It's just a sad lack of attention to detail in a very public-facing way.
- nivla 13y agoWell how many people using non-windows OS do you expect to go to Microsoft's website to check for what Windows version they are using? It not lack of attention to detail, it is a waste of time trying to implement a complex User Agent parsing for that 1 in a million who decides to do it for fun.
- BlakePetersen 13y agoThere may have been a number of other factors at play that led to the decision to have windows 8.1 as the default. I wouldn't immediately jump to "shitty code" as the culprit here, especially when the tool works exactly as it should for it's intended audience. It may have been something as simple as developing this tool before having confirmation as to which user-agent win 8.1 would use at time of launch (is it be 5.2? nope, bumped up to 5.3. Good thing we put in that fallback before pushing into production!) or evaluating the ROI on supporting an 'other/unknown' fallback with additional development. One may consider putting resources toward developing code for a user-base that provides no return on the development investment is 'shitty coding'.