Originally posted by Master5000
Also, you can't build a fully running, 64-bit version of VLC on Windows natively; VLC insists that the i686 versions of mingw be used for native compilations, and let's not ignore the fact that msys2, no matter how good it is, is still not a true Linux layer on Windows and will fail to build certain software packages or libraries if compiled using the default autogen.sh, ./configure, make and make install procedure due to differences between it and a real Linux operating system. Even the Windows-native MPC-HC demands that mingw-i686 be used. This applies for many other OSS software out in the wild for Windows as well.
Finally, old drivers may not install in newer versions of Windows if the driver INF file explicitly declares that it's meant to be run only on a specific version (e.g.: NT 6.0) and needs to be quite extensively edited to force an install on newer Windows, sometimes with lots of other issues as well. In addition, Windows 8 and onwards mandate driver signature verification, so you'd need to reboot to the Windows Advanced Recovery mode, disable driver signature verification for that one session just to install the modified driver. Not fun.
But for everything else, Windows just wins hands down. Look at the number of Thunderbird forks out in the wild for Windows with a GUI vastly superior to that of Thunderbird. Even for most OSS software out there, the Windows version always launches and initializes faster than the Linux version. Proprietary hardware drivers often have much more advanced power saving features and functionality compared to the open drivers on Linux, or even their Linux proprietary counterparts. And Windows can even recover from a kernel driver crash, whereas in Linux it brings the whole system down.
Comment