Live data from Hacker News

Homebrew 7.0.0

brew.sh

31–40 of 270 posts

Re: Homebrew 7.0.0

#31
post #29

Earlier quoted context omitted.

I have one of the last Intel Macs and works perfectly fine (on Sonoma). How long should I expect working tech being supported? I am already looking at Linux, but still need to get out of the Apple ecosystem. I am not going to spend +2500 Euros every 5 years on a laptop

What does saying "working tech" do for you? If I have a working Samsung CRT from 25 years ago do I ping them about smart TV support? Nowadays it's a shitty situation with planned obsolescence; but 6 years for an open source project dedicating resources to a dead end is more than enough and appreciated.

[deleted]

Re: Homebrew 7.0.0

#32
post #14

Today, I’m proud to announce Homebrew 7.0.0. The most significant changes since 6.0.0 are faster installations and upgrades, stronger sandboxing, a native macOS app, built-in vulnerability checks and an advisory database, the end of macOS 10.15 support and Intel Macs moving to Tier 3 (announced last year).

I think at one point you said you’re working on a rust rewrite? Is that still in the cards?

I tried it. It ended up being slower on most non-synthetic benchmarks (like repeatedly installing the same thing with warm caches).

The lessons learned were instead used to make the Ruby frontend much faster.

Re: Homebrew 7.0.0

#33
post #14

Today, I’m proud to announce Homebrew 7.0.0. The most significant changes since 6.0.0 are faster installations and upgrades, stronger sandboxing, a native macOS app, built-in vulnerability checks and an advisory database, the end of macOS 10.15 support and Intel Macs moving to Tier 3 (announced last year).

I think at one point you said you’re working on a rust rewrite? Is that still in the cards?

They experimented with it but ultimately decided to focus on perf with their existing ruby codebase.

https://github.com/Homebrew/brew/issues/7755#issuecomment-51...

Re: Homebrew 7.0.0

#34
post #7

Does installation still require root and a dedicated user account on Linux? That really put me off.

See the release notes: we now have experimental support for using any prefix shorter than the Linux default. We are aiming to eventually fully support (Tier 1) any prefix under 64 bytes long.

Re: Homebrew 7.0.0

#35
post #13

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

Sorry we couldn’t support this for longer :(

From the release notes:

> The Intel support decision reflects the limits of a volunteer-run project: Apple have dropped Intel x86_64 support from macOS 27 Golden Gate and GitHub Actions will retire Intel macOS runners in autumn 2027. If Apple and Microsoft’s GitHub, two of the world’s largest technology companies, cannot continue supporting macOS Intel x86_64, sadly neither can Homebrew. MacPorts still supports macOS Intel x86_64 and is likely to provide better results on this platform.

Re: Homebrew 7.0.0

#36
I found that Mise handles all my needs for development and it is scoped so it doesn't try to update Python and break all my virtual env when I install something new /shrug

Re: Homebrew 7.0.0

#37
post #21

Today, I’m proud to announce Homebrew 7.0.0. The most significant changes since 6.0.0 are faster installations and upgrades, stronger sandboxing, a native macOS app, built-in vulnerability checks and an advisory database, the end of macOS 10.15 support and Intel Macs moving to Tier 3 (announced last year).

Thank you for Linux Homebrew! It works so damn well. For me the distro package manager is for system packages, Homebrew and Flatpak for the user facing apps.

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?

Re: Homebrew 7.0.0

#38
post #36

I found that Mise handles all my needs for development and it is scoped so it doesn't try to update Python and break all my virtual env when I install something new /shrug

I split my usage. Homebrew for OS things mise for the various tooling.

The only problem some things still have a dependency on requiring python and others on the system. The problem being that they’re there, mise works just fine.

Re: Homebrew 7.0.0

#39
post #36

I found that Mise handles all my needs for development and it is scoped so it doesn't try to update Python and break all my virtual env when I install something new /shrug

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

Re: Homebrew 7.0.0

#40
post #7

Does installation still require root and a dedicated user account on Linux? That really put me off.

I always download the install script and change the directory to my user home directory, ~/.brew
Post reply on HN