The people building the many thousands of native Windows apps used by millions of people every day.
CAD/CAM systems. GIS applications. Automatic teller machine software. Public safety dispatch systems. Automotive diagnostic tools. Point of sale systems. List goes on.
While these systems are often written for Windows, there's actually very little reason to do so, and typically you're doing yourself a huge disservice.
Yes you can build a POS system using Windows tech, but you don't really gain much by doing so, other than a whole host of headaches when it comes to deployment and administration.
This is only remotely true for embedded systems, where you ship a fully integrated device, with all its associated peripherals as a turn-key system that does not have to interoperate with anything else.
If you’re in the business of shipping software that needs to run alongside other people’s software on the same machine, it’s a disaster.
Linux userspace backwards compatibility is extremely poor, the “solutions” to this issue (Flatpak, Snap et al) generally create more management problems than they solve. Desktop Linux is already an absolute monster to manage.
Try securely deploying hardware-backed PKI certificates for 802.1x to a fleet of Linux workstations. Takes a couple of minutes on Windows and macOS, but it’s a massive engineering effort on Linux.
CAD/CAM systems. GIS applications. Automatic teller machine software. Public safety dispatch systems. Automotive diagnostic tools. Point of sale systems. List goes on.