In the long run, hardware is cheaper than your time.
I Used Arch, BTW: macOS, Day 1
41–50 of 110 posts
Re: I Used Arch, BTW: macOS, Day 1
#42Re: I Used Arch, BTW: macOS, Day 1
#43Those apple chips are really quite impressive. But, AMD has those fancy APUs now, maybe it is possible to stay in x86 land a bit longer?
Re: I Used Arch, BTW: macOS, Day 1
#44My homebrew story is always something along the lines of: Me: Please install software A. Homebrew: In order to install it I will also install 20 libraries (some need to be built from source), update openssl, update Python and wreck all virtual environments. Also since its been a while I decided it must be time to upgrade your other unrelated packages. Enjoy!
Nix Darwin is the solution.
Re: I Used Arch, BTW: macOS, Day 1
#45My homebrew story is always something along the lines of: Me: Please install software A. Homebrew: In order to install it I will also install 20 libraries (some need to be built from source), update openssl, update Python and wreck all virtual environments. Also since its been a while I decided it must be time to upgrade your other unrelated packages. Enjoy!
You should use pyenv instead of relying on homebrew for your python version
Re: I Used Arch, BTW: macOS, Day 1
#46I wouldn't try to make macOS into Arch, if Arch is what works for you. Just run Arch in a VM on the mac, using Apple's virtualization framework [1]. (No need for other wrappers; the framework is often easier to use directly.) I find no significant performance issues; a lot of software actually runs faster in a Linux VM than when I compile and run it on the mac. The limitations are that the Linux VM's don't support sa…
I would love to use Arch in a VM on macOS, but Arch ARM is pretty bad. From the installation experience, the frequent stops in updates because something is compiling, to Chromium being broken for months.
Re: I Used Arch, BTW: macOS, Day 1
#47Those apple chips are really quite impressive. But, AMD has those fancy APUs now, maybe it is possible to stay in x86 land a bit longer?
Re: I Used Arch, BTW: macOS, Day 1
#48Earlier quoted context omitted.
I remember when homebrew first came out it was pretty snappy and didn't do a bunch of extraneous nonsense. A remarkably precipitous decline in software quality
Or the rose-tinted glasses have come off. Homebrew is simultaneously a very impressive "my first package manager" experience as well as a chronically deficient packaging solution.
Re: I Used Arch, BTW: macOS, Day 1
#49The Framework has given me a bewildering litany of issues over the years, and I now just want something solid, light, and reasonable battery life, so just I threw down for an M4 Air today.
Having used Linux exclusively for 25 years and an unaBashed CLI junkie, I'm a bit nervous about workflow friction.
How does experience with nixos-darwin compare against just VMing on top of MacOS?
Also, is there any reason for mucking about with Apple's bootloader etc?