3 ms·

I do not like how ready the big spenders in the Linux sphere are to push wayland into every crack, considering: 1. It consistently breaks closed-cource softwar

I do not like how ready the big spenders in the Linux sphere are to push wayland into every crack, considering: 1. It consistently breaks closed-cource software that I need to use in education like Mathematica and MATLAB 2. It requires tweaking to work with Flameshot and related screenshotting software 3. It breaks emulation layers like Wine and Proton (or significantly decreases performance). This was a dealbreaker since I managed to move almost completely to Linux for gaming. 4. It does weird things with scaling. I used to use three monitors (two 1080p above one another and a 1060p to the side) and it always did weird things if I tried to span windows across it. 5. It still is not working properly on Nvidia. There is a problem with these technologies where the leaders are reinventing wheels and making them square in the process, acting like past paradigms are completely useless and that you're ridiculous for even questioning the departure from status quo. And because big entities like Microsoft, Red Hat, Fedora, Canonical etc. spend money on them, the main users have little say in the features developed. Desktop finally got to a reliable and comfortable point with software compatibility and usability, but now we have a ton of people funded by the EmbraceExtendExtinguish crowd pushing a new desktop protocol stack that obviously breaks things.

tapoxi 3y ago
1) I haven't used these, but I assume newer releases will be native to Wayland. 2) This is because you need to make an API call to the compositor to capture the screen. This is a one-time change unless you're using a very old application that hasn't had Wayland support added in the last decade. 3) It doesn't significantly impact Wine/Proton performance. In fact the Steam Deck runs a Wayland compositor (Gamescope) with the games under XWayland. Valve is porting Wine/Proton to support Wayland natively. 4) This isn't up to Wayland but up to the compositor. 5) This is Nvidia's fault for trying to force everyone else's hand by using their driver API model of choice for years until only recently capitulating.
- charcircuit 3y ago
  1) They should work in xwayland

tapoxi 3y ago

1) I haven't used these, but I assume newer releases will be native to Wayland. 2) This is because you need to make an API call to the compositor to capture the screen. This is a one-time change unless you're using a very old application that hasn't had Wayland support added in the last decade. 3) It doesn't significantly impact Wine/Proton performance. In fact the Steam Deck runs a Wayland compositor (Gamescope) with the games under XWayland. Valve is porting Wine/Proton to support Wayland natively. 4) This isn't up to Wayland but up to the compositor. 5) This is Nvidia's fault for trying to force everyone else's hand by using their driver API model of choice for years until only recently capitulating.

charcircuit 3y ago
1) They should work in xwayland