I have been a Macintosh user for quite some time now and I have never, not once, not a single time, correctly distinguished "brew update" from "brew upgrade" on the first try

[pirijan@c.im]

@marcoarment truly the usb-a of terminal commands

[curtisbridges@mastodon.social]

@marcoarment I just make a single alias that updates everything and then i never have to remember anything but my naming convention.

[dluz@hachyderm.io]

@marcoarment The answer these days is simple! Just run `brew upgrade`, as it auto-updates. Erase `update` from your shell history and never wonder again.

[anyware@mastodon.social]

@marcoarment This is embarrassingly true! However, about two weeks ago, I had to manually type these many times, and for now (at least), I have it!

[matt_garber@mastodon.sdf.org]

@marcoarment Thankfully, I suppose, it at least matches the much longer history of Apt syntax behavior on Debian/Ubuntu servers, where you have to *update* the repo lists before being able to *upgrade* any outdated packages.

(And then I also make it easier by aliasing `brew update ; brew upgrade ; brew cleanup` as one run every few days.)

[drdrang@fosstodon.org]

@marcoarment It’s very simple. You use “brew update” when you want to update and “brew upgrade” when you want to upgrade.

[codingitwrong@oldbytes.space]

@curtisbridges @marcoarment yup mine is `brewup`

[malik@mastodon.social]

@marcoarment I‘m not alone

[tomhead@mastodon.social]

@marcoarment yep, yep, yep

Like `ln -s <source> <target>` or `ln -s <target> <source>`. Which is it? Hope I never end up in a situation where lives depend on getting it right...

[bbech@mastodon.social]

@marcoarment I never understand why I need to update then upgrade.

[wtl@mastodon.social]

@marcoarment