5 ms·

Good interfaces have 1 to 1 mappings between the available levers and the user's model of the tasks they wish and need to perform. Bad interfaces require you t

Good interfaces have 1 to 1 mappings between the available levers and the user's model of the tasks they wish and need to perform. Bad interfaces require you to care about implementation details that are arbitrary. Like whether the index is local or remote, whether it is stale or fresh, etc. This is not an opinion, this is what decades of product design lessons tell us. I don't use brew enough to ever go dig into settings, I wouldn't even know where to go find them, nor do I wish to expend cycles to go find them. They shouldn't design their software with such shitty defaults. All they're doing is ensuring my opinion of it gets worse every time I use it.

yamtaddle 4y ago
> Good interfaces have 1 to 1 mappings between the available levers and the user's model of the tasks they wish and need to perform. It already does. Sometimes I want to update. Sometimes I want to upgrade. This model matches the models of the other package managers I've used, for the most part. > I don't use brew enough to ever go dig into settings, I wouldn't even know where to go find them, nor do I wish to expend cycles to go find them. They shouldn't design their software with such shitty defaults. That's fine—but I guess it's not a huge frustration, then.
- unconed 4y ago
  It's a huge frustration that happens whenever I try to use it, which is not often enough for me to do anything about it aside from curse their idiocy. As for your mental model, you've adapted to the implementation details of specific package managers. This is just Stockholm lite.
  - thiht 4y ago
    It's not, it's you that persists in wanting update and upgrade to do the same. They don't do the same, but if you want, you can completely forget about update and just use upgrade, it does an update behind the scenes. But don't try to force kill update just because YOU have no use for it.

yamtaddle 4y ago

> Good interfaces have 1 to 1 mappings between the available levers and the user's model of the tasks they wish and need to perform. It already does. Sometimes I want to update. Sometimes I want to upgrade. This model matches the models of the other package managers I've used, for the most part. > I don't use brew enough to ever go dig into settings, I wouldn't even know where to go find them, nor do I wish to expend cycles to go find them. They shouldn't design their software with such shitty defaults. That's fine—but I guess it's not a huge frustration, then.

unconed 4y ago
It's a huge frustration that happens whenever I try to use it, which is not often enough for me to do anything about it aside from curse their idiocy. As for your mental model, you've adapted to the implementation details of specific package managers. This is just Stockholm lite.
- thiht 4y ago
  It's not, it's you that persists in wanting update and upgrade to do the same. They don't do the same, but if you want, you can completely forget about update and just use upgrade, it does an update behind the scenes. But don't try to force kill update just because YOU have no use for it.