Granted, it will not integrate with anything hardware-wise by itself (unless there's a package for it - if not, macOS still handles it, and Aqua/Quartz will keep running in the background anyway), but if what you wanted was something that is KDE or GNOME running with its own WM on its own X11 server, doing the exact same thing you'd get if you're running a Linux distro, that's been natively possible for over 15 years.
If a power user loses their power based on what GUI happens to be in front of them, how much of a power user was the power user to begin with?
Also tablet OS? Gnome is keyboard driven with tiling features OOTB...
Being keyboard-driven is nice but doesn't make up for these things, and these days macOS comes with Aero-Snap-like tiling built in too.
I'm tend to think of it as a server os with a DE, but as a backend developer I'm probably biased.
To me, GNOME and Pantheon (elementaryOS DE) strongly resemble e.g. iPadOS or Android running on a tablet for a few reasons:
- Chunky heavily padded touch-optimized UI elements (even when no touch capability is present)
- By default, minimize button not present in titlebars
- Near total abandonment of menubars in favor of mobile-style "hamburger" menus
- By default, no desktop icons (not even an app grid!)
- Simplistic ecosystem apps with mobile-like philosophy of eschewing functionality that doesn't fit in toolbars and hamburger menus
- Little to no presence of progressive disclosure (enabling power user functions to be present without falling in the path of novices and tripping them up)
- Limited extensibility and scriptability (more so than macOS in some ways), with what exists (GNOME extensions) being fragile and breaking constantly due to needing to monkeypatch UI code
While it's not my cup of tea, KDE and even less trendy DEs like XFCE do a better job at acting like an actual desktop environment and surfacing the capabilities of the system.
This is explained by the ElementaryOS H.I.G.:
> Apps should save their current state when closed so they can be reopened right to where the user left off. Typically, closing and reopening an app should be indistinguishable from the legacy concept of minimizing and unminimizing an app; that is, all elements should be saved including open documents, scroll position, undo history, etc.
> Because of the strong convention of saved state, elementary OS does not expose or optimize for legacy minimize behavior; e.g. there is no minimize button, and the Multitasking View does not distinguish minimized windows.