Earlier quoted context omitted.
Somebody sneak into this guy's office and move his 'debug run' key from F5 to F9.
I don’t use keyboard shortcuts TBH.
Why Johnny Won't Upgrade
71–80 of 588 posts
Re: Why Johnny Won't Upgrade
#72Earlier quoted context omitted.
So to sum that up, Johnny Won't Upgrade because like as not, the writers of the updates are The Enemy.
That is the modern tech business model. Rope in naive people with excellent services offered at a loss or at cost, wait for them to develop dependence, use nazi cult-think psychology to inculcate irrational loyalty to the platform, then take everything away in a major software update and sell it back to the poor fools for big profits.
Inevitably some users will complain about changes in every new update while others complain about a lack of eagerly awaited new features and bug fixes. You cannot make everyone happy :/
I'm sympathetic to the idea that workflow/ui changes should be explicit updates (or on beta opt-ins) with security/crash fixes being automatic. This model makes the most sense for professional tools that people make a living from (e.g. CAD). To be sustainable, software with multiple supported major versions will cost more.
Re: Why Johnny Won't Upgrade
#73Earlier quoted context omitted.
Hey, you know your car that you brought in for an oil change? I switched the turn signal controls with the wipers. No charge, and no givebacks.
I really think I could adapt to that easily and wouldn’t mind.
Re: Why Johnny Won't Upgrade
#74Earlier quoted context omitted.
Because for the most cases it is just a friggin' tool and routine the user had accustomed to. I do not want to hunt for the same item in a different place. Think of it as if your screwdriver used daily will have suddenly started to change shape every once in a while.
Most people aren’t really complaining the new UIs are worse - they just don’t like any change at all. It’s silly stubbornness.
Re: Why Johnny Won't Upgrade
#75Earlier quoted context omitted.
>I lost track of the number of times a friendly Windows 10 (and 7) update has re-enabled telemetry. Either that or there is yet another, completely different post-update Wizard for advertisement, telemetry, default applications, and other privacy stuff (There sure is a lot of effort put in moving settings around each update!) ...and that's why I'm using LTSC, because it's limited to security updates and supported for…
I've read[1] that it's possible to legally obtain LTSC without volume licensing by purchasing a few other Microsoft thingies. Is such a method how you did this, or did you unfurl your sails? Btw (rant incoming), this isn't a spiel against piracy. If Microsoft complains that people pirate LTSC without providing an easy legal way to obtain it, they can cry me a river. I just switched over to Linux from Win7 early this…
Neither. Ended up using a msdn key.
Re: Why Johnny Won't Upgrade
#76Some automatic updates should really just be different products. The most obvious one at the moment is Android Firefox is getting a big automatic update that, for a lot of people, will be a very big downgrade and an unfriendly UI change. But Mozilla doesn't want to maintain security patches for X different products. And that's true of most vendors. This model of computing where all users are always on the latest vers…
Is that why Mozilla sent notification spam to announce that the app will be updated?
Re: Why Johnny Won't Upgrade
#77> should never update a user interface without allowing the previous one to be used as the default I don’t understand why people are so precious about their UI and workflow. They obviously managed to learn and adapt to the current UI. Why can’t they adapt to a new one? If you’re super sensitive to something as trivial as a change to a menu location maybe that’s a sign you should be automating whatever your workflow i…
Now you are speeding with 150km/h down the highway and voila, the screen is gone (it's there in fact, but it's not the same screen any more).
Have fun poking with this new updated UI and workflow.
BTW, this example is exaggerated of course, but not completely unrealistic, and it's easy to find similarly disruptive situations triggered by a UI or workflow change.
Re: Why Johnny Won't Upgrade
#78Earlier quoted context omitted.
Because for the most cases it is just a friggin' tool and routine the user had accustomed to. I do not want to hunt for the same item in a different place. Think of it as if your screwdriver used daily will have suddenly started to change shape every once in a while.
Most people aren’t really complaining the new UIs are worse - they just don’t like any change at all. It’s silly stubbornness.
By default, changing the expected behavior is bad, there needs to be some benefit that justifies the change. It's not silly stubborness, it's pointing out that it is harmful and counterproductive to disrupt people's workflow. Variety is nice in food and entertainment, but in productive workflow predictability, reliability and lack of variety are very, very valuable. Saying "the new UI isn't worse" is not sufficient - is the new interface significantly better? Was the change required to enable something that I want which wasn't possible with the old interface? In that case, sure, make the changes - but not otherwise.
Every change in the interface that's not 100% backwards compatible incurs a nonzero cost, effort and inconvenience. Sure, people can and will adapt, but requiring them to adapt requires them to spend a scarce, valuable resource - attention. If a tool doesn't do the expected thing right away because it has changed, then it has failed, it has distracted the user at a time when they wanted to do something else instead of playing with the tool. That's the key difference between a toy and a tool; a toy is useful for it's own sake and should draw attention to it, while a tool is useful for doing particular things and must get out of the way, allowing the user to focus on the job or the product instead of the tool.
Re: Why Johnny Won't Upgrade
#79Some automatic updates should really just be different products. The most obvious one at the moment is Android Firefox is getting a big automatic update that, for a lot of people, will be a very big downgrade and an unfriendly UI change. But Mozilla doesn't want to maintain security patches for X different products. And that's true of most vendors. This model of computing where all users are always on the latest vers…
Re: Why Johnny Won't Upgrade
#80Some automatic updates should really just be different products. The most obvious one at the moment is Android Firefox is getting a big automatic update that, for a lot of people, will be a very big downgrade and an unfriendly UI change. But Mozilla doesn't want to maintain security patches for X different products. And that's true of most vendors. This model of computing where all users are always on the latest vers…
And good lord do I hate it
Now, not only do I have little-to-zero control over the bits on my machine, but I'm fully locked-in to whatever shenanigans Company X has decided is appropriate for me