I've been using Linux exclusively for about 8 years. Recently I got frustrated with a bunch of issues that popped one after another. I had a spare SSD so I decided to check out Windows again. I've installed Windows 11 LTSC. It was a nightmare. After all the years on Linux, I forgot how terrible Windows actually is.
On the day I installed the system and a bunch of basic software, I had two bluescreens. I wasn't even doing anything at that time, just going through basic settings and software installation. Okay, it happens. So I installed Steam and tried to play a game I've been currently playing on Linux just to see the performance difference. And it was... worse, for some reason. The "autodetect" in game changed my settings from Ultra to High. On Linux, the game was running at the 75 fps cap all the time. Windows kept dropping them to around 67-ish a lot of times. But the weirdest part was actual power consumption and the way GPU worked. Both systems kept the GPU temperature at around 50C. But the fans were running at 100% speed at that temperature on Windows, while Linux kept them pretty quiet. I had to change the fan controls by myself on Windows just because it was so annoying. The power consumption difference was even harder to explain, as I was getting 190-210W under Linux and under Windows I got 220-250W. And mind you, under Linux I had not only higher graphical settings set up, but was also getting better performance.
I tried connecting my bluetooth earbuds to my PC. Alright, the setup itself was fine. But then the problems started. My earbuds support opus codec for audio. Do you think I can change the bluetooth codec easily, just like on Linux? Nope. There is no way to do it without some third party programs. And don't even get me started on Windows randomly changing my default audio output and trying to play sound through my controller.
Today I decided to make this rant-post after yet another game crashed on me twice under Windows. I bought Watch Dogs since it's currently really cheap on Steam. I click play. I get the loading screen. The game crashed. I try again. I play through the basic "tutorial". After going out of the building, game crashed again. I'm going to play again, this time under Linux.
I've had my share of frustrations under Linux, but that experience made me realise that Windows is not a perfect solution either. Spending a lot of time with Linux and it's bugs made me forget all the bad experience in the past with Windows, and I was craving to go back to the "just works" solution. But it's not "just works". Two days was all it took for me to realize that I'll actually stick with Linux, probably forever. The spare SSD went back to my drawer, maybe so I can try something new in the future. It's so good to be back after a short trip to the other side!
They're things like drive mapping scripts, stuff like that. They're definitely normal for our setup. Just not sure why they have to interrupt me!
The fact that Windows devs seem to not know how to run tasks hidden and in the background always bothers me. I’m sure it’s the fault of Windows itself, but Linux doesn’t open jack until I tell it to. With all the extra helper programs needs in the tray to run all the proprietary hardware, I about lose it with all the shit popping up to yell at me.
It's very easy to run things like scripts in the background. Showing a command/powershell windows because of a drive mapping script is amateurish (and very annoying). Usually scripts like those are run on logon.
We have an automation server at work that runs a bunch of scripts for all kinds of stuff. It just uses task scheduler. Hiding the script output is as simple as telling it too. We have a lot of servers at work that run important production shit interactively. So someone has to logon the server and start the problem.
It's utterly disgusting. I recently introduced them to NSSM which can run simple programs as a service, which entirely solves the problem. But it's bizarre that no one else has suggested that before, or found some other solution.
Fortunately, I'm not responsible for prod applications running on those servers, it just really fucks with our patching procedures.