3 ms·
To the extent to which operating systems manufacturers care about this, they then need to address the actual problem: that operating system upgrades are not jus
by saurik 10y ago
To the extent to which operating systems manufacturers care about this, they then need to address the actual problem: that operating system upgrades are not just useful security fixes but also "the entire computer now has a different user interface and no longer supports not only some of the software I was using but some of the hardware I rely on" (I know someone who upgraded to a new version of Mac OS X which rendered the $1000 multitrack mixer he uses for his recording job non-functional, and has since sworn off of updating anything ever, and I simply can't blame him).
- ninju 10y agoAnecdotal evidence of updates causing issues can be countered with example of where Windows Defender updates prevented virus, keyloggers and other malware from infecting computers. It is an unfortunate reality that we live a world where people are actively pursuing ways to infect and control our personal computers. The software (OS makers in particular) are doing their best to react/respond to the threats as they are discovered and identified. It is continual game of cat & mouse
- saurik 10y agoWhat? No: you cannot "counter" an experience with a non-experience. Users often directly experience the pain of upgrading. This teaches them to avoid upgrading. Users cannot directly experience the pain of not upgrading: that isn't a thing they can experience. At some time fundamentally uncorrelated to their decision to not upgrade an event which may or may not have been prevented if they upgraded happens to them (and that's assuming they even understand what is going on! usually this manifests as "computer is running slower"). This is like trying to teach someone to take extreme safety precautions around the magic glowing green rock that you insist will make them get sick and die thirty years later if they don't follow some exacting procedure that involves wearing a suit with a mask that actively hurts to wear: one with sharp edges which cuts their face and has even on multiple times left them with a scar. Sure: maybe you can try to spend a bunch of time teaching this person about radiation, but there are billions of them and they don't care. You can force them to wear the suit and make their lives painful and shitty. Or maybe you can admit to yourself that "maybe I am part of the problem" and make the suit not actively hurt to wear. You can't get rid of the suit, but we can at least decrease the attrition as much as possible. As far as I am concerned, Apple (and I am not neccessarily saying they are unique: only that I only can explicity state at them as I have been so centrally in their ecosystem for the past decade) actively scorns their "uneducated" users, refusing to accept any blame for the people who don't upgrade, and this is whether you are examining at their actual engineering practices, consuming their marketing messages ("be courageous"), or you talk to them in person (my favorite so far being someone who told me they are proud to work there as Apple is willing to tell our users that they are just afraid of the future and will need to adjust). And again: even looking past this problem (that you really can't "counter" experience with non-experience), providing "stable" upgrades as the default that do not push people to do major upgrades with totally-unrelated massive user interface changes or gratuitously incompatible architecture breakages. Does this take time and thought? Yes. But if you aren't doing this, you--not the user!--are directly responsible for any loss of life or property that results from users not upgrading. (FWIW, this is actually related in an interesting way to how people in my country, America, do not trust scientists. Rather than attempting to increase trust in science among the general population, which is the reason why countries that have high vaccination rates are where they are, people would prefer to blame the uneducated masses--end users who are constantly being jerked around by popular science reporting who are probably just sick of being told about stuff that never happens or being told to do first one thing and then the opposite next year--and legislate them into forced compliance :/.)
- blacksmith_tb 10y agoOuch, that's a particularly poignant example. On the other hand, I am not sure that never upgrading is a viable alternative, unless the machine connected to your picky hardware is air-gapped... My sense is that a fair amount of the UX obnoxiousness of all OS upgrades is a side-effect of not being able to reliably wake the machine when it's not in use - otherwise I'd rather have updates installed at 3AM, when there's no chance I'm doing something with my machine. Ubuntu is the least rude of the three in my experience, macOS in the middle, and Windows is the most abrupt, but something more like Chrome's silently upgrading all the time seems like it would be a better experience (until it broke everything, surprise).
- pfranz 10y agoAudio stuff has been notoriously finicky and late to support updates to the OS since the mid 90's. Most people I know go by,"Once it is set up, don't change a single thing." For quite a few years audio guys stuck to Mac OS Classic (9.x) because of the money invested in audio plugins. Audio hardware companies seem just fine with dropping support for new OSs forcing you to buy the new model.
- cryptarch 10y agoOS makers seem just fine dropping support for older audio hardware forcing you to buy the newer model. When did it become the new normal for OS's to break compatibility with older hardware? Or was all this hardware relying on undocumented and non-standardized interfaces?
- pfranz 10y agoI'm just talking about what I've seen for people who run businesses with large investments in audio equipment. It isn't just with updating software--that credo goes for which ports are attached, how things are wired, and even the levels on the console. I have no idea if the examples I've seen ware relying on undocumented APIs and as a user it's irrelevant (there aren't too many choices in high end audio hardware and you can't always mix and match vendors). I've seen a new OS comes out, it no longer works with the hardware you have (or it introduced bugs), and nobody issues an update to fix it on either side. You're running a business, so you may or may not care about the new features, but what was working yesterday absolutely has to work today. There's an article on the front page right now talking about how macOS broke the "poll" call. Nobody can say with confidence if it'll even get fixed. libcurl is working around it, but not everyone has the bandwidth to deal with it.