|
|
|
|
|
by csydas
1283 days ago
|
|
It's the wrong way to Fram the question. If I have a program that emits a painful audio bit every time the user does X and only 0.05% of users disable it by going to a configuration value they need to search for through dozens of (my own) SEO'd results, that doesn't mean that only 0.05% of users want it disabled, it just means that only 0.05% of users were able to figure out how to stop my program from doing X. I work on a product where our power user base is known for requesting registry options to change/disable feature x/y, and our market research has consistently shown a registry value doesn't enter most people's minds; to further this point, our user base is specifically IT persons. Even our Linux user base (actual day to day linux users) don't consider asking if we have a config file to edit somewhere in any overwhelming way. The point I take from this data (which I know is anecdata for you) is that most users assume software "out of the box" is what you see is what you get. Making these changes and options and not including a way to remove them is not a good way of tracking interest since the sample size that is actually willing to take the time to complain and post compared to those that just look at other software entirely are far different. You're dealing with a complete unknown in the Power User space; regular users are even less inclined to see how to disable it and hiding it behind registry edits is actually a dissuasion. |
|
I doubt that they removed the side taskbar option without very extensive testing and discussions. In fact, it's a well repeated criticism of Microsoft, that they have TOO MANY options, not too few:
https://www.joelonsoftware.com/2006/11/21/choices-headaches/