I tried Wayland again and it still fucking sucks. What is even the point? 
@newt what the hell are you people trying to do with x that doesnt work in wayland? idgi, i guess i was lucky because i was running all amd? i used it for gaming and music and programming for years and never had issues. like what features are missing?
@ciel I run all AMD (Threadripper 3970 + Radeon 6900) and KDE+Wayland lags as fuck. No such issue with Xorg.
As for features, Wayland still doesn't allow a program to query a list of available windows and set its own position on screen. This is beyond retarded.
As for features, Wayland still doesn't allow a program to query a list of available windows and set its own position on screen. This is beyond retarded.
@newt ok thats true. very cute. im convinced. i wonder how hard it would be to make work ... there's openbonzi which seems like some sort of xneko clone but not something like that. also in rust, uhg. im so confused why you're having performance issues. i was running a ryzen 3 3200g and an rx560, I shouldve been having issues if you were ...
@ciel maybe my monitors are too big for this stuff to handle (5120x2160 + 3840x2160), I dunno. But I definitely see huge FPS drop when I use Wayland.
With Wayland, those mascots won't work until there's a bunch of protocols merged and implemented. Which might just never happen, because autistic eunuchs from freedesktop keep bikeshedding. For the love of fuck, the simple protocol from KDE that maps Wayland surface ids to dbus ids has been hanging there for three years now. Can you imagine this?
Wayland suffers from all design anti-patterns at once. There's a design by committee, second-system effect, and truly bazaar-like bikeshedding, and all at the same time. Nobody is responsible for the whole thing, but everyone thinks he or she can chip in and make a difference.
With Wayland, those mascots won't work until there's a bunch of protocols merged and implemented. Which might just never happen, because autistic eunuchs from freedesktop keep bikeshedding. For the love of fuck, the simple protocol from KDE that maps Wayland surface ids to dbus ids has been hanging there for three years now. Can you imagine this?
Wayland suffers from all design anti-patterns at once. There's a design by committee, second-system effect, and truly bazaar-like bikeshedding, and all at the same time. Nobody is responsible for the whole thing, but everyone thinks he or she can chip in and make a difference.
