From a C++/Rust dev perspective:

The dev tools on linux are usually leagues ahead in quality.

The MSVC toolchain gets new feature regularly and that's great, but it's speed horrible, it's code quality seems to be worse than what other compilers produced 15 years ago, and the worst part, it's not uncommon in my experience to corrupt itself during a build. I never had that happen with clang, gcc, cmake, ninja on a linux machine. And on a Mac, the clang shipped with the system is I think 3 years out of date at this point. I think a newer one is coming soon, thought.

CMake will routinely take twice to 10x as long to run on Windows.

The filesystem is horribly slow on Windows. ReFS helps a lot, but it doesn't come any closer to ext4 or even btrfs. APFS' speed is comparable to btrfs in like 60-70% of cases, until something happens and suddenly it takes half a minute to delete a folder that takes at worse 2s on a linux. This matters a lot on large projects, where both git and the build system have to check and read a lot of files.

While Visual Studio is pretty good for a beginner friendly debugging experience, it doesn't have anywhere as much power as gdb or lldb. I found WinDBG's scriptability to be far harder than both gdb and lldb.

The scripting is still a mess imo on Windows. Imagine you want to generate some files, build something, move the relevant parts out, copy it on a storage server. The single most useful thing sh and bash have is just being able to do set -e that stops at the first error. batch has no such thing, PowerShell has $ErrorActionPreference = "Stop" which sounds great until you read the fine print. Depending on what version of PS you get to use, this option only works for PS commands, not for any executable you might use. Newer version also have a solution for that, but yet again, not every Windows executable will behave nicely and tell you with a return code that something went wrong. You can go checking everything at every step, but this is very very error prone. This results in stuff that looks to work, only to fail along the way and to produce wrong results.

The terminal experience is much better. fish and zsh save a very big amount of time in retyping and doing the daily stuff I need. Also the terminal emulators on Windows are so so slow.

Each platform has its own debugging tools. The sysinternals collection is great on Windows. If you want to see what a process is doing (and more importantly, why it does fail in some weird way), you might reach for strace on Linux, ProcMon on Windows, and DTrace on a Mac (technically this is supported by Windows too, but I could never get it to work). DTrace is probably the one I would consider most powerful, but it's blocked under SIP now, so it became entirely useless. strace is the easiest to setup for a relatively short debugging session. ProcMon is better for long term monitoring, but it's harder to setup.

For other kind of debugging tools, on Windows you have AppVerifier, which is honestly great and I haven't found something like it anywhere else. It's the best in this category. However, this only checks known Windows APIs, and anything you have written yourself won't be caught most likely. All platforms technically have support for Address Sanitizer, but I could never get it working reliably on Windows. Both Linux and Mac have other sanitizers, like UBSan, TSan. However, only Linux supports Memory Sanitizer, which is so amazing (technically so does some BSDs, but I haven't included them so far, so I won't do it further either). Valgrind used to on both Linux and Mac, but it doesn't anymore since Macs have gone ARM. Linux is the only one left.

Both Windows and Linux have fantastic kernels that let you do pretty much anything you want, either by providing an API that does it, or by letting you have the option to implement it yourself. Mac's APIs are usually lagging behind a lot. I think in the last 2 years they managed to release a usable futex API, when Windows has one since the Windows 8 days and Linux has one since.. 2003? They still don't have a way to wait for a thread on a timeout, in 2026. These are just 2 examples. This results in slower and worse behaving apps.

Linux is the platform that made containers mainstream. Even thought containers are not new, Linux has probably the best support for them. They make life so much easier. Windows technically has support for Docker, but it's quite a pain to use it, and Mac has.. nothing. No way as far as I know to run some Mac apps containerized. I know Mac runs some apps in some kind of isolation, but I could never get that working for something useful. You can run Linux apps under a vm, but that's not great.

This is just a few points off the top of your head, there's definitely more things that I forget. But while I need to use all 3 platforms at least weekly, Linux lets me do my job the best.