Earlier quoted context omitted.
That’s not that far from the reality. It’s essentially like using a Linux with really good graphical UI, ecosystem/3rd party integrations that just works and fully supported stellar hardware. After all, macOS is certified Unix and Linux is Unix-like.
As a Linux user who has run a Mac daily for work before, I don't really feel this at all. To me, the core of the Linux experience consists mostly of things that are not part of macOS: - uniform, comprehensive, robust package management, including for the system software - GNU coreutils and related utilities (sed, grep, find, etc.) - good filesystems - 'root is root'; no policy or other bullshit restricting what root…
> uniform, comprehensive, robust package management, including for the system software
Every Linux distribution has its own package manager, so that somewhat fails on the 'uniform' point. Package management for system and apps being shared (comprehensive) is an arguable point as well, and 'robust' seems to not be the default on more traditional Linux distributions.
The approach seen in for example Fedora Atomic matches the macOS approach a lot more, including rollback and consistency, but also splitting the system image, overlays, and user apps.
> GNU coreutils
Not all Linux distributions have these, either, busybox distros seem fairly common these days (and offer most the popular switches you'd see with GNU utilities).
In addition, of course, the GNU utilities run under any UNIX-like, so if you do need any of the convenience switches you're used too, they exist anywhere as well.
Again, of course, subjective.
> good filesystems
APFS seems 'better' than the ext* default seen on most Linux distributions, and has had less of a history of 'random corruption' than early btrfs.
> 'root is root', ...
Red Hat-like distributions (and even Ubuntu) seem to by-default enable some kernel security module, which have the same effect.
The implicit UID 0 bypass is nasty for security.
> lots of .. terminal emulators
I'm not a picky terminal user, but macOS Terminal.app nowadays seems to match, say, gnome-terminal or Konsole quite well in behavior.
Perhaps it doesn't support some fancy feature set, but I'm not sure if the main DEs do either.
> some choice in desktop experience
Valid point. However, if you prefer something as uniform as the macOS experience, you can't get that on generic freedesktop Linux.
> popular apps don't just entirely stop working
Depends. The typical Linux distribution has a nasty ABI as well, often only guaranteeing source compatibility.
This is indeed often easier to work around even for binary-only Linux apps (on a multilib amd64 system, you can usually run some libc5 app from the late 90s fine. on macOS, this is 4 CPU architectures ago and you won't even stand a chance).
> pretty much everything is discoverable and configurable if you're determined
Same goes for macOS and even Windows. Reverse engineering is a thing that can be done with sufficient determination, and in many legislations has exemptions for these kinds of use cases.
macOS and Windows also offer symbol names for a fair amount of OS components, it's just perhaps a little more work than 'grep the source code for a flag'.
In the end, however, it's all a matter of tradeoffs and what you're used to (i.e. won't have to waste time learning before being able to get work done), and if you're used to something that varies from the default of any system, this is less and less likely with macOS or Windows.