News for hackers. Stuff that matters.
Re:Our Audit of Homebrew by latexr on Wednesday July 31, 2024 @08:04AM (#41118455)
That is provably false from so many angles.

* Apple has no aversion to Ruby, and on the contrary has multiple developers pushing for it. They themselves had MacRuby, a project that allowed one to create Mac OS X (at the time) applications with Ruby.¹

* The reason there’s even an Xcode command line tools package available officially from Apple is because of Homebrew. A third-party made it first by extracting the necessary bits and then Apple officially supported it.²

* There’s a liaison between Homebrew and Apple, who helped during the Intel to Apple Silicon transition.³

¹ https://web.archive.org/web/20100908131627/http://developer....

² I know this from a reliable source and it is public information, but it was so long ago it’s hard to find.

³ The official Homebrew Twitter account tweeted about this at the time. I no longer have a Twitter account so can’t dig it up.

Re:Our Audit of Homebrew by rurban on Thursday August 01, 2024 @03:44AM (#41126988)
Wrong. MacPorts started as official DarwinPorts, supported by Apple. It became independent later. It is a proper ports package manager.

Homebrew would have a good head start, because it can use a better language, ruby. But it blew its chances with many questionable choices, they are just amateurs. But as always, worse is better.