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
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.
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);
Somebody convince me I’m wrong.
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
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.
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);
Or you can use 100% with countdown and skip options