In my agency Mac is there because of tradition from developers and designers. More and more developers jump ship to better hardware and use Windows with WLS2 or Linux. Designers tend to stay with the Mac even if they switch to Figma. Some years back it was PS -> Sketch. Now it is Sketch-> Figma massively for a year or so.
An overpowered Windows machine is best suited for gaming, not design work. Vector graphics tools like Sketch work fine on a MacBook. They don’t need a desktop grade CPU with tons of RAM and a powerful video card.
An overpowered machine would definitely be welcome. My point was to emphasize how a crossplatform app would let her take advantage of the opportunity (a new computer I built for one game that I'm giving away) where a native app does very little for her.
I use a Macbook myself and encountered the same thing on the new Windows machine. Every application that was Mac-only was just downside. It made me extra motivated to finished shifting my work environment to crossplat apps like VSCode. And CLI tools that worked well in WSL2.
[1]: https://news.ycombinator.com/item?id=24838816
So I believe both platforms are problematic. Does Windows try to do way more data collection by default? Sadly yes. Is Mac without fault? Sadly no.
Same for videos from YouTube in Safari when they go full screen.
I use Windows 10 for work and Mac OS for personal use and both have their share of quirkiness and bugs. Mac OS is way more mouse based UI and interestingly no one complains about it.
My girlfriend is a UX professional that does most of her work in Sketch. She doesn't care about macOS beyond the fact that it's required by the tools she has to use.
I impulse-built an overpowered Windows machine earlier this year and tried to pawn it off on her, but she didn't even want it because it doesn't run Sketch. She's stuck on a Macbook.
Some people are replying to you saying there are these great benefits to being macOS native, but they really pale in comparison to having to learn something as complex as Sketch. A few familiar component paradigms don't really put a dent in the learning curve, or it's at least vastly overstated. I'd liken Sketch more to Photoshop in the sense that some native components aren't going to make the hard stuff easier.
One practical downside of being macOS-only is that it makes those hard fought Sketch skills less portable and any business that uses Sketch in their pipeline now has a hard platform requirement. Maybe they'll choose something else like Figma. That's something much more tangible to a Sketch professional.
Even VS Code's popularity among developers (the one group presumably sensitive to "native" vs not) suggests how little weight "native" carries with most people. When it's time to get work done, turns out there are more important considerations.
I think you're right, hard to imagine it's a hill worth dying on.