> I'm saying that it's unsustainable to maintain a hundreds of features for the benefit of different slices of 1% use. There isn't one kind of "power user," es

> I'm saying that it's unsustainable to maintain a hundreds of features for the benefit of different slices of 1% use. There isn't one kind of "power user," especially for something like a web browser. If you want to support power users, you probably will need to support hundreds of specialized features, many of which won't be used my everyone. If you don't do that, then I think it's very unlikely that you support power users [1]. Apps with feature-sets like this exist, so I think it's wrong to make a blanket statement that it's unsustainable. I'm not saying it's always sustainable either: if you're a two man team at a small company, you probably can't manage to support much more than the core user group. However, Mozilla's big and I think they need to offer something unique compared to Chrome and Safari. [1] As opposed to developers or extension-writers. My definition of power user excludes people who extensively modify the software themselves.