Live data from Hacker News

Homebrew 7.0.0

brew.sh

231–240 of 271 posts

Re: Homebrew 7.0.0

#231

Earlier quoted context omitted.

It is Rust now?

It's still in ruby, although I see the new GUI is in swift: https://github.com/homebrew Rewriting a program in Rust (specifically) really only makes sense for a few reasons: 1) the existing implementation is in an unsafe, cumbersome language (C, C++). 2) the existing implementation language is too slow and that slowness cannot be worked around . 3) the implementation is enormous, in a dynamic language and you despera…

i just tested and `mise bootstrap` is over twice as fast at installing when a bottle was in the cache. other commands like `status/check` are 20-30x faster. that's without spending much work at all on perf—i'm sure i could bring these numbers down much further.

Re: Homebrew 7.0.0

#232
Congrats on the release @mikemcquaid. I like how the trusted taps feature could be opted into early. It made it easier to migrate my setup before it became compulsory. Hope big changes like that can keep the same flow. Keep up the great work!

Re: Homebrew 7.0.0

#233
post #120

Thanks for the hard work, but the Tahoe limitation for the GUI app is absolutely ridiculous.

Yeah, I'm holding onto Sequoia until after Golden Gate is GA. I've heard nothing good about Tahoe.

same. "macOS Tahoe 26+" requirement is a bummer.

Re: Homebrew 7.0.0

#234
post #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?

> 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 postpone updating due to needing an old version for some reason.

Re: Homebrew 7.0.0

#235
I’ve really been enjoying nix as my package manager on macos. It’s on a separate volume so feels even more isolated from clobbering my macos and has, in my uninformed opinion, better sandboxing and reproducible builds

Re: Homebrew 7.0.0

#236
post #54

Earlier quoted context omitted.

How come that MacPorts supports macOS versions all the way back to 10.5 Leopard in the latest version?

That's an excellent question for the maintainers of the MacPorts project! It can supplement the very clear and polite answer you've already received from a maintainer of Homebrew.

The polite Homebrew project that used to market themselves with "MacPorts driving you to drink?" on their website.

Re: Homebrew 7.0.0

#238

As a MacPorts users (generally light-weight, just a few things here and there): Has anyone gone from MP to HB, or vice versa? Why did you switch from one to the other (and perhaps back again)? What did you find as the pros/cons of each?

I switched from Homebrew to MacPorts a few years ago because of Homebrew's aggressive dropping of macOS versions they consider "too old." Even in the top-comment announcement here[1] they are making sure to include that they are removing support, as if they're proud of it! MacPorts generally doesn't care what version of macOS you run, so here I am. I'll probably never go back to Homebrew. MP is great! 1: https://news…

Yes, the pride in aggressively dropping support for Macs that just received a major OS release from Apple only 12 months ago (and they were selling just three years ago) is a little off-putting.

Re: Homebrew 7.0.0

#239
post #15

And that's the end of Homebrew for me as a user. I like the app, but my old Intel MacBook apparently can't handle it anymore. I'm back to the old installation methods !

How long do you expect them to support Intel processors though? It’s been like 6 years since the last MacBook release had any Intel processor, and Apple doesn’t make OS updates anymore, so it doesn’t surprise me that Homebrew stopped too.

Years, honestly. After all, Intel Macs just received a major macOS release from Apple only 12 months ago. MacPorts manages to support all the way back to Leopard!

Re: Homebrew 7.0.0

#240
post #223

Earlier quoted context omitted.

Homebrew doesn't have to lift a finger to support Intel Macs. It already does! All they have to do is not kill support for them. Hey, it's their software, they are all volunteers and can do whatever they want. I'm grateful for the short window of time in which I was able to use their software. I don't get to decide their support period, but I will still hopelessly complain about it. "Deliberately breaking compatibili…

Software maintenance is not free, especially for a project the size of Homebrew, and it's perfectly reasonable for software to not be supported on older computers due to maintenance burden, with a good example being 32 bit processors. If you had a 32 bit processor would you expect all of your software that was supported now to be supported forever, just because it supports it now?

How does MacPorts manage to do it?
Post reply on HN