[RiverCrochet]

Tech-oriented people love software malleability and also can handle the responsibility - e.g. understanding something that's broken + customized by you could have been broken by you.

Non tech-oriented people, the masses, absolutely love customizability and malleability--but aren't willing to handle the responsibility. They will reach out to tech support who can't possibly know every customization option of every application and its effects, and complain when they tell them to reset/reinstall.

And in a corporate environment where the company provides the PC, the company would rather not deal with it. Office dominates at the workplace, is mostly making money from corporate users, and users want it to behave the same way it does in the workplace. So any backlash by users is simply not going to matter unless it might cause companies to not renew their licenses.

A company I work for is moving to Office-on-the-web for PCs that are used by people who don't really use Office that much except possibly to read Word docs, in order to save on licensing costs I presume. It's even less customizable than any desktop version. So the trend is going to continue.

[conartist6]

You're talking about a world in which costs are centralized. A central entity handles all R&D costs and all customer support costs for one product.

If you split the support costs between many members of a community though, you don't need to fear customization. Then, ideally, the users who are most alike will support each other, the same way you can get a degree of support for some particular flavor of Linux by seeking out other people who use that flavor (or another one that's enough like it)

Backlash will be in the form of working, competing software maintained by communities, precisely because this is the only form of backlash that might cause companies not to renew their licenses.

[xg15]

What is the "responsibility" of customizing the color scheme of your own PC?

[jrapdx3]

Well, there's a (modest) learning curve involved in customizing color schemes and of course more complex tasks that are still in the domain of user's options.

Users can be fearful of "messing it up" if they change defaults. Making changes necessarily confers responsibility to follow instructions, learn how to alter settings and know the set of options that are appropriate to change and which are not.

[Bjartr]

Not setting the text color the same as the background color and making everything unreadable, including the UI to change the color back?

[Jtsummers]

That takes a pretty basic safety mechanism to address, require confirmation after the change. Windows has (had?) that, after 15 or 30 seconds or whatever from a change (like to resolution or something) it reverts back without confirmation. This makes changes of all sorts easy and cheap to perform. The worst case is you idle for 30 seconds waiting for it to go back to a legible form.

[zzo38computer]

I think having the monochrome mode (which might be available at start time, and would also (temporarily) reset the font) would help with this and other problems (e.g. if one colour of the display is defective). This might be used for the UI to confirm the change but also when you start the computer that it can display such a message so that you can use that to recover from this and other problems (including screen resolution, colours, fonts, languages, and many more).

[Bjartr]

And when they click through the confirmation without reading it like the vast majority of users?

[Jtsummers]

If you can't see it because you borked up the colors badly enough, why would you be clicking on it?

[Bjartr]

Didn't say the buttons were invisible, just text.

Even if this specific example is flawed, non-technical users can and do end up in similar non-sensical situations that require a call to support to sort out. The more customization that's possible, the more complicated those calls can get. (Think of the support guy that has to figure out that Grandma's Windows Home setup has custom group policy settings that her well-meaning grandson setup to make things simpler for her by hiding this or that, and now she can't follow the tech's instructions that work for 99.9% of users)

Not only that, but they do so enough that the added cost to field those support calls is enough for companies to change their products to reduce their likelihood.

Almost no-one on this forum falls into the category of user I'm describing. And this kind of user is one of the most common for general consumer software. There is a real cost burden to supporting software with configurability.

And when this kind of thing gets messed up, do users go "Oops! My bad!"? No, they go "This software sucks, I'm going to use <competitor> instead where this kind of thing never happens!"

[immibis]

The old lady who calls tech support saying "half my screen is grey!" and it turns out she accidentally resized her taskbar to the maximum size.

[RiverCrochet]

Remembering where the setting is so if you want to update it again you do it on your own instead of calling tech support.