High DPI screen support in Linux is still troublesome, especially between multiple screens with different DPI/resolution, especially between GTK and Qt programs.
And I haven’t played around with Asahi yet, but it’ll be hard to top the built-in power/suspend/hibernate/resume behavior and its effect on battery life (especially in being able to just count on it to work if you suspend for days, where it seamlessly switches to hibernate and starts back up very quickly). But on my old Intel MacBook, the battery life difference between MacOS and and Linux is probably two to one. Some of it is Apple’s fault for refusing to document certain firmware/hardware features, but the experience is the experience.
Yes, software that is in a package manager is similarly easy on a Mac. There’s an app store, which can be used to install the dependencies for homebrew (which is a good package manager for most of the stuff that Linux package managers maintain, including building stuff from source). Going outside of a package manager is relatively easy (but needs to be enabled, as the defaults basically discourage users from installing software not verified by Apple), but that method of software installation still beats running .exe/.msi installers downloaded from the internet, beats running random shell scripts, probably beats downloading docker containers and flatpaks, and is not that far removed from installing from the AUR or something like pip/conda: you still need to know what you’re doing, and you have to trust the source/maintainer. None of that is unique to any operating system, except those that simply don’t allow you to install software not reviewed/approved by the manufacturer (Apple mobile devices, Android devices by default).