X.Org Server Development Hit A Decade High For The Number Of Commits In 2024

[Artim]

I don't know in how many ways it can be said but these clowns will still keep throwing their meaningless tantrum.
https://www.youtube.com/watch?v=MH7KYmGnj40

They will until there's no software left capable of running on X, at least if someone removes the ability of Weston to run as an X client. Or they will just keep using that as some kind of reversed XWayland and will still be pestering people when everyone else has forgotten that X ever was a thing, like the morons they are.

[Monsterovich]

Wayland is modular, XOrg isn't. But no, interchangability isn't needed in by anyone, otherwise XOrg couldn't be an option either.

Complete bullshit. Every Wayland server is unique and incompatible with other servers. In Xorg you can easily change window manager or compositor, but in Wayland even a screen capturing program may not work on another server.

[Hibbelharry]

Complete bullshit. Every Wayland server is unique and incompatible with other servers. In Xorg you can easily change window manager or compositor, but in Wayland even a screen capturing program may not work on another server.

In X the Xserver basically lost being a server long time ago. Very much of the stuff expected to be done in the server was moved out into the WMs because Xserver failed to do a lot of tasks in a sane manner. Retrofitting many things didn't work because that would have broken backwards compatibility so it was a lost case. That basically means every WM capable of compositing does nearly the same amount of stuff as in Wayland.

Xserver has gone from being it's own OS to not anything more than a bad IPC implementation, that's all.

X11 also isn't any more modular than Wayland at all. It's split up in many more git modules, yeah, but if you check for the relevant really used parts and locate those in bloated WMs full of workarounds for bad or undefined X11 behaviour and the corresponding X11 parts, you'll get a picture.

See the video from Daniel Stone linked before, he explained that pretty well.

I don't get why some people still believe the Xserver is anything more than cruft we had to use but can't move away from to a better implementation of IPC.

[MrCooper]

Yet “X.org is dead and no one wants to work on it anymore”, right Wayland fans?

You're two pages late to the party:

https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/1516068-x-org-server-development-hit-a-decade-high-for-the-number-of-commits-in-2024?p=1516235#post1516235

xorg has supported the 30bit RGB 101010 deep color format for literal decades. Sure client support is pretty spotty, but thats no different than wayland.

Actually it's completely different, and it's a good example for why Wayland had to happen:

Xorg will most certainly never be able to switch to 10 bpc by default (which would be a minimal requirement for HDR), because it would break too many clients.

In contrast, Wayland compositors have advertised 10 bpc formats to clients for many years, and clients have been using them without issues. (GTK can also use 16 bpc floating-point formats if the application requires it. These formats can't be supported in X for multiple reasons)

Further in contrast to X, with Wayland the formats used by clients for their surfaces and the format used by the compositor for its output are completely independent. Mutter switched to 10 bpc by default for its output in GNOME 46, again without issues.

[Monsterovich]

In X the Xserver basically lost being a server long time ago. Very much of the stuff expected to be done in the server was moved out into the WMs because Xserver failed to do a lot of tasks in a sane manner.

Why the hell should the window manager functions be in the server. Stop with your Waytrash crap in your head. Xorg has the architecture done perfectly.

In X the Xserver basically lost being a server long time ago. Very much of the stuff expected to be done in the See the video from Daniel Stone linked before, he explained that pretty well.

Screw that guy, if he likes to implement his own "Xorg" from scratch, let him do it, other DEs besides GNOME and KDE won't have such resources. Furthermore, now with the efforts of Wayland, fragmentation on GNU/Linux desktop would be insane.

Reminder: Wayland was originally created for the GNOME kiosk, where there are no features, so the architecture is just that.

[FedFer]

Also client's don't need to care, "unsupported clients" will just send sRGB to the server as always.

This site's reading comprehension is almost as piss poor as Tumblr's...
Drawables can also be read from in X11 meaning an sRGB-only client could try to read an HDR surface which would need to be mapped back to sRGB for the client to work with.

[Artim]

Complete bullshit. Every Wayland server is unique and incompatible with other servers. In Xorg you can easily change window manager or compositor, but in Wayland even a screen capturing program may not work on another server.

Lies. Yes, mot Wayland implementations use custom Wayland servers. But that's merely the status quo, but there are still things like wlroot or Theseus' Ship. Just because right now nobody bothers to make a Wayland server that could be used in every DE/WM doesn't mean it's impossible. This isn't a thing inherent to Wayland. While on paper you can also only on paper change that much. And no, as Wayland screen capturing is done through portals, it will always work, as no Wayland implementation will just throw out basic protocols for no reason. So only if a DE wants to make it an inherent feature to not allow screen capture it won't be possible.

[Vistaus]

Why the hell should the window manager functions be in the server. Stop with your Waytrash crap in your head. Xorg has the architecture done perfectly.


Screw that guy, if he likes to implement his own "Xorg" from scratch, let him do it, other DEs besides GNOME and KDE won't have such resources. Furthermore, now with the efforts of Wayland, fragmentation on GNU/Linux desktop would be insane.

Reminder: Wayland was originally created for the GNOME kiosk, where there are no features, so the architecture is just that.

The fragmentation already exists, with X.Org, Wayland and Arcan.

[Monsterovich]

But that's merely the status quo

How many more centuries will this status quo be before we see a finished product rather than a specification from a "Wayland party"?

but there are still things like wlroot

wlroots and other libraries that just help in Wayland-server development and have nothing to do with the implementation of a unified server and such. Wayland is not about productivity, but about endless development. Hyrpland seems to have already given up on wlroots.

And no, as Wayland screen capturing is done through portals, it will always work,

Portals require implementation from the unique DE server - which means if run Weston right now, your portal crutches won't work. And it also requires the mandatory installation of Pipewire which, by the way, I have installed right now. More BS from Wayland cultists.

[Monsterovich]

The fragmentation already exists, with X.Org, Wayland and Arcan.

Without Wayland there is no fragmentation, you could write a backwards compatible implementation of Xorg-protocol. The same goes for Arcan which is conceptually better than Wayland.