|
|
|
|
|
by fenomas
2372 days ago
|
|
Yeah, I think the existing UI is absolutely correct for that one. I'm not a heavy brew user, but if it works like other package managers then the "update" command is a fairly casual, frequently used, and typically reversible kind of action. If you pull in too high a version of something, oops, remove and redo. Whereas "upgrade" is something you probably only do when you have a specific reason. I mean, it's sometimes sensible for apps to auto-correct on inputs, but a frequently used "muscle-memory" kind of action should never auto-correct into something heavy and non-reversible. I imagine that's the thinking there. |
|