[marionauta]

It's corporate talk for "if it breaks, don't complain"

[arboles]

It's also a sneaky strategy to deal with features you've decided to remove, because users are that fucking stupid.

1. Instead of just removing the feature, hide the feature and call it unsupported so the users who remember the feature can't complain yet.

2. Then finally remove the feature in the next update, with justification that it was an unsupported option and used by few people, so users can't complain.

Frog boiled. With each update the company seems to be acting rationally on "metrics" and principles, but the decision was set internally before that.

[afavour]

It can be metrics driven the whole way.

- Compact mode is rarely used and a pain to maintain

- If we hide the feature, what's the user reaction?

- Minimal user reaction to hiding, we're safe to remove

[micromacrofoot]

never remove features: “product is too bloated”

remove features: “product is tricking us”