5 ms·

> It basically means: worth tailoring to, given precious UI space and limited developer resources. How much precious developer time is required maintain a user

by 394549 8y ago

> It basically means: worth tailoring to, given precious UI space and limited developer resources. How much precious developer time is required maintain a user-facing text field on an entity with only a handful of other fields? Certainly not enough to properly justify a feature regression with user-data loss. > Do you think 50% of power users used this feature? How about 10%? 5%? 1%? IMHO, you're thinking about power users incorrectly. Power users aren't as cookie-cutter as regular users, so you shouldn't expect them all to use an identical set of features. For instance, say you have 100 power user features. It wouldn't surprise me if none of those features passed 1% usage, but 90% of power users use at least one of them. Get rid of them all due to "low usage according to telemetry" and you've just created regressions for 90% of your power users.

dblohm7 8y ago
How is that supposed to be sustainable?
- 394549 8y ago
  Are you saying it's unsustainable to maintain an application suitable for power users? It'll definitely take more effort than maintaining a restrictive, dumbed-down app; but it's certainly not impossible and I think the benefit is worth it.
  - dblohm7 8y ago
    I'm saying that it's unsustainable to maintain a hundreds of features for the benefit of different slices of 1% use.
    - 394549 8y ago
      > 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.
      - dblohm7 8y ago
        > Mozilla's big and I think they need to offer something unique compared to Chrome and Safari Mozilla is tiny compared to the size of the Chrome team.
dao- 8y ago
> How much precious developer time is required maintain a user-facing text field on an entity with only a handful of other fields? The description removal blocked improvements to bookmarking that will actually affect a significant share of users: https://bugzilla.mozilla.org/showdependencytree.cgi?maxdepth=4&id=1402890&hide_resolved=1 https://bugzilla.mozilla.org/showdependencytree.cgi?maxdepth...
- deleted 8y ago
  [deleted]

by 394549 8y ago

dblohm7 8y ago

How is that supposed to be sustainable?

394549 8y ago
Are you saying it's unsustainable to maintain an application suitable for power users? It'll definitely take more effort than maintaining a restrictive, dumbed-down app; but it's certainly not impossible and I think the benefit is worth it.
- dblohm7 8y ago
  I'm saying that it's unsustainable to maintain a hundreds of features for the benefit of different slices of 1% use.
  - 394549 8y ago
    > 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.
    - dblohm7 8y ago
      > Mozilla's big and I think they need to offer something unique compared to Chrome and Safari Mozilla is tiny compared to the size of the Chrome team.

dao- 8y ago

> How much precious developer time is required maintain a user-facing text field on an entity with only a handful of other fields? The description removal blocked improvements to bookmarking that will actually affect a significant share of users: https://bugzilla.mozilla.org/showdependencytree.cgi?maxdepth=4&id=1402890&hide_resolved=1 https://bugzilla.mozilla.org/showdependencytree.cgi?maxdepth...

deleted 8y ago
[deleted]