121–130 of 270 posts
Earlier quoted context omitted.
Python might be just one of the languages required by the dev stack not the only language. Mise is the right tool for the job.
Last time I checked, Mise is still a one-man show. That’s way too risky for a critical party of my supply chain for my taste.
Earlier quoted context omitted.
The present is built mostly on layers of the long-past :) It makes me think of when Arch merged /usr/bin and sbin with /bin and sbin. Having them split made sense in a ton of scenarios that used to be very common, but increasingly the split was vestigial for most users.
Yea, my understanding is that the split between / and /usr used to be more or less: the drive they used for / ran out of space, so they mounted another drive as /usr. As a consequence, / became where you put stuff that was essential during early boot, while /usr was where you put everything else. But these days, "early boot" is handled by initramfs and we've all got drives large enough to not need the split anyway.
I've always used it on my Mac work machines, but always used my native package managers on Linux. What are the reasons to run homebrew on Linux? Better newer package support when you're on something slower moving like a Debian distro?
I've standardized my config scripts on using language managers for those tools (go, cargo, uv), which isn't perfect, so maybe brew is worth a chance.
Earlier quoted context omitted.
Are you implying that a 6 year old hardware is as good as a paperweight? Outside of the Apple fairyland this is just bonkers. I'm not blaming the Homebrew project/developers here, but the fact that many people are okay with deprecating perfectly fine hardware.
No, he’s asking what you think a reasonable support timeline is. An open source project supporting hardware 6 years old is pretty awesome.
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 !
Actually, Homebrew 7 is supported on your Mac, you just have to install Linux to use it. :) If you want to continue using the same MacBook that will be only path forward when Apple decides to EOL it (if it hasn't already happened). I'm a long time Homebrew on Linux user, it works really well. I always prefer it over the distro supplied package manager for user facing CLI apps.
Earlier quoted context omitted.
I didn’t build it. The emoji were my idea. I (and Homebrew) have used them heavily before LLMs did. Maybe LLMs loving them is my fault. Sorry if so.
Have we pinned down the emdashes source yet? ;-P
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?
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!
Thanks for the hard work, but the Tahoe limitation for the GUI app is absolutely ridiculous.
Always a joy to see security and performance as a big highlight on a release. Brew is notably slow compared to the other package managers I use, but never in an unbearable way. I've always used it on my Mac work machines, but always used my native package managers on Linux. What are the reasons to run homebrew on Linux? Better newer package support when you're on something slower moving like a Debian distro? I've sta…