221–230 of 271 posts
Earlier quoted context omitted.
We've all gone through it :-( Happy users of the (really good) software until our hardware gets "too old" and the inevitable rug pull.
That hardly happens on desktop/laptop Linux. Seems like a proprietary OS problem tbh.
Earlier quoted context omitted.
would you please share what amount of the new dev (work done on brew) is AI/LLM-assisted. this major version bump was very quick to arrive compared to when v6 got released?
Can’t speak for others but a lot of my work. I review it all locally first. The flow feels a lot like reviewing human PRs locally. https://github.com/MikeMcQuaid/AgentIDE I actually wrote my own “Agent IDE” to make this prompt/review/push flow easier.
`The macOS deployment target is set to 27.0, but the range of supported ....`
Golden Gate AAAAAARRRGGGHHHHHH
Just another few days, right? :)
Earlier quoted context omitted.
How many of those 20 year old projects had to go through an architecture change that the manufacturer no longs supports? Come on man be reasonable.
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…
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?
I'm salty today because I tried to run Fusion 360, and found that Autodesk just out of the blue decided that 1. My computer is too old to run the software (which ran just fine a few weeks ago on the same computer); 2. That I needed to update the software, and 3. The update will not run on my "old" computer. They took software that ran fine on my computer and deliberately pulled the rug out. Fuck Autodesk. I'm spending the entire afternoon exporting dozens of files I have on their cloud, one at a time, since they apparently can't even manage to keep an existing version of the software running.
Earlier quoted context omitted.
https://docs.brew.sh/Homebrew-Security-and-Supply-Chain We take supply chain security very seriously, moreso than many package managers.
I hate to have to be this harsh as it is clear you did a lot of work, but I have warned members of the brew team about serious gaps here multiple times over the years and seemingly nothing has been done. Brew is not anywhere close to a level of supply chain security to be allowed anywhere near production access or production code review. Language package managers are a joke and not worth comparing to but at least we…
If you have concrete concerns, please bring them to us. Vague concerns and hand-waving about “people getting hurt” isn’t appropriate or productive.
Earlier quoted context omitted.
I have this bound to an alias: bu Run it every couple of days, easy peasy.
If you're going to update that frequently, you may want to consider something that allows for cooldown like this [1]. I've gotten more nervous about supply-chain attacks over the last few months. 1. https://github.com/whoschek/homebrew-cooldown
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 MP to Homebrew over a decade ago. At the time, Homebrew was less finicky and better at resolving dependency conflicts. It was a lot easier to get a system running MacPorts into a an irretrievably borked state. Not long after, Homebrew install instructions became ubiquitous, whereas with MacPorts it seemed like you always had to figure it out for yourself — if the package was even available, which it m…
The second has also never happened to me. macports installs the packages into a separate prefix, and you just add that to the path, so I wonder how it could bork irretrievably.
Regarding instructions: for most packages, I found that just replacing `brew` with `sudo port` is enough, as most ports are available. And quite a few install instructions mention homebrew together with macports. I have not run into missing packages, but sometimes the ones that existed were a little out of date.
Earlier quoted context omitted.
That hardly happens on desktop/laptop Linux. Seems like a proprietary OS problem tbh.
You're definitely right about that. I'll admit it. If you're not the kind of person who likes to throw all your electronics out every few years to spend $thousands on new ones then the Apple ecosystem is not for you.
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?
Earlier quoted context omitted.
If you're going to update that frequently, you may want to consider something that allows for cooldown like this [1]. I've gotten more nervous about supply-chain attacks over the last few months. 1. https://github.com/whoschek/homebrew-cooldown
That's a very good idea. Thanks for the link. Ideally this should be a feature in homebrew.