In the end it is Linux's responsibility to make other op systems programs run natively on it and have access to the hardware. No matter what the dev's tell you on the Linux or the Wine side.

Mac OS can run Windows X86 / X64 stuff a few different ways. I doubt Microsoft wrote the code to do so.

Windows can run Linux, Apache, Arm, Android, and many others directly within Windows. And you can bet that Microsoft wrote the code to do most of what is natively supported without some other program to do so.

Linux, well, it can't run much of anything unless a definition and translation is written for Wine, for everything Wine has never run into before.

Remember, Wine is ( W ine I s N ot an E mulator ), it is a translator. And being only a translator, Wine has severe disadvantages in cross op system compatibility. And anything it has never seen, won't run....

Wine is good for many programs because someone took the time to write what was needed for it to work within Wine. But as you know, Wine also has some issues that prevent it from being useful in many ways. Specifically, Linux blocks using or sharing certain hardware on the system.

Linux used to have advantages in areas like servers. But now that those advantages are basically gone unless you write a custom kernel for the specific hardware in your server, or someone already has written it. That is what has kept companies like Red Hat alive, people paying for support and custom kernel mods.

There is little difference in the home pc area now, other than there is no one paying to make it work. 

---

Some things are easy to explain, other things are not........ <- Store ->   <-Freebies->