Live data from Hacker News

Homebrew 4.0.0

brew.sh

401–403 of 403 posts

Re: Homebrew 4.0.0

#401

While I use Homebrew on my Mac — it is a major risk. I am afraid that the project is not following strict security policies and will be compromised at some point. Evil package or evil version of brew can steal or modify my data. I think this will also hurt the Mac platform. I wish Apple would invest some effort into building an App Store for cli programs. While it may be complicated for the community(require signing,…

They have, it's called Macports. It started as a port to Darwin of the existing *BSD ports and (I believe) is subsidized by Apple.

It installs itself in /opt/local, it respects the Apple SIP.

Homebrew basically sucks, because it doesn't follow Unix conventions and it doesn't follow MacOS conventions.

Macports has both pre-compiled and build-from-source, supports current and past MacOS releases, uses xcode/clang for compilation, supports port variants and multiple versions installed in parallel (with "port select" to choose a default) etc etc.

Not sure why people use anything else.

Re: Homebrew 4.0.0

#402

Earlier quoted context omitted.

`brew` has never been slow for me. (Subjective, obv.)

I've heavily used probably four Linux package managers, plus both major ones on Mac, and have used two or three less-common Linux package managers at least a little bit, plus a couple of the BSDs. Oh, and Chocolatey on Windows. I've never gotten this complaint about Brew at all. It has never seemed notably slow to me.

Nothing can feel slow to me anymore after dealing with emerge on gentoo, spending close to 20min solving dependency requirements. Surprisingly, compiling everything was the quick part, the frustration came from dependency resolution

Re: Homebrew 4.0.0

#403
post #394

Earlier quoted context omitted.

Did you mean /opt/homebrew? For Intel Macs it's /usr/local. You can't just delete it. You give up binary packages if you install it anywhere else.

Ah, yes I did mean `/opt/homebrew` - and yes I know on Intel Macs it works differently, but it can be installed at custom locations for people who still have them.

I stated the problem with custom locations already.
Post reply on HN