Earlier quoted context omitted.
When I get angry about npm, I remind myself there is gradle.
When I get angry about gradle, I remind myself there is autotools.
Homebrew 3.0
241–250 of 516 posts
Re: Homebrew 3.0
#242The majority of the ports and software I want installed are essentially Unix/Linux/GNU environment tools. Macports has always seemed to me to be a more "unix-y" way of doing that, and it works politely with Apple's ways on top of the Unix core (eg locking down the system volume). It also has a very nice "select" and "variants" system that allows you to have multiple versions of a package as well as packages with more…
Re: Homebrew 3.0
#243Earlier quoted context omitted.
> It’s Weird that Apple doesn’t do this themselves. It’s not like they don’t have a cash. I can understand them not wanting to do it themselves. I don't think they want to take on the responsibility for maintaining all those packages (for legal reasons or otherwise). Because it's a "not officially Apple" thing, Homebrew can probably get away with a "no warranty" sticker that an official Apple project couldn't. What A…
I don't know about the "DUMP TRUCK OF MONEY", but a program that formalizes support for the Open Source community on MacOS would be a win for Apple as well as Apple's customers.
Re: Homebrew 3.0
#244I can’t even begin to imagine how much value Max Howell (creator of Homebrew) has added to the world. It’s the recommended package manager at every place I’ve worked at and saves so much headache. I use Linux at home and package managers like AUR are great, but macOS is where the users are.
Contrarian view here: brew fucking sucks. It’s the worst package manager I’ve used for doing random unwanted updates at odd times. Someone else would have filled the void if homebrew hadn’t shown up, and it would hopefully have been better. I hate that brew is good enough that it’s got some kind of local maximum such that there’s no replacement forthcoming. There, I said it.
Re: Homebrew 3.0
#245Earlier quoted context omitted.
Homebrew maintainer here: I'm sorry that we don't meet your expectations. Two things for your consideration: 1. It's uniquely visible among system package managers. When people have problems with a package in `apt` or `dnf`, they find a community or third-party repository for the package or bug the upstream directly. By contrast, Homebrew has always been visible on GitHub, does not require a special login to a bugtra…
Point 2 here is huge. If Apple cared about open source or cross-platform developers, they would pay at least one full-time Homebrew developer and upgrades would be smooth. It speaks volumes that they are swimming in money and can't be bothered to make a token gesture.
I agree with a lot of the sentiment here, but I want to make one important correction: Apple has helped us. In particular, they gave us access to DTKs for the M1 and provided us with a liaison for the migration. We're very thankful for that help.
That being said, Apple is a massive company and they have their own development goals and velocity for macOS. They're not actively looking to break Homebrew, but they're also not going to halt everything for us.
Re: Homebrew 3.0
#246Earlier quoted context omitted.
It’s Weird that Apple doesn’t do this themselves. It’s not like they don’t have a cash. And it’s important for devs to have up to date tooling. This intrepid band of volunteers are adding huge value to one of the largest corporations on earth. I appreciate the DIY effort of anyone who volunteers, though I see the donate tab on their website and sigh a little.
It seems to me that if you compare Apple and Microsoft, it's only the latter that cares deeply about the developer experience on their platform. https://github.com/microsoft/winget-cli
What was Apple's first product? A computer. A computer meant for people not having a CS background. The Apple II kicked off the home computing revolution, i.e. bringing computing to the masses. The Mac was the computer "for the rest of us" and was aimed squarely at graphic artists, desktop publishers, musicians, and the like.
So yes, Microsoft has always been developer and business focused whereas Apple has always been the computer "for the rest of us."
Re: Homebrew 3.0
#247Earlier quoted context omitted.
Yes. I'm really torn about brew. On the one hand, I hate to crap on the work that the maintainers have done, and it's clearly the best thing out there for macos. On the other hand, it's a terrible dictatorial piece of software that wants to command precisely how you use your computer; those same maintainers are actively hostile to users, as evidenced by the endless stream of nasty responses to issues, arbitrary chang…
I already stopped using Mac, but for people still using Mac: you really should give nixpkgs a try.
Re: Homebrew 3.0
#248Earlier quoted context omitted.
> What prevents you to do it better then? What prevent you from forking it? Sharing improvement ideas? Contributing to the project? I think ~everything he stated is generally assumed true. I use Brew installed software every single day, and appreciate it. That doesn't put it above criticism though.
There is no criticism in their statement though, just a generalized opinion/rant that doesn't point out single issue and is factually inaccurate.
I think these two might be somewhat contradictory.
Re: Homebrew 3.0
#249Earlier quoted context omitted.
It’s Weird that Apple doesn’t do this themselves. It’s not like they don’t have a cash. And it’s important for devs to have up to date tooling. This intrepid band of volunteers are adding huge value to one of the largest corporations on earth. I appreciate the DIY effort of anyone who volunteers, though I see the donate tab on their website and sigh a little.
It seems to me that if you compare Apple and Microsoft, it's only the latter that cares deeply about the developer experience on their platform. https://github.com/microsoft/winget-cli
Re: Homebrew 3.0
#250One thing I haven't seen mentioned here is that Homebrew forced people use Ruby to write formulas (ie packages), whereas MacPorts forced people to use Tcl. This one decision, plus hosting formulas on Github, was a major contributor to their present success. As much as I sympathize (deeply) with all the criticism of Homebrew here on this thread -- I used to use MacPorts religiously and love it -- I don't think Homebre…