Originally posted by bug77
View Post
Announcement
Collapse
No announcement yet.
Wayland Is Driving Fragmentation Around EDID Parsing - A Call To Fix That
Collapse
X
-
Originally posted by mos87 View PostWhat, an architectural oversight leading to implementations having to do the same thing every client has to each on their own??
Totally unexpected tbh from the redhat/gnome/PROGRESSIVEPEOPLEOFTHEFUTURE stack =P
- Likes 2
Comment
-
Originally posted by birdie View PostAh, here we go again, Wayland doesn't provide a standard(ized) WM/WC out of the box or is Wayland = Gnome?
X11 comes without a standard WM, Xorg as the most popular implementation too.
When you need to troll, at least put some work in it.
- Likes 3
Comment
-
Originally posted by Zan Lynx View PostNo, there's like six X implementation that run on x86 hardware. Most of them are obsolete and haven't been maintained for ages but they're there.
- Likes 3
Comment
-
Originally posted by microcode View PostEDID parsing is not that complicated, and the styles of many of these projects are different (though some of them are similar enough). I feel like it's not really a big deal to have EDID parser fragmentation.
- Likes 1
Comment
-
Originally posted by Alexmitter View PostThen X11 is also not a protocol.
The X Window System (X11, or simply X) is a windowing system for bitmap displays, common on Unix-like operating systems.
Not to mention what X is (or isn't) is totally irrelevant in this context.
Comment
-
Originally posted by Alexmitter View Post
Here is a link to: https://github.com/wayland-project/weston
X11 comes without a standard WM, Xorg as the most popular implementation too.
When you need to troll, at least put some work in it.
When you want to look smug at least have your arguments right.
- Likes 4
Comment
-
Originally posted by birdie View PostX11 = X.org for the past >10 years. Weston is not a standard WM/compositor and Mutter/Kwin/wlroot/etc implement various desktop APIs differently.
When you want to look smug at least have your arguments right.
Solaris only moved to X.org fully in 2010 before that that platform was a choice between X.org and Xsun. But you go and use a HPuX server today and its HP X11 that don't use X.org. This is the thing when you say X11 most commonly on Linux these days it equals X.org. But there are still Linux distributions where you found MicroXwin or equal closed source until 2015.
We still have Linux distributions like tinycorelinux shipping with their own customs X11 servers today.
So birdie "X11=X.org for the past >10 Years" in reality is not true. There is a lot of X11 fragmentation you have just ignored
libwayland-server has over time expended in the features in provides. Please note Mutter/Kwin and Wlroots all use libwayland-server.
https://gitlab.freedesktop.org/wayla...ree/master/src
Yes there is a core common code part to wayland in libraries from the main project.
Also Weston is officially the reference compositor for Wayland the same way X.org X11 was the reference X11 server for the X11 protocol. So its kind of sad that libweston has not been picked up by more compositors. This is normal levels of fragmentation for what was going on with X11 server before wayland that you have been failing to see birdie.
- Likes 3
Comment
-
-
Originally posted by Alexmitter View Post
It was okay when every X compositor was implementing and doing the same things?
I'll just say that X for a system from 80-something worked (and continues to work) quite well, despite maybe internally becoming a mess over the years.
Comment
Comment