3 ms·
Nobody has said it, but it seems we are reaching a fork in the desktop? For users, not 'right' and 'wrong' here, just two groups whose goals differ. Those sup
by zbuf 6y ago
Nobody has said it, but it seems we are reaching a fork in the desktop?
For users, not 'right' and 'wrong' here, just two groups whose goals differ.
Those supporting X.org are using X very much in the spirit of it; custom window managers, network transparency, and possibly bitmapped fonts, BSDs.
And those in support of Wayland have arrived there via Linux with eg. GNOME and dominated by GTK and QT desktop apps; looking for an open-source offering with the same functionality as Mac and Windows desktop.
Really, this has been brewing for a while. It's been a fluke that the underlying X has allowed these two groups to co-exist.
- swiley 6y agoOne more nice thing about X that people sometimes miss is that you can turn off compositing (this is the default really.) Lots of people say Wayland feels "sluggish" and this is likely a major contributor to that. Especially if you don't have hardware acceleration (and there are a huge number of reasons why that might not be working.) Wayland solves a lot of problems by deciding to just not handle things but we have to recognize that taking that position sacrifices things.
- zbuf 6y agoYes, I am also not using compositing, which I always assumed means apps render direct to the framebuffer. Does this mean that moving to Wayland (or its implemenation) is going to add 1 or more frames of delay to my output? This could be a part of why I have always found other modern systems to be less snappy than my own X desktop.