3 ms·
I fully support this decision (though the chrome team has made some really odd decisions - https://bugs.chromium.org/p/chromium/issues/detail?id=377191 https://
by jay-anderson 10y ago
I fully support this decision (though the chrome team has made some really odd decisions - https://bugs.chromium.org/p/chromium/issues/detail?id=377191 https://bugs.chromium.org/p/chromium/issues/detail?id=377191), but why is there a general move towards software not being configurable? In the past lots of software packages let you set the key bindings to your heart's content. It feels like more and more software is removing this ability. Are there architectural reasons? Is it a costly feature to maintain?
- gefh 10y agoYes, it's costly to maintain the combinatorial interactions between configurations. But 'make it a setting' has further costs- when you're supporting a customer and you can't figure out the exact state they're in, when you can't make sweeping product changes because 8% of users have some incompatible option set, when someone implements a bad feature and there's no strong way to keep it out if you can just 'make it a setting', or when a feature becomes obsolete but is kept around 'as a setting'. It relieves the product team from one of their most important responsibilities.
- another-dave 10y agoI know your numbers are only an example, but taken at face value — if 8% of your users have an option set, maybe it's because you've overlooked a user-case that's valuable to them. In that case, having a configurable app that can feed you in this data is like free A/B testing and is a boon to a product team, IMO.
- zyxley 10y agoEvery configuration toggle is something somebody can break by clicking it wrong. For most people, things like this are a source of background worry, not a useful benefit.
- deleted 10y ago[deleted]