4 ms·
I envy your patience. I had to drop MacOS altogether out of frustration that there were no good package managers, and VMs simply don't cut it for me. Nowadays,
by smoldesu 5y ago
I envy your patience. I had to drop MacOS altogether out of frustration that there were no good package managers, and VMs simply don't cut it for me. Nowadays, I run an inverse setup: I do pretty much everything in Arch, with a few Wine prefixes to solve Windows compatibility, and a healthy combination of Darling and QEMU to spin up MacOS instances.
- Svetlitski 5y agoGenuinely curious, what didn’t you like Homebrew (assuming you tried it)?
- heavyset_go 5y agoAnother HN user did a write up on Homebrew[1] that I agree with. My main gripe is that Homebrew would regularly break my Python virtualenvs with linking errors. Meanwhile on Linux, I have virtualenvs that I created 9 years ago that still just work. These days you might be able to sidestep that issue by not using Python from Homebrew at all, but installing and managing it with Pyenv instead. [1] https://saagarjha.com/blog/2019/04/26/thoughts-on-macos-package-managers/#to-sudo-or-not-to-sudo https://saagarjha.com/blog/2019/04/26/thoughts-on-macos-pack...
- Groxx 5y ago`brew pin python` and it'll stop that from happening. but yeah, this is a constant source of pain, and I end up helping people at work fix it probably on a weekly basis (or more often). python bin-envs are such a hassle.
- heavyset_go 5y agoI need to run the latest Python versions, including alphas and betas, though, and have everything just work even if the system and local Python versions change under me. Pinning Python would make it difficult to contribute to CPython, or make sure my libraries work with new Python alpha/beta releases before stable versions are released. Virtualenvs based on Pyenv's local Python installs on Linux works well, and virtualenvs that were based on old system Python versions still work even when I upgrade the system Python. This is where I'd get linking errors with Homebrew that I don't get with Linux.
- Groxx 5y agoat this point you're far beyond the intended use for a widely used package manager. install a stable python somewhere by hand and keep it there ¯\_(ツ)_/¯
- viraptor 5y agoDoes Darling work for anything serious these days? What apps are you running on it?
- handrous 5y agoMeanwhile, I find macOS sticky in part because of the package manager (homebrew). In particular, I've not seen a package selection so good and so consistently up-to-date, with so very little fiddling or upkeep to add or maintain 3rd-party repos, since I was on Gentoo—and portage broke (in whole, or just had broken individual packages) a lot more than homebrew does (which is almost never). I can't think of a single thing I use that isn't available and well-maintained on it, open or closed source. Even obscure things often just install on my first guess at the package name, no muss, no fuss. Now, what I don't use it to do is to manage project dependencies, but then I don't like using, say, the "system" PostgreSQL or Nodejs or whatever even on Debian, either, unless I'm using them directly and not making them part of a project that will need to be distributed or deployed elsewhere and worked on by others. I'm entirely fine keeping core OS parts, my personal software I use, and management of individual project dependencies, strictly separate—in fact, having worked this way, I prefer it. I could be tempted away by a similarly-great and high-quality package selection, maybe, but that would be table-stakes before we even get into the rest of how the package manager operates.
- smw 5y agoJust fyi, you can use homebrew on linux.
- handrous 5y agoYeah, but it's got a much smaller set of packages available and, last I checked, had a lot more issues with broken packages and things like that (I assume because there are fewer eyes on it, and way less total time spent on maintenance of it)
- smoldesu 5y agoAre there any packages that exist on Brew, but not, say, APT or pacman?
- handrous 5y agoOn macOS brew? Yeah, tons. To even get somewhat close with Ubuntu or Debian you'd have to add a bunch of non-standard package repositories, and because of the way most Linux distros tie up user-facing programs with system releases, you'd have to do similar to stay up-to-date on packages that are in the default repos. Arch does much better, but a quick search of ones I guessed might be missing turned up the following missing, from what I have installed on my Mac: - rolldice - android studio (package name android-studio in homebrew) - tealdeer - heroku (these are the Heroku command line tools) - sublime text (package name: sublime) - postman - slack Maybe you can add other repos to get them on there, but I usually just guess the package name and get what I want. I don't think I have a single thing on my Mac, as far as software I directly use (not project dependencies), that I didn't install with Homebrew, aside from first-party Apple software (Pages, Numbers, Safari, Xcode, Mail, and so on). And that's not bringing up all the Mac-only software I've installed with it, which obviously wouldn't be fair. I haven't added a single extra repo. That's just with the defaults. You used to have to do a one-time invocation to enable binary-only packages (mostly closed-source stuff) and then use a different keyword for operating with them, but that's no longer the case and hasn't been for IIRC at least a year—it's all transparent. "brew install [guess at package name]" works almost every time I need it, and a "brew search" finds the rare failures. I basically never need to open a browser to find & download software, and it's all up-to-date, and it's all totally separate from my base system so is extremely unlikely to ruin my morning because I ran a blanket update-everything-to-latest and didn't pay enough attention.