I love using my macs for development, but I would not say that it's "very similar to linux". Having to go out of your way to install a package manager is one of these things.

WSL is close enough to linux that a lot of docs just add in a little note for WSL users to follow linux instructions instead of windows.

I don't even think it should be a design goal to perfectly simulate the Linux interface. MacOS nix underpinnings are much more BSD than Linux. Yes, a package system like homebrew needs to be installed, but on the plus side you can choose if you want homebrew or macports.

There's no getting around it, we have to individually learn all of the systems that we're on. Every time I'm on a linux system (I mostly use BSD) I'm badly thrown by systemd. This is my fault--I need to learn it--but it's always annoying to have to relearn how to do basic tasks on a similar yet different system.

I agree about the need to simulate Linux isn't always desirable.

However the need for a package manager is obvious, even Windows (itself, not WSL) has come around to recognizing this. Yet we still have to rely on a complete third party for such on mac (thankfully, we have open source options, at the bare minimum). Surely Apple can come up with something! Especially since afaik the brew maintainer failed to get past the interview process at Apple, surely they can do better!

> Especially since afaik the brew maintainer failed to get past the interview process at Apple, surely they can do better!

Is this really your litmus test? What other Company/Manufacturer do you hold to the same level as Apple?

Any developer that creates 3rd party software that’s not hired by the OEM must be shit?

No, you're misunderstanding me. I'm stating that if Apple doesn't even think the maintainer is good enough to get hired, surely they can produce a better solution than him. This doesn't indicate that the 3rd party developer is shit at all, not sure why you would assume such.

Perhaps don't leap to negative conclusions so abruptly.

> This doesn't indicate that the 3rd party developer is shit at all, not sure why you would assume such.

Perhaps don't leap to negative conclusions so abruptly.

You’re correct I completely took your words out of context and weaponized my frustration. I apologize.

Does sed -i work on macOS these days? It works great on WSL.

The macOS toolchain sucks and typing in gsed all the time sucks even more.

Your beef appears to be with BSD. And when you install the GNU tools it tells you how to setup your path to not have the prefix.

Yes, the GNU toolchain is leaps beyond BSD.

Ah yes, and then plenty of scripts that assume BSD sed break.