Why Wayland adoption to have official support in programs is so slow?

https://lemmy.ml/post/19267163

Why Wayland adoption to have official support in programs is so slow? - Lemmy

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 [https://docs.blender.org/manual/en/latest/getting_started/installing/linux_windowing_environment.html] 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.

Also XWayland has many limitations as X11 does.

If an app has only ever supported X11, then it probably doesn’t care about those limitations (the apps that do care probably already have a Wayland version). And if an app doesn’t care about the extra stuff Wayland has to offer, then there’s not really a reason to add the extra support burden of Wayland. As long as they work fine in XWayland, I think a lot of apps won’t switch over until X11 support starts dropping from their toolkit, and they’ll just go straight to Wayland-only.

Yeah I agree. Maybe some day X11 will be seen as something legacy that needs to be deprecated. But not now…
Plasma deprecated their X11 session in v6 pending removal in the future, and Redhat has already dropped it in Fedora & will do for EL in the next release.

Wayland isn’t even adopted by every desktop environment yet. xfce, cinnamon, mate, lxqt, and all the ancient window managers all use x11, and all have their users.

If it works on xwayland, chances are it won’t be switched for a long time.

Xfce4 and cinnamon are close to wayland support.
May programs do though

So software like CAD is funny. Under the surface, 3d CAD like FreeCAD or Blender is taking vertices and placing them in a Cartesian space (X/Y/Z - planes). Then it is building objects in that space by calculating the mathematical relationships in serial. So each feature you add involves adding math problems to a tree. Each feature on the tree is linearly built and relies on the previously calculated math.

Editing any changes up tree is a massive issue called the topological naming problem. All CAD has this issue and all fixes are hacks and patches that are incomplete solutions, (it has to do with π and rounding floating point at every stage of the math).

Now, this is only the beginning. Assemblies are made of parts that each have their own Cartesian coordinate planes. Often, individual parts have features that are referencing other parts in a live relationship where a change in part A also changes part B.

Now imagine modeling a whole car, a game world, a movie set, or a skyscraper. The assemblies get quite large depending on what you’re working on. Just an entire 3d printer modeled in FreeCAD was more than my last computer could handle.

Most advanced CAD needs to get to the level of hardware integration where generalizations made for something like Wayland simply are not sufficient. Like your default CPU scheduler, (CFS on Linux) is setup to maximize throughput at all costs. For CAD, this is not optimal. The process niceness may be enough in most cases, but there may be times when true CPU set isolation is needed to prevent anything interrupting the math as it renders. How this is split and managed with a GPU may be important too.

I barely know enough to say this much. When I was pushing my last computer too far with FreeCAD, optimising the CPU scheduler stopped a crashing problem and extended my use slightly, but was not worth much. I really needed a better computer. However looking into the issue deeply was interesting. It revealed how CAD is a solid outlier workflow that is extremely demanding and very different from the rest of the computer where user experience is the focus.

Wayland will perform better than X as there is no server it has to go through. It can talk almost directly to hardware

It’s true what you write, but it’s not related to Wayland/X11.

But this is the reason CAD software can’t use multiple cpu cores for geometry calculations. The next calculation needs the result of the previous one, it can’t be parallelized.

It is not enough to make a better product.

It is not enough to create all tooling and libraries to seamlessly migrate to the new product, but it helps.

There also needs to be a great big positive reason to make the change. Paying developers, huge user base, the only hardware support, great visuals, etc.

Until I cannot run software on X11, I won’t switch over knowingly.

Once the desktops switch to Wayland and all distros ship with Wayland by default, support should slow.

Ideally, developers stop improving xwayland over time and go into maintenance mode for a bit. Once it goes into maintenance mode, developers should naturally fall off as it winds down.

If every desktop makes a very public announcement about the xwayland protocol being put into maintenance mode, actively supported apps should switch over. It’s up to the public how long they want to keep maintaining xwayland (open source etc).

But why would the distros do that? It takes effort and has real costs for them.

They’re already starting to go that way, in a couple years Linux mint is even going to support Wayland. Ubuntu and fedora has already defaulted to Wayland. Fedora is actually deprecating xorg in a few releases. Budgie wants to have full support next year.

There isn’t much more than the testing they already have to do every release. Infact not having to support legacy code will free up resources for the whole Linux community as well as cutting the time in half for validating packages on distros. Every package that runs on xorg also runs on wayland, they have to test both.

Granted some have custom tools they’ll be working on but it’s going to be a while before every major DE supports Wayland. I’m curious, you think the distros have to implement their own version of Wayland?

xwayland cannot ever be removed, because wayland, by design, will not have enough functionality to replace it. So one can either support X desktop environments with their own individual bugs, or one X implementation that has the needed features and works consistently for all DEs

If developers drop off there’s not much we can do. It’ll eventually have to be removed or become a bigger security risk than developers say it is already.

Support on the x server itself has dropped off precipitously since Wayland hit the mainstream and most small x11 DEs are trying to build off of WM like wayfire or wlroots.

I do not care about security risks. If something made its way onto my system, I’ve already lost. I just want one implementation of something that gets the job done. And by “gets the job done” I mean it allows us to do things better, not disallow us from even having the option to do things because someone had their tinfoil hat on too tight. Ffs you can’t even set your window icon. I don’t care if kde has implemented that feature. If I use that, I’d be supporting kde, not wayland. It won’t work on other des and so the maintenance burden increases drastically.

Your arguments kinda weak, no offense. I do have a solution for you though. If you want to stick with a version of Linux that’s guaranteed to support xorg for eight years, I’d recommend Rocky linux! When that reaches EOL I guess you could just stay on it.

Enterprise plans on being fully switched over to Wayland by the next major version. You won’t be able to install xorg on redhat for example. The biggest contributors to xorg(Enterprise) are going to shift focus to xwayland to support legacy software on wayland.

Besides it’s exciting finally catching up to truly hardware accelerated desktops like Mac OS 10.0 and windows vista. At its heart xorg is a purely single threaded software accelerated bitmap based windowing system from 84. They’ve had to rewrite small but incredibly complex chunks of the code just to try to keep up with the modern world. Just look at the history of 3D acceleration in x11.

Your free to give it a good go though! The very same team that actively maintained xorg threw in the towel ten years ago when they diverted resources towards a new windowing protocol and they’re not going back.

Rocky Linux Release and Version Guide - Rocky Linux Wiki

The wiki for the Rocky Linux project

new features are fine. But first and foremost, is not breaking existing apps, or committing to porting them yourself. So if desktop apps need to do xyz, then wayland needs to support doing xyz. period. No ‘but that’s insecure’, no ‘but why would you want to do that’ (for setting a window icon or positioning the window ffs). Support existing applications. I’m not saying it should support x protocols. But it should offer replacement features for existing apps to be ported to. And it needs to be wayland. Because it’s already the case that certain functionality is implemented for gnome, or kde, with incompatible apis, to fill in the void left by wayland itself. If I want an app to work as I want it, consistently, everywhere? X, with all its warts, is my only choice.

As an example, the accessibility protocols. They’re good to have. Except they’re opt-in. So incompatible with existing apps. Some apps need to restrict access. They could declare that and make use of additional functionality. But no, choose a default that break everything instead.

The argument that apps just need to be ported also assumes the app is still maintained. Are you willing to do the work yourself if not? Probably not. You’re just the one looking down on people like me for wanting functionality in existing apps to be “not literally impossible to implement”

This whole argument ignores xwayland and the fact that new features are added as a standard of Wayland literally every day.

For as long as xwayland is supported you can use your old apps. Wayland actually supports different window icons for multi window apps. But Wayland has always supported window icons, kde just had an annoying bug they finally fixed. Chromium and electron apps kinda just didn’t support window icons very well in wayland for a while.

For accessibility, it’s been broken on Linux for literally years but there’s an active effort to make it better and more universal than it ever could have been on x11. The effort of building a fully featured accessibility stack is being led by the gnome team with help from the free desktop organization and kde.

This is my last response, this conversation isn’t going anywhere anyway. I’m not the one transitioning the Linux world to Wayland, I don’t see why you could blame me for it anyhow.

staging: Add xdg-toplevel-icon to allow windows to set dedicated icons (!269) · Merge requests · wayland / wayland-protocols · GitLab

Hi everyone! Here is yet another controversial protocol, but I think it is a lot easier to discuss pros and cons if there is a concrete...

GitLab
So, even though KDE Plasma has significantly advanced Wayland, a stronger push is still needed to drive the change further.

I don’t think kde plasma was the only one. Anyway, it just feels natural for xwayland to stop pushing for feature parody and for focus to switch over to Wayland after a while.

The biggest target for developers is the Ubuntu/Debian platform so their switch to Wayland should motivate other projects and paid applications to at least take notice.

New projects will try to support both but typically will focus more on Wayland. There’s already an unintentional incentive to partially support xdg protocols Wayland relies on thanks to flatpak.

Because Wayland is STILL lacking a lot of things that people need.
Could you give me some examples so I can understand what’s missing and being waited on?
Someone above mentioned screen reader support for blind use accessibility stuff. For users who are blind, this is critical.
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.

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.

It’s the opposite for me. X11 is unusable on my laptop because it doesn’t support fractional scaling well, whereas on my desktop it doesn’t allow for a multi monitor setup with different refresh rates. Both dealbreakers are not present with Wayland. Though your point still stands; NVIDIA GPUs continue to suck more with Wayland than X11 for example.

I’m not defending x11, both wayland and x11 are trash, it’s just whichever trash pile you find yourself most comfortable in.

On x11, fractional scaling is more or less just handled by the gui toolkit. It does suck that you need to set an env var for it, but IMO that isn’t too bad.

the multi monitor stuff does suck for sure. It’s not an issue for me personally. One thing that is a massive issue for me is x11’s terrible handling of touch, I use touch screens daily so that’s a massive issue for me, wayland compositors are also typically quite a bit faster then x11 + wms on low end systems now too (not to be confused with total resource usage/lightness).

Wayland has a lot of things going for it, but it also has a lot going against it. Both are terrible. Arcan save us (oh how a man can dream)

Because it doesn’t matter for most apps. XWayland works fine.

Even Blender says if it fails to use Wayland it will use X11.

What are you trying to say? Of course it does. Pretty much every Linux app still supports X11, because a lot of people are still using X11. Only exception I’m aware of is Waydroid.

It is still young and underdeveloped.

It is advertised to be simpler, but I don’t understand any of this words thrown in this thread. And I don’t care. Pulseaudio and pipewire is still making me troubles, even thou alsa worked without issues for me.

Point it, make it clear and stable and we will come. Until than we will use the beast we know. It os mich easier when there are no options, but Wayland is fighting something that exists and it takes time and effort.

Another problem is they pushed it to early and people got burned. Until I start seeing “I switched to Wayland in one command and everything works” I (as a user) will not touch it (unles my distro decides to drop X).