Wayland is not ready as a 1:1 compatible Xorg replacement just yet

Post by ddevault » Tue, Feb 02, 2021, 1:32 PM UTC

adrusi wrote: post #283

ddevault wrote: post #244

Earlier quoted context omitted.

What makes you think uinput is less capable? Ultimately everything that uses input uses uinput, it's the source of truth.

For the same reason that it can make sense to say that python is more powerful than C, even though you can obviously do more things with C than with python. Xdotool lets you send keystrokes to a particular window, even if it's not in focus. You can do that with ydotool if you also do some sway IPC, but it's not as convenient, and no one has made a higher-level tool, possibly because it would be a nightmare to make it…

Post by stuaxo » Tue, Feb 02, 2021, 1:35 PM UTC

elric wrote: post #43

jchw wrote: post #19

> Wayland solves no issues I have This is a common sentiment, but it is kind of funny. Because software engineers working for companies will know the struggle of trying to justify reducing technical debt, improving security practices, etc. but fail to see why these things are useful to them personally when the tables turn. Wayland indeed “breaks a lot of shit” but it’s not an accident or done due to incompetence. Als…

> [...] reducing technical debt, improving security practices, etc Reducing technical debt by rewriting everything from scratch (almost?) never works. It's the baby and the bathwater. It's the sort of thing that seems attractive to junior developers, but more seasoned folks know that the legacy system contains years of embedded knowledge and workarounds for "real world" issues. The new, conceptually beautiful system…

Post by severino » Tue, Feb 02, 2021, 1:37 PM UTC

turminal wrote: post #257

severino wrote: post #201

Earlier quoted context omitted.

> Nvidia is the major blocker here and there is very little wayland devs can do to fix this I know, but it can be difficult to understand. I mean, how come we currently have Nvidia drivers for Linux, which work pretty well, and they can't be used for Wayland?

Because the entire linux graphics community uses the same API (GBM) and wayland is mostly built around that, but Nvidia insists on not using it for some reason.

Post by ehvatum » Tue, Feb 02, 2021, 1:38 PM UTC

turminal wrote: post #245

tannhaeuser wrote: post #81

Earlier quoted context omitted.

I haven't seen many desktop apps emerging in the last decade, so whom is that "legacy is holding back the Linux desktop" argument addressed at? X may not be the most modern architecture, but it's still the API almost all F/OSS desktop apps are ultimately written and tested against. For many apps, wayland doesn't bring a new perspective, but end of life with no new apps taking their place. For other apps, wayland mean…

You are overestimating the difficulties of porting old stuff to wayland. XWayland doesn't have a prespecified EOL, it's just going to sit there indefinitely to support all the legacy apps. This means that there is no need to hurry with migration. And the issues in X that wayland aims to fix are much bigger than the issues that python2 had when it got replaced.

Post by adrusi » Tue, Feb 02, 2021, 1:40 PM UTC

Filligree wrote: post #243

adrusi wrote: post #226

Earlier quoted context omitted.

Wayland definitely supports screen capture.

Can you write an application which uses screen capture on Wayland, and which works equally well regardless of compositor? If not, then Wayland doesn't support screen capture. Individual compositors might, but asking developers to implement five separate screen capture protocols is a big ask.