never remove features: “product is too bloated”
remove features: “product is tricking us”
remove features: “product is tricking us”
I’d hesitate to call something like optional compact UI metrics “bloat”. To me the term is better applied to e.g. features associated with only tangentially related services or something running in the background sucking up CPU cycles for little user benefit… basically the modern Microsoft playbook.
Don't get me wrong. When Firefox removes a feature, often it's not out the concern of bloat to be able to serve existing users better, but to shift resources for the next revamp that will make the browser ever more "modern", to claw for a new userbase.