Until you need/want some project that's relatively new and you pine for the days of brew. Technically inferior Perhaps but often much more up to date. :/
I heard great things about AUR when moving to Arch but honestly I've been unimpressed. A lot of stuff is already exists in official repos for other distributions, and I don't actually care about bleeding edge versions, just ease of install. And most of the time in my experience, AUR packages aren't very recent, or aren't configured how I'd like.
That said, you can just customise the PKGBUILD yourself, and even then it's no real stress to build from source yourself. Even if you then stabbed yourself in the eye with a pencil, it'd still be a better system than on MacOS or on Windows.
The problem I find with Arch Linux, and this really only has started happening recently, is that for some reason Arch loves to break stuff. My most unstable distribution had to do with Arch. I find that distros like Void and Alpine Linux offer more robust rolling release systems.
What in particular has broken for you? I've had the same Arch install for almost 6 years now, with no breakage at all. (Other than once or twice when I decided to reconfigure something and screwed it up. Always recoverable though, without a reinstall.)
I personally find that Alpine offers the least robust, because it doesn't even have a package mirror, so once a package gets updated (especially in Edge), then you can no longer download the old package, unless you build and sign it yourself. Arch has been incredibly stable for me, even more so than Ubuntu or Debian.
I always assumed this is because Linux package managers such as apt and yum are first-class citizens on the platform, while Homebrew is a bit of a de-facto solution on macOS.
No, macports is non-native as well and is an excellent, stable alternative, although Homebrew has slightly better coverage. Homebrew's main issue is that it was written from scratch, ignoring lessons from 30+ years of package management experience, and there's no obvious benefit that doing so has brought. Compared to macports, which is based on freebsd ports, Homebrew is brittle and normal operations frequently result in an inconsistent state.
In my experience, unless your needs are extremely basic, sooner or later you'll run into an issue where the solution is basically to commit nuclear warfare on your filesystem and start over again. Also, expect to rely on random blog posts and stack overflow as the de facto user's guide (which maybe is just the state of the world for everything now.)
As to Homebrew, I don't understand why it complains if I use sudo to do an install but then also complains if I'm not running as an admin account! If there's a reason for this splitting of hairs, I don't know what it is.
shrug use Mac for the generally superior UI, interface hardware, and app ecosystem, ssh into a Linux VM/server/workstation for the generally superior development experience. Best of both worlds.