Linux

The devs have been working hard to hammer out those troublesome edge cases. There's a lot less of them than there was a year or two ago.

Really? It was very noticable to me when I didn't have screen tairing anymore

That’s NVIDIA’s fault for refusing to adopt the agreed upon methods for rendering graphics on Linux. They tried to force EGLStreams on everybody for almost a decade while knowing GBM was better.

I mean I'm on wayland and nvidia works fine

I just yesterday tried Wayland under Arch with a 1070 after a long time. Single WQHD monitor though. Although X11 is really performant, Wayland was more smooth regarding KDE desktop effects. Witcher 3 (via Heroic) showed fewer microstutters and I will try some more proton games and other applications over the weekend.

I recently had to downgrade nvidia drivers from 560 to 550 because wakeup from sleep and hibernate would coredump. I read that this is fixed with 560 but only under Wayland. The developers definitely progressed on the nvidia front.

That I can understand, however I want to piont out that this is an Nvidia problem entirely. Wayland works perfectly fine under 2/3 hardware vendors.

Luckily, they finally open-sourced their shit so going forward, this will probably change. But chances are only from the 2000 series on, so it might take an upgrade for many folks...

why is there no replacement for x11 forwarding over ssh??

There kind of is. The project you're looking for is waypipe.

Knowing how these things tend to go, I predict you'll try to use it for your use case and it just won't work for whatever stupid reason. But I successfully used it to tunnel an app from my Debian machine at home to a Windows machine under WSL.

All I know is that there are VNC and RDP solutions for Plasma and VNC solutions for Wayland in general.

You can autostart anything on any distro by putting the command in a startup script.

There's libraries like wl-roots that make it a lot easier, no?

Now instead of having Wayland covering everything, applications try to cover every desktops. In the good old times, it worked everywhere.

Why does flameshot need to handle different wayland desktops separately? Because simply the protocol doesn't do it's job. It doesn't cover everything. It's indeed not ready.

I think this is intentional. Call me paranoid.

Elaboration: we have seen in the past how RedHat's and others' policies would always not reach some part of Linux users, and those users still wouldn't feel as second class citizens - it was just a matter of choice and configuration to avoid PulseAudio, systemd, Gnome 3, one can go on. That was mostly connected to escaping major environments and same applications working the same with all of them. Wayland, while not outright making Gnome the only thing to work, creates a barrier and doesn't make that a firm given anymore.

It won't be too long until using Linux without Wayland will cut you off from many things developed with corporate input - and that's developers' time paid as opposed to donated for or volunteered, so much more effort.

Now, there was a time when there weren't that much corporate input and still things would get done. But it will be hard to fall back to it, when the whole environment, one can say, ecosystem, is so complex and corporate-dependent.

I would say this is the time of all those corps whose investment into Linux was so nice in 00s and 10s reaping what they sowed. This wasn't all for free or to profit on paid support. And people who thought that it's GPL that was such a nice license that "forced" corps to participate in FOSS projects they benefit from, with those projects remaining FOSS, are going to have to face reality.

Fat years are ending, so they are going to capitalize on their investments.

This has already happened with the Web 10 or more years ago, when Facebook, Google and others have suddenly gone Hitler, while now they are in terminal stages of enshittification.

Same process.

You can disagree, no need to insult me.