Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Homebrew 7.0.0

brew.sh

Post reply on HN
Print view View original

251–260 of 270 posts

Re: Homebrew 7.0.0

#251

Post by setopt »

mikae1 wrote: post #250
setopt wrote: post #195

Earlier quoted context omitted.

> I've found that this way you can get many of the stability pros of using an atomic distro even on a non-atomic one. Digression, but I’m curious since you brought it up: Are you saying that Silverblue-based distros are noticeably more stable than Fedora? Or is it more a theoretical benefit, that you believe more in the long-term stability of that architecture?

> Are you saying that Silverblue-based distros are noticeably more stable than Fedora? TBH, I can only say it's far more stable than openSUSE, Ubuntu and Manjaro which are the non-atomic distros I've used for a long time. Aurora has never broken and I've never had any major problems that I can recall in over two years. I never initiate updates of the system, my Flatpaks or Homebrew. That happens in the background and…

Thanks for the input!

> I never initiate updates of the system, my Flatpaks or Homebrew. That happens in the background and whenever i restart (without me noticing).

Two follow-up questions on this:

- How does Homebrew auto-update on Linux? Do you have a daemon, cron job, or similar? Or a plugin for GNOME Software, Discover, or similar? (I’ve used Homebrew on Mac and Linux, but not with auto-updates.)

- Does Aurora sometimes reboot multiple times when doing updates? On normal Fedora I usually end up running dnf update manually to avoid doing updates in batches; when it updates on reboot, it can reboot 2-4 times… I have full-disk encryption on my laptop and it’s painful to have to wait for all the password prompts during updates. If this could happen be done in one reboot on atomic distros that would certainly be a benefit.

Re: Homebrew 7.0.0

#252

Post by setopt »

nxobject wrote: post #147
curt15 wrote: post #37

Earlier quoted context omitted.

Where do you draw the line between system packages and user facing apps? Some software defies such an easy categorization. If your default install doesn't come with docker and you install docker later for development, does that make docker a user-facing app? What about language toolchains like golang, rust, npm, etc?

It's an interesting question on Linux. On macOS entire toolchains would be fair game. I just ran `brew install colima`, `brew install llvm`, etc. But clearly anything that would conflict with distro-specific opinionated decisions is out. Or DE-specific opinionated decisions. Maybe a good rule is "anything that would be useful simutaneously on all *nix".

"Conflict" is maybe a strong word? Homebrew installs stuff into its own directory tree so it should in theory not have issues coexisting with native packages.

Re: Homebrew 7.0.0

#254

Post by maxloh »

e12e wrote: post #234
9dev wrote: post #39

Earlier quoted context omitted.

Why would you even use python without uv anymore, and have a system python binary and virtual envs linked to it?

> Why would you even use python without uv anymore Probably wouldn't: https://mise.jdx.dev/mise-cookbook/python.html#mise-uv > have a system python binary and virtual envs linked to it I'm not sure if you're saying avoid using system python? In my experience so far, you never want to develop complex software locked to system versions of runtimes. Too often you need a bleeding edge feature, or conversely need to postp…

Old Mise user too.

Now that PNPM supports managing runtimes [0], I found that most of Mise's offerings are actually built into package managers. Maybe I will have it graduates from my machine when I have time.

[0]: https://pnpm.io/cli/runtime

Re: Homebrew 7.0.0

#255

Post by hn_throw2025 »

mixmastamyk wrote: post #211
tonyedgecombe wrote: post #201

Earlier quoted context omitted.

> Find an ARM Mac used (like an M1) and upgrade. And throw away perfectly good hardware.

In general I agree, but recycling old power hungry gear may be better for the environment in the long term.

So discard a working and perfectly good Macbook to be replaced by a new one manufactured by the World’s #1 CO2 emitter and transported probably halfway around the world in a container ship burning dirty bunker fuel.

Re: Homebrew 7.0.0

#256

Post by hn_throw2025 »

Grombobulous wrote: post #169
aydgn wrote: post #13

Farewell, Homebrew. It's been a good run. - 2019 Intel iMac user.

I'm probably the millionth person to parrot this to you but my goodness you are a hero if you can tolerate the Intel Mac experience in 2026. I thought my Intel Mac from that era was incredibly weird. Little firmware-ish things were so glitchy and sluggish. At some point the wake from sleep/lid open just took forever in ways that didn't happen on older Intel Mac models (or maybe I was going crazy). I just had this str…

> used M2 MacBook Air

And what if you are a developer and need to replace a well specced Mac and don’t have serious budget, especially considering recent memory and storage price increases?

Rather than a coffee table status symbol or a fashion accessory for pretending to write a novel in the coffee shop?

Re: Homebrew 7.0.0

#257

Post by hn_throw2025 »

nebezb wrote: post #101
watermelon0 wrote: post #44

Earlier quoted context omitted.

Are you implying that a 6 year old hardware is as good as a paperweight? Outside of the Apple fairyland this is just bonkers. I'm not blaming the Homebrew project/developers here, but the fact that many people are okay with deprecating perfectly fine hardware.

No, he’s asking what you think a reasonable support timeline is. An open source project supporting hardware 6 years old is pretty awesome.

I managed to sell my battered old 32-bit Thinkpad on eBay last year. I couldn’t put Trixie on it, but Bookworm installed fine.

Re: Homebrew 7.0.0

#258

Post by 9dev »

doodlesdev wrote: post #119
9dev wrote: post #116

Earlier quoted context omitted.

Last time I checked, Mise is still a one-man show. That’s way too risky for a critical party of my supply chain for my taste.

So is sudo... And that's not "too risky" for the entire industry. That's not to say bus factor is irrelevant (I personally think about it a lot when choosing software projects), but truthfully the bus factor here especially doesn't matter much, as mise is an easy tool to replace (with asdf, for example) if something goes wrong with it eventually. I highly recommend trying it out. I resisted using it for some time, bu…

> So is sudo... And that's not "too risky" for the entire industry.

Sure it is, and that's why I'm looking forward to systemd's Run0 -- but for now, there's just no way around the sudo package. That's different for Mise, though, because there are a lot of ways to work productively without it. I'm not fond of consciously adding supply chain vulnerabilities to our stack when I don't have real pain to do so.

Re: Homebrew 7.0.0

#259

Post by 9dev »

e12e wrote: post #234
9dev wrote: post #39

Earlier quoted context omitted.

Why would you even use python without uv anymore, and have a system python binary and virtual envs linked to it?

> Why would you even use python without uv anymore Probably wouldn't: https://mise.jdx.dev/mise-cookbook/python.html#mise-uv > have a system python binary and virtual envs linked to it I'm not sure if you're saying avoid using system python? In my experience so far, you never want to develop complex software locked to system versions of runtimes. Too often you need a bleeding edge feature, or conversely need to postp…

> I'm not sure if you're saying avoid using system python?

That's what I'm saying, yes. System python should be treated as a REPL for interactive shell scripting and otherwise ignored entirely.

Re: Homebrew 7.0.0

#260

Post by mikae1 »

setopt wrote: post #251
mikae1 wrote: post #250

Earlier quoted context omitted.

> Are you saying that Silverblue-based distros are noticeably more stable than Fedora? TBH, I can only say it's far more stable than openSUSE, Ubuntu and Manjaro which are the non-atomic distros I've used for a long time. Aurora has never broken and I've never had any major problems that I can recall in over two years. I never initiate updates of the system, my Flatpaks or Homebrew. That happens in the background and…

Thanks for the input! > I never initiate updates of the system, my Flatpaks or Homebrew. That happens in the background and whenever i restart (without me noticing). Two follow-up questions on this: - How does Homebrew auto-update on Linux? Do you have a daemon, cron job, or similar? Or a plugin for GNOME Software, Discover, or similar? (I’ve used Homebrew on Mac and Linux, but not with auto-updates.) - Does Aurora s…

> How does Homebrew auto-update on Linux? Do you have a daemon, cron job, or similar? Or a plugin for GNOME Software, Discover, or similar? (I’ve used Homebrew on Mac and Linux, but not with auto-updates.)

I don't know, and I don't want to have know, how it works. :) It just does. You can force updates by running "ujust update". It updates Homebrew, Flatpaks, the system image and all Distroboxes in one go. You can also turn auto updates off.

> Does Aurora sometimes reboot multiple times when doing updates?

I doesn't reboot at all. I never notice updates, they happen in the background. System image upgrades are applied that time I turn off my computer and turn it on again. No extra reboots then. It's just a boot like any other.

Post reply on HN