Linux

48323 readers

638 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

163

Why Wayland adoption to have official support in programs is so slow? (wayland.freedesktop.org)

submitted 3 months ago by Psyhackological@lemmy.ml to c/linux@lemmy.ml

108 comments fedilink hide all child comments

Wayland seems ready to me but the main problem that many programs are not configured / compiled to support it. Why is that? I know it's not easy as "Wayland support? Yes" (but in many cases adding a flag is enough but maybe it's not a perfect support). What am I missing? Even Blender says if it fails to use Wayland it will use X11.

When Wayland is detected, it is the preferred system, otherwise X11 will be used

Also XWayland has many limitations as X11 does.

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

[–] Psyhackological@lemmy.ml 4 points 3 months ago (3 children)

Could you give me some examples so I can understand what's missing and being waited on?

[–] winterayars@sh.itjust.works 4 points 3 months ago (1 children)

Someone above mentioned screen reader support for blind use accessibility stuff. For users who are blind, this is critical.

[–] drwankingstein@lemmy.dbzer0.com 1 points 3 months ago

This is actually one thing that doesn't involve wayland, as pretty much everyone is using at-spi. It's not great, but it does work.

[–] drwankingstein@lemmy.dbzer0.com 3 points 3 months ago

for one, it's missing a good chunk of A11y stuff, activity watch requires something to monitor the active window, there is a PR for that, still not merged, this has been an issue for years

It's missing protocols that will let applications request to be a privileged application, which is necessary for applications to use other functionality.

Missing protocols to control always-on-top / layers, which is needed for OSKs to function, and a couple other A11y things off the top of my head.

It's not just a11y either, Window positioning still isn't merged, which means if your app opens two "windows", you cannot currently select where to open them, or to even bind two windows together (Android emulator does this for instance).

There is a LOT wayland is missing, it IS getting better, just at a snails pace.