6 ms·
As an end user, it is sometimes hard to distinguish between 'made to run buggy' and 'put no effort in to make it not buggy'. They are most likely doing the 'pu
by cortesoft 10y ago
As an end user, it is sometimes hard to distinguish between 'made to run buggy' and 'put no effort in to make it not buggy'.
They are most likely doing the 'put no effort in to make it not buggy' action, and it just appears that they are doing it on purpose.
- c3534l 10y agoBut the only time it is buggy if you SAY it's Linux. If you say it's Windows, it works fine. That's not having the software passively become buggy, that's CHANGING the way the software works if and only if the OS is Linux, but working correctly if it's told (but isn't actually) Windows. I don't think this is a conspiracy, but I don't think the characterization that users think that because OneDrive works on Windows better than Linux, buggy by inaction is assumed to be buggy by action: this situation is far more damning than that.
- emodendroket 10y agoIt seems entirely plausible that there are optimizations that are only applied on certain platforms or something with the idea that any platform should fall back to the slower but better-supported behavior.
- jacquesm 10y agoExcept that we're talking - as far as is visible to me at the moment - about server side behavior, something that need not change at all depending on the user's client.
- eridius 10y agoNo we're not. The bug report says 100% CPU. It's very clearly doing something client-side.
- jacquesm 10y agoThat is speculative. Yes, the client side is the one where the problem shows up but it's when the user agent is changed that the problem appears and the client side does not do anything with that user agent, it gets sent to the server. So something in the response from the server or some interaction with the server than causes the 100% CPU load.
- cortesoft 10y agoThat is exactly what the people you are responding to are saying. The client makes a request to the server, and the server either returns the new optimized client code if the user agent is one that it knows supports the new code, or it sends back the older, slower, client code for an unknown user agent. They are probably returning the older code because they KNOW it works, even if slower, while they aren't sure if the new code works or not on other machines. The author says it works fine on linux when getting the windows response, but we can't be sure he has tested every use case; maybe it fails under particular conditions, which is why they are still returning the old code. Or, perhaps, they just haven't tested it so they go with the safe thing, which is to return the older code.
- jacquesm 10y agoSo, you're telling me Microsoft is unable to tell the difference between code that doesn't work (the 'old' code) and code that does work (the 'new' code), and that to be safe they are returning the non-working code as a fix for potential problems that do not appear to exist? If there is anything that would be more damaging to Microsoft than calling them malicious it is probably calling them incompetent, that's their core expertise you are challenging there.
- wernercd 10y agoOf course MS is unable to tell the difference between code that works and code that doesn't... on an unsupported platform. Incompetent? "MS: We support Platform X, Y, Z." ... "Mob: MS must be malicious or incompetent because they aren't testing and pushing new code to Platform 9 3/4" Unsupported. Means exactly that.
- pbhjpbhj 10y agoShould be testable, for example what optimisations are in the FF48 code sent to Windows that breaks FF48 on Linux? MS will I'm sure provide those details to demonstrate their lack of malice. /s
- emodendroket 10y agoIf you're that hot and bothered about it try fetching a page with both UAs.