4 ms·
You already know why it should be in an add-on: because your use case is a rare one, and rare features for particular audiences don't belong in the main browser
by wpietri 14y ago
You already know why it should be in an add-on: because your use case is a rare one, and rare features for particular audiences don't belong in the main browser UI.
There are some fields where "But it's traditional," is a reasonable response to a proposed change. But software isn't really one of them.
- singleuse 14y agoI'd like to know on where the notion that removing features used by only a fraction of the user base is what should be done comes from ? It is brandished right and left as if obvious, but it is never explained.
- wpietri 14y agoConsider all the possible features that 1% of the userbase wants. Are you saying they all should be included?