Windows, on the other hand, not only has special characters that cannot be used but also reserved words that cannot be used as file names (eg COM). Then there’s the issue with magic file extensions and even Windows Explorer hiding extensions entirely by default.
On balance I prefer Linux’s approach. Sure it creates some problems but they’re easy to be worked around and usually only rear their head when you start using lesser polished UIs or shared file systems with Windows. Plus Linux empowers you to use those names if needed, or change them if it’s a problem. Whereas Windows has these weird hidden show stoppers - many of which were only relevant in the days of DOS but have been carried forward in every iteration of Windows since (including NT) for compatibility reasons. That causes way more problems to developers - which is my personal use case.
https://docs.microsoft.com/en-us/windows/desktop/fileio/nami...
Worst scenario is you’re dealing with a non-technical team but in those instances you’d keep your storage centralised and use an NT based solution (or something with first party support for AD) so you catch any Windows related bugs at save time rather than further down the road when you need to access them again. Given file names in Windows is limited by both the file system and the OS, whereas Linux is limited only by the file system, all you really need to do is catch those Windows-related errors. So running an NT-based storage array would solve that problem.
Which one? There's a crapton.
PS - "evil" is not a religious term, it's actually the substitute for a religious term, which is "wickedness" (see Widipedia.)
Sounds like your graphics card doesn't work well with Linux. Is it Nvidia ?