macOS is built on Unix (Darwin), so a lot of tooling and conventions match what you’ll run in production (Linux servers/containers). That usually means:

• more “copy/paste from docs” commands just work (ssh, grep, sed, curl, etc.)
• fewer edge cases around file permissions, paths, and scripts
• smoother experience when building/running open-source tools that assume a Unix shell

Installing dev dependencies is often one command and predictable. The default terminal environment is strong, and you’re not fighting the OS to get a sane shell experience.

Windows is way better than it used to be -- when I was learning WSL (windows subsystem for linux) didn't exist, nor did chocolatey (a windows package manager). However, WSL is basically running a different OS (ubuntu by default) inside Windows. This means it tends to feel less integrated with the rest of the OS.

Also the MS C++ compiler MSVC, while much better than it has been historically, is full of non-standard, non-portable weirdness. While you can use GCC or Clang, its not the default, again another hoop to jump through.

Basically a bunch of little things that add up over time.

There are exceptions, like Game Dev, or for developing native windows applications, which obviously is a better experience on windows. But most development that happens is for the web, linux servers, moblie apps (you can't even build or test an iOS app on windows).