Linux

48310 readers

645 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

184

ELI5 the whole Wayland vs X11 going on. (programming.dev)

submitted 10 months ago by alexdeathway@programming.dev to c/linux@lemmy.ml

123 comments fedilink hide all child comments

Title

you are viewing a single comment's thread
view the rest of the comments

[–] lloram239@feddit.de 10 points 10 months ago (2 children)

The issue isn't just that the features had to be reimplemented, but that they were not part of Wayland to begin with. Wayland does only do the most basic stuff and leaves everything else to the compositor (aka Gnome or KDE). That means every compositor will implement their own hacky version of the missing functionality and it takes ages until that gets unified again, so that apps can actually use that functionality.

Wayland is a classic case of an underspecified software project, they do a thing and they might even do it well, but what they are doing is only a fraction of what is actually needed for it to work properly in the real world. That's why we are 15 years later and the new "simpler" Wayland is still not ready.

[–] deluxeparrot@thelemmy.club 2 points 10 months ago (1 children)

Wayland does only do the most basic stuff and leaves everything else to the compositor (aka Gnome or KDE). That means every compositor will implement their own hacky version of the missing functionality and it takes ages until that gets unified again, so that apps can actually use that functionality.

Would this functionality be mostly the same? Could they get together to make a shared libcompositor that implements the bulk of the functionality? Or is it so tied to specifics of the desktop environment that there's little commonality. In which case, Wayland not doing it would be the right call.

[–] ReakDuck@lemmy.ml 5 points 10 months ago* (last edited 10 months ago) (1 children)

I think wlroots is the standardized thing. Many WMs use it but desktops need to switch over to it afaik. I think KDE talked about doing this for plasma.

I am unsure what wlroots really is and maybe its not a libcompositor you were talking about but similar.

[–] SomethingBurger@jlai.lu 4 points 10 months ago

This is exactly what it is.

[–] verdigris@lemmy.ml 1 points 10 months ago* (last edited 10 months ago)

It seems very well specified to me, just developers have leaned on X's insecurity for years to let them just reach across application boundaries freely. That's addressed by Wayland, but it's obviously a breaking change that requires new ways of transferring information between apps with oversight from the system, instead of X where all apps could just freely spy on each other. Things breaking and being complex to reimplement is the cost of doing it right.