Originally posted by bug77
View Post
Announcement
Collapse
No announcement yet.
Wayland's Wild Decade From v1.0 Release To Usable GNOME/KDE Desktop Support
Collapse
X
-
-
Originally posted by 144Hz View Postduby229 There’s no misconception. Mutter on Wayland Just Works(tm). There’s a lot of code and mindshare between Mutter and Weston so that’s kind of expected. I have no problems with Wayland. It’s well architected and doesn’t suffer from scope creep.
People should stop blaming Wayland for their poor choice of Wayland compositors.
Wayland=simple.
Compositor=complex.Last edited by duby229; 30 December 2019, 03:56 AM.
Comment
-
Originally posted by 144Hz View Postduby229 Wayland’s simplicity is a deliberate design feature. Besides technical merits it comes with many other benefits. Gone are the days where protocols need to deal with other desktop compositors’ quirks and poor design.
No more bastardizing “standards”. Just pure Mutter. And it comes with no downsides. The remaining desktop X resources just moved to work directly on Mutter instead.
Comment
-
The main bulk of the work (because Wayland has such a trivial useless scope) needs to be done by individual compositor developers (almost like the WM developers of X11). These are tiny teams and can simply not manage to provide a robust solution if they have to do it all from scratch. This is where a "Weston compositor SDK" comes in handy. Unfortunately these are all currently crap too.
Its all crap, crap, crap XD
The only benefit I can see is Wayland eliminates the overwhelming choice of Window Managers / Compositors because they become too hard to develop. Unfortunately I imagine many Linux users will not like this. However reducing fragmentation is good for the enterprise.Last edited by kpedersen; 30 December 2019, 08:52 AM.
- Likes 1
Comment
-
Originally posted by CommunityMember View PostEGLStreams is a standard. So is GBM.
Originally posted by 144Hz View PostJust pure Mutter.
Originally posted by 144Hz View PostAnd it comes with no downsides.
Originally posted by 144Hz View PostMutter is doing well so no one can claim they are left without options.
As others have said, the core protocol is so narrow in scope that you can't create a fully functional environment without additional private protocols that each compositor has to reimplement over and over again, and so nothing is compatible with anything. Yay, fragmentation! wayland-protocols helps a little here, but even that is far from complete and then you also have compositor devs refusing to implement things that are part of wayland-protocols (like xdg-decoration <- and spare me your "CSD uber alles" mantra, if CSD was the answer to everything, xdg-decoration wouldn't exist).
- Likes 1
Comment
-
With proper standards and well-defined protocols there can be as many compositors as people feel like creating, and it won't cause fragmentation because the protocols will ensure interoperability.
- Likes 2
Comment
-
Originally posted by starshipeleven View Postcreated by NVIDIA on the fly and not used by anyone else but them. Technically right but in practice it's bullshit.
In this particular case, it seems GBM has acknowledged drawbacks (performance, iirc) and while EGL Streams improves on that, it doesn't fix everything. And the third solution, the one that people are supposed to be working on together, is still MIA.
Long story short, this seems to have landed in the hands of drama queens. Looking at this vary page's source code, it has "<!--[if IE]> ... <!--<![endif]-->" in it. Virtually every piece of code that's supposed to be portable has some target specific pieces in it, but in this case it seems it has become way more important to stick it to Nvidia instead.
Comment
Comment