> macOS for anything that might qualify as work

FWIW, a lot of "work" areas are still deep into Microsoft Word, which works a lot better on Windows.

Yeah, that one's heavily dependent on what one does. Software availability rules all, for that choice, and one only really has a choice if some certain minimum level of that is met by more than one OS. If I were developing deep server-side VM tools, or drivings, or what have you, I might find using a Linux or BSD workstation well worth the hassle. Embedded dev, macOS probably isn't a realistic choice, and maybe not even anything other than Windows, depending on hardware vendor support.

But when I write or compose documents, I don't need MS Office interop, and it'd probably be my 3rd or 4th choice of "suite" for that kind of thing, behind the Apple's versions (mostly because they have great default templates, are very stable, are fairly easy to use, and are very light on system resources), Abiword/Gnumeric and other pieced-together open source options, and maybe LibreOffice in 3rd place. But, if I had to pass around Office documents, that'd be another story.

Probably my main pain-point on Mac, as far as work-stuff goes, are under-developed virtualization tools. They have a hypervisor, but it's a pain to use and there's almost no community around it. No simple way to pick an earlier version of macOS and virtualize it, even. VirtualBox is... OK. Barely. 3rd party commercial options improve the situation a ton, but you get much better tools out-of-the-box on basically every other at-least-semi-viable workstation OS.