> I’ve never sat there thinking “If this was only 2 seconds faster…” while doing an update

I definitely have thought something along those lines (mostly when I go to install a small tool, and get hit with 20 minutes of auto-updates first).

Pretty sure I also will not be adopting this particular solution, however

▲

bombcar 7 hours ago | parent | next [-]

I've never thought "only 2 seconds faster" - I've certainly thought "why is this taking half the time it takes Gentoo to recompile an entire server".

▲

saghm 2 hours ago | parent | prev | next [-]

I'm not sure if I just have way fewer things installed than most people or I just update more often, but I haven't experienced anything like this for years. I run `brew upgrade` probably around once every (work)day, usually right before doing a git pull or something, and then I'll quickly look at a couple emails or slack messages, and then it's always done by the time I switch back

▲

joshstrange 7 hours ago | parent | prev | next [-]

But you can turn that behavior off, IIRC it tells you the environment variable to set if you don’t want it to do that every time it runs.

I agree it’s annoying, but I haven’t turned it off because it’s only annoying because I’m not keeping my computer (brew packages) up-to-date normally (aka, it’s my own fault).

	▲	swiftcoder 6 hours ago \| parent \| next [-]
		I'd be much happier if it were on a background job, than arbitrarily running when I invoke a command
	▲	slackfan 6 hours ago \| parent \| prev [-]
		Terrible default behavior is a great reason to abandon a software package.

▲

SOLAR_FIELDS 7 hours ago | parent | prev [-]

FWIW this seems to have improved in recent years. Back in the dark times of non parallelized downloads I would purposefully wait to end of day and fire the thing off before leaving