Also, none of those kludges would have even been necessary if the project scope was properly defined from the start and the project manager didn't let the users keep trickling in new requirements without also extending the deadline.

So yeah, how dare I go back and implement something the way it should have been done the first time?

you are viewing a single comment's thread
view the rest of the comments

[–] PrinzKasper@feddit.org 4 points 4 months ago* (last edited 4 months ago)

About a year ago I tried switching to Linux and used Linux Mint exclusively for about a month and a half.

I have multiple monitors with different refresh rates, one 144hz and a 60hz monitor. The problem is that the compositor runs at the lower of the two, for both monitors. In theory it should be possible for a full screen app like a game to bypass the compositor completely, but I could never get that to actually work, games running in both exclusive full screen and borderless were kneecapped to 60hz video output because I had the audacity to have a secondary monitor connected. But even if that did work correctly, regular desktop use would still be kneecapped. Admittedly not as important, but still annoying. I ended up having to use a hacky config tweak to force the compositor to run at 144hz, which worked but also caused tearing on my secondary monitor.

On top of that, X11 straight up does not support VRR / G-sync if you have more than one monitor. And HDR? Completely unsupported.