Checkboxes that kill your product

Re:Checkboxes that kill your product by wpietri on Monday March 18, 2013 @03:27PM (#5396552)

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.

[ Parent | on HN ]

Re:Checkboxes that kill your product by singleuse on Tuesday March 19, 2013 @05:53AM (#5399859)

I'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.

[ Parent | on HN ]

Re:Checkboxes that kill your product by wpietri on Tuesday March 19, 2013 @01:59PM (#5402497)

Consider all the possible features that 1% of the userbase wants. Are you saying they all should be included?

[ Parent | on HN ]