export HOMEBREW_NO_ANALYTICS=1There are likely to be more issues related to Apple's switch to the `prime` linker.
(I’m a port contributor and am on macports-users where this issue has come up twice. There is what I think is excessive concern about the macOS beta NDA preventing the creation of a package installer until after GA when it no longer applies. A bigger problem is the availability of sufficient build hardware as they have a smallish Mac mini multi-booting into 11, 12, and 13.)
./configure && make && sudo make installThe homebrew team seems incredibly burnt-out, to the point of hostility. I've really enjoyed the nixpkgs community so far and encourage others to check it out; it hasn't replaced homebrew entirely for me (yet), but it's getting closer every day.
macOS could be a modular rolling release, but you need to milk the peasants from time to time
Macos 12 will run on most Macs from 2015 and later.
8 year old hardware isn't Earth shattering, but it's also not a "hostile" period of time for a non-commercial open source project to support. And it's certainly not "new hardware every year".
Old Macs are often perfectly usable in terms of hardware, but macOS security updates have left them behind.
As of today, it's likely that the 2016 Mac I'm writing this on (which can run Monterey but not Ventura or Sonoma) is out of support.
Of course the Mac apocalypse will be when x86 support is dropped, possibly starting in the next macOS release.
Once my (i)Macs stop receiving security updates though, I might try a Linux distro, just to give them a second life.
I have used it before and, in my experience and everyone else I know who has used it, the vast majority of time the newer versions run absolutely fine with no issues. Occasionally some newer features don't work, but I'd but confident that 2015/2017 iMacs would be able to run the latest version no problem.
Those both should still be getting security updates. Ventura just updated to 13.6 this morning, Monterey updated to 12.7 a few days ago, and Big Sur updated to 11.17.10 a little over two weeks ago.
Big Sur is expected to stop getting security updates in a couple months. Monterey will probably get them until sometime in the last quarter of 2024, which would be the end of the line for 2015 5K iMacs. 2017 5K iMacs should get Ventura security updates through the last quarter of 2025.
It's still my impression, that the 2017 Macs (sold by Apple well into 2018), should have made the cut for Sonoma. I don't even care about any of the new features. I'm more interested in bug and security fixes. So hopefully I have more time to hunt for the perfect display that can adequately replace the 5K 27" of my current setup. And I know there is the Studio Display. But that one is too expensive for me.
It's been that way for about a year and a half now and has not gotten any worse so I don't think I'm in any danger of suddenly needing a new Mac. The way my iMac happens to be on my desk I'm directly in front of a spot about 30% in from the left and most of my main focus is on the left side, so the bad pixels aren't too annoying.
The 27" 5120 x 2880 display has definitely spoiled me. I want something with a similar density and not much bigger or smaller than 27".
These seem to be the choices currently:
1. Apple Studio Display. As you've noted it is expensive. It also comes with a stand that does not have a height adjustment. Add $400 to get it with Apple's height adjustable stand. (Or for $0 get it with Apple's VESA mount adaptor instead of the standard stand, and buy your own stand. If you can find a VESA compatible height adjustable stand for less than $400 this is cheaper than buying Apple's stand).
One thing to not if like me you would really like a monitor that you can keep using for a very long time is that in 2021 Apple made a change to AppleCare. It used to be that you could buy at most a small fixed number of years of AppleCare. Now you can keep renewing AppleCare indefinitely.
For the Studio Display it is $49.99 per year. If the Studio Display is fine for someone except for the price, it might be worth considering if that plus $49.99 per year, which should let you keep it working for a long time, would make it worth it.
2. LG UltraFine 27MD5KL [1]. Supposedly this is the same LG panel that Apple used in the 5K 27" iMacs. Just under $1300. Seems to get good reviews.
3. Samsung ViewFinity S9 [2]. This is new. $1600 so same as Apple's price for the Studio Display, but the S9 is height adjustable and VESA compatible so no paying extra if you want height adjustability.
[1] https://www.bhphotovideo.com/c/product/1500040-REG/lg_27md5k...
[2] https://www.bhphotovideo.com/c/product/1760795-REG/samsung_l...
The Samsung display seems nice. But how long is Samsung going to support the devices OS? The price is also not competitive in my opinion. For 1600 I would prefer the Studio Display, even if it's not height adjusted.
I will probably wait for the next Mac mini model with the M3 SOC. Luckily I'm not in a hurry.
The way I see things Apple is completely responsible for this problem and should also be responsible for providing a decent solution at a reasonable price.
But currently the cheapest option (Basic M2 Mac Mini + Studio Display + Keyboard & Mouse) 2642€ instead of the previous 2100€ (inflation is unhinged in Apple land) and on top of being much more expensive for a way more locked down configuration (previously RAM was freely upgradable and SSD upgrade was involved but doable) it is not faster in a way that match the price increase or even better than what Intel has been doing. In fact the truly faster is mostly single thread performance (42% better), multicore is a just bit faster (21%) and GPU is actually slower (-14%). In other words : for much more money you gain a bit not in way that is change what it possible to do with the computer but you also lose in a way that make some things you could do before worse (gaming and generally). That is on a
Lifelong customer, got my first own mac at 15, which was an ibook and also my first personal computer at all. I also bought the second gen ipod (first gen didn't get much availability in france) and even imported the first gen iPhone
Maintainers get requests to do things they have no interest in, like maintaining software for OSes past a certain date. That doesn’t sound so bad, but there are a lot, and they can even be mean. The maintainer can block these users individually, but it’s different users all the time, so that doesn’t stop it.
So, the maintainer addresses the user base, the whole crowd all at once. The problem is most of these users haven’t seen these interactions, so the message seems hostile. Having someone say “I owe you nothing.” seems really weird when you’ve never asked them for anything. Or, if they list of all the ways and reasons for you to not contact them it looks hostile. The users don’t see the fan next to them throwing a beer can at the center fielder.
Max Howell (founder of homebrew) went to interview at Google, shoved a coding exercise back in their faces, made a snotty comment about how all the engineers at Google using Macs use his code and how dare they blah blah greatest engineer in the world blah blah, and walked out the door.
That coding exercise was likely given to him precisely because all the google engineers had a lot of experience using brew, or they did it as ego check to see if he'd be insufferable to work with.
Howell failed to realize that and instead went and bragged about it on twitter, almost certainly confirming for the hiring committee that things had worked exactly as designed.
Whole lot of fucking sass from a man who either didn't care or didn't know about the security implications of making a directory in the default path user-writeable, thus making probably hundreds of thousands of developer's systems less secure:
https://infotoast.org/site/index.php/2021/05/30/homebrew-is-...
And for what it's worth, Howell did say he regretted his tweet, and that he wasn't up to snuff technically (in the Quora link in a sibling comment to this one).
And that's not even getting into the "waaa?" from `du -hs /nix` although I am open to that being a misleading dumber due to hardlinks and other trickery that du may not correctly surface
Are you running garbage collection? It gets out of hand if you keep all versions, but you don't need to do that
Though it does tend to get clobbered on macOS updates.
The default installer is not idempotent yet (and my work on trying to resolve that has stalled, unfortunately, see https://github.com/NixOS/nix/pull/7603), so trying to run it again to fix this issue will result in errors.
Nope, du counts hardlinks correctly when it encounters the same inode multiple times in the course of fulfilling a single invocation.
per https://ss64.com/osx/du.html :
> Files having multiple hard links are counted (and displayed) a single time per du execution.
Nix's disk usage profile is pretty similar to Flatpak's, or to a collection of closely related Docker containers. The difference between no Nix install and having one isn't huge. But your first installed Nix package will pull in very low level common dependencies— on Linux, everything between whatever application and the kernel (and on macOS, a bit less). Your next application will come with a smaller increase. Once you have a handful of programs installed, you no longer have big downloads for individual additions. When you have a lot installed, the difference isn't that huge, proportionally.
Over time, your Nixpkgs version will rotate and you can end up with deps from old versions of Nixpkgs, which can take up a lot of extra space. But that's easy enough to manage by pinning Nixpkgs.
If you ever uninstall programs, Homebrew's broken uninstallation functionality can very quickly make a Homebrew installation much (up to several times) larger than the equivalent Nix one once you have more than a handful of packages installed.
```
# Please don't change this. We don't support it, because the
# default shell profile that comes with Nix doesn't support it.
readonly NIX_ROOT="/nix"
```
I haven't seen any configurations where the entire /nix is relocated, but nix _does_ support relocating the store with the environment variable `NIX_STORE_DIR`.[1]
However, this means that you can no longer use the the binary cache and *everything* you install has to be compiled from scratch, including glibc. The reason is that nix usually patches paths like `/bin/myprogram` to `/nix/store/1238f...-myprogram-1.2.3/bin/myprogram` in everything that depends on `myprogram` during build time to isolate the build outputs from the system. If you change your store, all those paths will now be invalid, including the hash part.
So using a nix store that isn't `/nix/store` is possible, but I don't think anyone is actually doing it except in a few select scenarios.
You can also compile nix itself with a different root. That will work as expected, but you still have the issue that you need to compile everything you install yourself.
[1]: https://nixos.org/manual/nix/stable/command-ref/env-common.h... (you can also relocate most other directories. The `prefix` in the paths is `/nix`)
Agreed, but it's at least possible. My usual install is just cloning Homebrew to ~/homebrew and setting up a symlink. It's far from ideal, due to the number of packages I need to build from source, but it works, and it's allowed me to function normally in tightly controlled environments.
As far as I can tell, the initial installation for Nix doesn't allow this, though iFreilicht pointed out some options that I haven't seen before, so I may be wrong.
I remember seeing SBCL builds broken on Darwin/ppc for a long while, and eventually SBCL decided to drop support for Darwin/ppc altogether. Still, these ports maintainers did not give up and eventually found a way to fix SBCL builds on PPC: https://trac.macports.org/ticket/65484
I recall seeing some work to bring back PPC support upstream, but I am not sure what the progress on that is. It's still cool seeing downstream users fix builds that simply didn't work (and to the point where upstream decides to remove support entirely since they couldn't build it anyway).
same could be said for pkgsrc I guess. I've used that on other *nix systems; haven't tried it on MacOS yet but the fact it's an option is huge
I’ve also dabbled in this area http://leopard.sh/
there are a lot of scripts out there to mitigate this but the boot-strapping is always a bit of a bother. like the script i wrote, my first instruction was "So... you go download chrome for 10.x for PPC... you can find it here in the old forgotten wasteland of google on a deserted old site that might not exist much longer... "
It’s better suited for a multiuser system (and I share my desktop with my wife who has a different login) and is more stable, too.
port is the standard macOS package manager! port is the standard macOS package manager! port is the standard macOS package manager!
Then I used macports. What a nice experience. Provided what I’m after is listen on there!
The tone with which they write that stuff actually makes me not use it - not because it’s not good (it generally is), I just get annoyed reading it.
LOL dude...
"FAANG" is not the only place to work
All I see is, they protect themself from each and every script kiddy that runs to reddit or github when something doesn't work because of their own config issues.
I'm sure someone will start a macOS package manager based on python and yum to signal the waning days of those technologies.
But it is unmaintained (it seems its author has moved on to Nix).
It reminds me of my boss emailing gnu.org to tell them one of their mirrors was down and got a nastygram back that said "It's spelled GNU/Linux" and the mirror went unfixed.
They don't maintain the mirrors themselves. These are maintained by third party who decide to hosts the mirrors so there is that.
Also, Homebrew attempting to nuke /usr/local on uninstall left a quite bad taste in my mouth. I had installed MacTeX before Homebrew, and thankfully MacTeX had proper file permissions set up, so my TeX installation was left in-tact. Still scary knowing that this is just done in the background without warning (unless the operation fails with errors).
If I could switch entirely to MacPorts, I would.
It would be an interesting discussion to have, as they do have some of that sort of thing (the 1Password CLI, for example), but I don’t know what the general policy would be.
I’d love to see MacPorts get more funding for build resources and to potentially add that, because the way that Homebrew works occasionally leaves things broken (`pipx` venvs are a great example).
…Like I said, language X developers want all their tools to be written in language X, and their package systems too.
As for why Homebrew packages seemed to be broken less often, I can only speculate. At least one big benefit it had was being on GitHub. A lot of folks were already familiar with how to cut a PR. Not so with how to submit a Portfile patch to the MacPorts Trac.
Its being in ruby is a strike against it, for me. I use it anyway. It’s probably my favorite package manager, all things considered, and I’ve used a lot.
But Homebrew's fundamental tradeoff w/r/t purity was also a huge boost to installation speed at a time when most package managers for macOS still required you to build most things from source.
That and the slick, user-friendly UI were probably the biggest factors for Homebrew's success when it came out.
For instance, installing ripgrep now requires building the latest version of Rust from source, which takes three hours per Rust version; installing Pandoc requires building and storing the whole GHC; etc.
My only advice for someone new to OCLP/unfamiliar with Mac boot loader in general (like me one week ago) is that the OCLP boot screen during setup looks very similar to the native MacOS boot picker and went through four different flash drives trying to follow the instructions thinking it wasn't booting properly from the drive. Look closely at the instruction screenshot to distinguish them.
Tcl made some sense ~20 years ago but it’s 2023 and the only time I ever touch it anymore is for MacPorts itself.
I predict that Apple will admit defeat at the very least with Perl, one of the biggest beneficiaries of the Lindy effect. It has entrenched itself so much that you won't just yank it away without some serious bleeding.
Also, there is jsc if JavaScript is what floats your boat, although it's buried quite deep.
why pay for work when it would've been done for free and apple gets to reap the financial benefits?
Also, if you are not going along in the upgrade rabbit race, honebrew gets really annoying and actually in your way at some point.
I see myself moving to macports soon, if brew gets worse and the stability of my setup is compromised (lots of php versions with valet for example).
I guess brew is now more targeted at “prosumers” now since it is imposing unnecessary limits on what “pro” users want and need.
Its more nuanced than that.
As a dev, i like a stable environment and i dont like to do big updates all the time, since that means i have to spend hours updating my setup again. Everytime i run brew im scared it will hose my PHP versions, etc, since it auto updates everything.
To install old PHP versions one needs to hack the install files to make it works.
If you bring up any of these issues you are screamed down by the devs as “you should always be on the latest versions anyway bla bla”… but that is just not a realistic scenario in the real world. Legacy code is everywhere.
In the end brew is not really for pro users, but, as i said, maybe for people using it to install youtube-dl or whatever.
Once the pain of reinstalling and hacking it to make it work becomes too big then i will switch.
I run:
$ sudo bash
# port selfupdate && port -u -c upgrade outdated && port reclaim
once a week.
When I upgraded to Ventura (from Big Sur), I followed the instructions for an OS upgrade and everything moved across cleanly.
It installs itself in /opt
It works with MacOS's Frameworks for stuff like python and java.
It allows you to run multiple versions with "port select".
Why would I want to run anything else?
I for one, am shocked.
Maintainers of popular free, open source community tool are tired of being asked to support out of date OS.
Colour me even more surprised!