There is no reason to display “100%” in your UI for more than a single second. Either show 99% and then finish, or show 100% only when you are ACTUALLY done and only show it for a little.
If you’re still doing ANYTHING AT ALL don’t say you’re 100% complete. How is it still like this
I don’t think it counts percentages. It has to be more like : do this; display 30% ; do this ; display 70% ; do this ; display 100% ; do this; done (maybe);
Because Microsoft knows no one is going to stop using Windows even if it sucks. It’s same way no one actually moves to Canada when a shitty US president is elected. The average person has a high tolerance for bullshit.
more accurately, average person has a higher tolerance for bullshit than for spending many hours learning something new or spending potentially years applying for citizenship in another country
I imagine it started with some sub-installations actually giving approximations that were acceptable and summed up, but then some finalizing was not taken into account or something needed to be added after the other processes are finished, and the deadline was close. That last part builds up over time with other quick additions and some annoying stuff that is actually quite performance heavy and not easy to incorporate through the whole installation. “Let’s do it at the end as well.”
No time / budget to change the 100% to 99% as they have to adjust calculations based on the processes that actually do a good job. Although a display change could fake it, priorities are elsewhere.
Last week I had the lovely experience of it also pushing a bios update that enabled bitlocker and locked me out of my drive. I had to completely wipe the laptop and lose the data.
Exactly. After reading through some forums it sounds like BitLocker may have been enabled at the factory initially but I had never noticed and since I didn’t set it up myself I had no key. So anyone reading this and running windows: right click your C: drive and see if BitLocker is enabled. If it’s enabled and you didn’t enable it or don’t have the key then disable the encryption. You can re-enable it afterwords and safely backup your new key so you never find yourself in this situation.
When I updated to Windows 11, it detected TPM 2.0 but failed to notice my drive had an MBR partition table and therefore couldn’t use Secure Boot. It happily updated anyway and rendered my drive unbootable.
The original Azure progress bar was Microsoft’s crowning masterpiece of progress bars. It would very slowly fill up, and then wrap around and start to fill up again. To be fair, all of the animations in that early KnockoutJs version of the Azure portal were just incredible to watch, and someone must have put a lot more effort into them than they did adding features.
Spinners must die. I don’t care if I don’t understand what exactly you’re doing, Windows, (I’d be surprised if you knew), but show me something, anything about the steps you’re currently doing, so I can guess if you’re doing something at all.
They could actually show you a command prompt / terminal readout, which shows warnings and errors when things just outright fail and the process is borked… but that would scare people, apparently.
LOL, yup! I was just going to reply that people find that scary, and then got to your last sentence. Idk why it scares people. I love seeing the output.
Because MSFT long, long ago abandoned the concept of giving users choice, or just in general not treating them like idiot babies.
Brings me back to when I was contracting with them, same time Win 8 came out.
MSFT does what they call ‘dogfooding’, ie, every worker is alpha/beta testing basically all MSFT software all the time.
My team was managing SQL servers and running queries. SQL Manager, and a whole bunch of other shit completely broke when 8 came out.
It initially did not even have the ability to go back to a Win7 style interface.
They truly believed that limiting all office workers to a UI where they could have, at max, one pane on 1/3 of the screen and another pane on 2/3rds would be completely fine.
We effectively could do no work for about 1/3 of our contract.
Working at or for MSFT is a curse I would only wish upon my worst enemies.
I actually had to quit another, earlier contract as my manager expected me to work overtime without pay. Before that, my one cool boss just showed me that I was being paid about 1/3 of what MSFT was paying the contracting firm for me.
And that is to say nothing of the massive racism that all the American employees just looked the other way on: Pretty common for Indian employees of a higher caste to treat Indian contractors of a lower caste like total dogshit, and the line from HR was ‘its their culture!’.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.