6 ms·
Almost always, nobody has any intention to "make it run buggy." It's about making it run well on platforms you care about (and officially support), and ignoring
by skybrian 10y ago
Almost always, nobody has any intention to "make it run buggy." It's about making it run well on platforms you care about (and officially support), and ignoring the others. Complicated software is usually fragile enough that it will have similar results.
- jacquesm 10y agoIf a user agent change makes the software slower for a platform then that's not exactly an accident so somebody must have had the intention to make it run buggy. This has nothing to do with 'making it run well on platforms you care about' but it is 'making it run bad on platforms you don't care about'. It takes more code for the software to act in this way (this is what proves this is intentional and not accidental), and more support to boot.
- erikpukinskis 10y ago> If a user agent change makes the software slower for a platform then that's not exactly an accident so somebody must have had the intention to make it run buggy That's not necessarily true. For example they might be doing polyfills that are slower than the native windows implementation. I feel like I'm seeing a lot of this kind of thinking everywhere. The canonical example for me is lately is "he voted for Trump/Hillary therefore he must support groping/war/whatever". I wish people would ease up on these kinds of deduction-based motivation attribution. It's my view that there enough self-professed unethical motivations for us to work against, without speculating. The speculation just muddies the waters.
- Lievelingsduif 10y agoI'm guessing you don't really understand what he's saying. He's saying that by pretending to be Windows instead of Linux the webapplication runs better. There's nothing native about it. The same exact website/piece of software runs better by saying "Hi I'm on windows". This obviously means foul play.
- JshWright 10y ago> This obviously means foul play. No, it really doesn't. It could just as likely mean they load a bunch of slow polyfills and workarounds when the browser is not part of a whitelist (assuming it won't have support for various APIs that it actually does support).
- pbhjpbhj 10y agoI struggle to consider that Microsoft is really that inept as to only be able to design it that well. I mean, do they do any testing at all? Across the browsers and platforms accessing their sites? Seriously, white-listing?? I don't buy it.
- emodendroket 10y agoIt seems most likely that they do testing on exactly the browsers and operating systems they say they support and no other platforms and do not want to expand the list because they'd have to provision more environments and do more testing.
- jacquesm 10y agoI'd buy that if it sent out the exact same code that it would without that UA. But it doesn't.
- JshWright 10y agoWhat don't you buy? They test with a certain set of supported platforms. If a client isn't one of those (whitelisted) platforms, then they may send out a bunch of inefficient polyfills so they know XYZ functionality exists, even if it's slow.
- jacquesm 10y agoExcept that it works just fine if those 'unsupported' platforms are treated in the exact same way as the supported ones. To make it seem as if a whole pile of work was done in order to make unsupported platforms work less well but this is a good thing is something that I find very hard to reconcile. And if this were a company that did not have a history of exactly such tricks it might be more believable, MS - with me at least - does definitely not have the benefit of the doubt in cases like these.
- fnord123 10y agoMicrosoft has a history. https://en.wikipedia.org/wiki/AARD_code https://en.wikipedia.org/wiki/AARD_code
- skissane 10y agoYou are talking about something Microsoft did in the early 1990s. It is very likely that most or even all of the people involved don't work for Microsoft any more. No company is ever going to be perfect, but I honestly believe that today's Microsoft is a much better corporate citizen than 1990s Microsoft was. (And, with the AARD code, while they shipped it turned on in the beta, it was disabled in the final release – which suggests to me that someone in charge at Microsoft had second thoughts about this even back then.) If 1990s Microsoft did something seemingly anti-competitive, it probably was intentionally anti-competitive. If 2010s Microsoft does something seemingly anti-competitive, while it still might be by intention, I'm more inclined to give them the benefit of the doubt and presume it is the unintentional side effect of an innocent (even if misguided) decision.
- jacquesm 10y ago> If 1990s Microsoft did something seemingly anti-competitive, it probably was intentionally anti-competitive. Ok > If 2010s Microsoft does something seemingly anti-competitive, while it still might be by intention, I'm more inclined to give them the benefit of the doubt and presume it is the unintentional side effect of an innocent (even if misguided) decision. That's fine with me. But the degree to which MS has abused its monopoly position in the past, the degree to which they have been found guilty of bribery (in very recent times) in order to push MS products where Linux would have been a viable (and more sensible) alternative (for instance: http://www.intellinews.com/former-romanian-minister-admits-taking-4mn-bribe-in-microsoft-case-500447431/?archive=bne http://www.intellinews.com/former-romanian-minister-admits-t... , there are plenty of other examples), the Windows 10 privacy violations, the crippling of Skype on Linux and so on make me believe that there are still at least some parts of MS that have not changed all that much.
- vedranm 10y ago
- WaxProlix 10y agoIt's been mentioned a bunch in this thread already, but they're doing feature support detection by user-agent string. It's not malicious, it's sloppy. Here's a quote from the /r/linux thread [1], courtesy of /u/angellus: > This is certainly a bug. It is not a targeted attacked against Linux users. Report it to Microsoft. Microsoft is just doing really shitty feature detection using User Agent strings instead of, well actual feature detection. I was able to reproduce the same result by setting my User Agent to Firefox 52 on Windows 98. If I set it to a "more realistic" user agent like IE 7 on Windows XP, it would actually redirect me to a busted page to upgrade my browser instead of Word Online. It appears if Microsoft cannot figure out your User Agent (including your OS as part of it), it gives you a busted experience. 1 https://www.reddit.com/r/linux/comments/60nj67/office_365_onedrive_looks_at_useragent_to/df7wnk1/ https://www.reddit.com/r/linux/comments/60nj67/office_365_on...
- pbhjpbhj 10y agoThat commenter appears not to have heard of browser detection or UA sniffing, it has nothing to do with feature detection, they're a completely different method (and paradigm). Nor should browser detection cause Firefox to follow a different switch in the code when on a different OS, not since about version 2 when I think there were bugs making that useful. Really browser detection was something needed to handle MSIE way back in the day, or possibly other browsers before web fonts. But this ain't browser detection, definitely not feature detection, it's OS detection - the system responds differently when only the OS in the UA string is altered.
- emodendroket 10y agoWhat he's saying is that they're using UA sniffing in place of feature detection (which is frowned upon these days but was common at one point).
- px1999 10y agoIf you have different stuff available, you might choose to only cache/microoptimise the pages served to 98% of your userbase, which would lead to this type of effect with no malicious intent.
- AsyncAwait 10y agoSimple solution, do not do preferential treatment based on one's OS.
- lighthazard 10y agoWhile it's a solution, it's not a simple one. Developers don't have this luxury. Choosing an OS to support means supporting all the APIs and possible ecosystem that comes with it.
- AsyncAwait 10y agoBut they're not supporting an OS, but a browser here. If it works in Firefox on Windows, there's no technical reason for it not to work the same way in Firefox on Linux.
- emodendroket 10y agoYeah there's no reason at all that anything would work differently in one browser or another, signed, a guy who has never done Web development.
- minitech 10y agoAgain: operating system, not browser.
- allannienhuis 10y agoThere are differences in supported features on different OS's with the same browser. They don't ship identical bits on each platform. The differences are pretty minor OS integration things usually, but there are differences.
- deleted 10y ago[deleted]
- bubblethink 10y ago>Almost always, nobody has any intention to "make it run buggy." Well, Microsoft has a long history of "making things buggy" everywhere else to create lock-ins. This instance may not be strictly related, but people's attitude has been shaped by years of anti-competitive stuff that MS has pulled.
- skybrian 10y agoThey do have a reputation, but it's decades old, and things have changed quite a bit. I don't think we should base our conclusions on stale data.
- Piskvorrr 10y agoDecades old. The GWX consent brouhaha is decades old? Edge (not IE) becoming the default browser all by itself is decades old? Riiiiiiiight. Decades of consistent data, methinks.
- gkya 10y agoI really don't get why they can't put the browser they like as the defaultone into their OS. Not that I'm an MS apologetic (I don't really use anything MS since time immemorial) but it seems silly to me, frankly.
- bubblethink 10y agoI think it has a habit of changing itself to default even after the user sets something else as the default. Minor annoyance though compared to the overall pain of using a windows machine.
- Piskvorrr 10y ago"Minor" depends on whom you ask: each time this happens, MS generates n angry support tickets...for me, not for themselves, of course: "the computer is broken again and I have lost all bookmarks and sign-in data, why did you break it again?!?" (The good news is, of course, that nothing is "lost" except for the default browser flag: resetting to FF fixes it...until next time)