Earlier quoted context omitted.
For me: - No nagware (no Apple Music pop-ups, advertisements for safari, login nag in settings, et. al) - Built-in package manager - Having (relative) parity between production and development Between those three, you probably couldn't pay me to go back to MacOS. Adding my own package manager, disabling ads and making my Mac into a Linux-equivalent machine is possible, but it's a lot of work to maintain and set up. I…
I have an M1 Pro MBP and Linux running on a Framework laptop. The Linux built in package manager is only ok. It often lags behind in versions of things I need. I ended up using Homebrew on both Mac and Linux. For the cases the Linux built-in package manager is too out of date I use Homebrew. It's not perfect on either system. > - Having (relative) parity between production and development For certain classes of devel…
I’d also not be opposed to a package manager more geared towards making sure things work without fuss than trying to reduce redundancy. I don’t really mind if there’s multiple versions of whatever lib installed if that’s what it takes. Storage is cheap, my patience isn’t.
In theory flatpak and such should meet that need, but the implementation is so much more quirky and troublesome compared to e.g. Mac application bundles.