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