How is Wayland “ready” when critical things like idk, non QT apps quiting when the compositor crashes (and thus losing progress!) are called a “non showstopper”
@klangcola I'm not commenting on whether ot should be a show stopper or not. Just that it will eventually come also for non-Qt apps with MRs from KDE contributors to other projects.
its not listed as one is the weird thing, because it totally should be
imagine drawing and suddenly your compositor crashes leading to your program to crash and you to lose hours of progress, but other QT programs are fine
should’ve used krita because that’s QT except you cant replicate your workflow in that program because it misses features (and also you dont like it)
This is a real scenario I would have to worry about. That’s a showstopper for me
@Zamundaaa@mnglw xorg Apps don't crash when the compositor crashes, you can just switch out compositors/window managers. But xorg Apps crash when the xserver is crashing
Wayland isn’t perfect, but it’s definitely getting there.
I think one of the biggest migration problems is that things have to move from the windowing system to the desktop environments, and they’re slowly adapting to it.
lokalize (Translation tool) is, only application for me, not working with Wayland at all (There is bug reported about it). I am using KDE with Wayland on my daily laptop.
pointieststick.com
Oldest