Cries in game dev

No, seriously. I've tried getting Unity to work on Linux once, and gave up after few hours of random crashes, bugs or errors. And I never even got to building the game, which I'm sure would be an entirely different adventure that would still in the end require to reboot to Windows and try the build there.

Also, getting O365 to work on Linux was another reason why I eventually gave up, since our company is simply a Windows-based, and the web apps are just too cubersome to use. And for alternative clients you usually need an app password (disabled in our domain) or another setting that you don't want to enable for 95% of your employees, since it's just a security risk in the wrong hands.

Oh, and then there are VPNs. I never managed to get Checkpoint mobile working on Linux, without it also requiring intervention from IT to enable some obscure configuration or protocol support.

It's a shame, but every attempt I made to switch ended exactly the same - after few days of running into "make sure to enable this config on the server side" or "if you don't see that option in the settings, contact your system administrator" for every tool I need for my job, I just gave up.

But I'm considering it giving it another try, and just go with the Unix + Windows VM for administrative tasks. But knowing myself, just the small hurdle of "having to spin up a VM" would be a reason to postpone and not do it properly, since that's additional effort... And then there's still the gamedev I do part-time, where I simply don't believe it's a good idea - after all, given the states the engines are in, it's a recipe for disaster of "works on my machine but not in build" or "doesn't work on my machine"...