Live data from Hacker News

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

gist.github.com

241–250 of 419 posts

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

#241

Earlier quoted context omitted.

>> Many seasoned Xorg developers work on Wayland. All of them are either working on Wayland or moved on. There are no Xorg developers.

Who is downvoting this and why? Face it, Xorg is on life support. The only patches it still receives are Xwayland-related fixes.

I don't expect a stable application to receive many patches. How many patches do you think Xorg should receive nowadays and in what areas?

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

#242
post #29
post #7

Wayland doesn't even work for me, so I guess I don't have such problems. I'm not really into the actual arguments between NVidia and Wayland folks, but I suspect it's something like "they don't want to bow to us, therefore we don't want to work with them" from both sides. Like a kindergarten ;)

It's more like "Nvidia claims they support a certain API, but it's utterly broken, and developers are rightfully fed up with that".

I thought that software development was about finding solutions to problems, not escalating existing problems and demanding changes so we don't have to adapt.

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

#243
post #226

Earlier quoted context omitted.

Screen sharing seems a critical feature to enough people to rise well above mere “minor feature” if the goal is to replace Xorg. That was probably true 12 months ago, but definitely true 8 months ago. If the goal is to have a different display protocol that a significant fraction of the possible user base can’t reasonably use as their root display because it provides yet another way in which “Linux isn’t ready for th…

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.

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

#244
post #103
post #23

This is absurd. Author claims that "Wayland breaks automation software". They then use the "py37-autokey" tool as an example. Autokey uses Xorg APIs for key handling. Of course this is not going to work on Wayland since it's written for Xorg and not for Wayland. The author is probably the type of person that buys an AMD graphics card, and then complains that AMD "breaks" software that's based on CUDA...

That was just example. Because of Wayland's security model of sandboxing applications, none such tool will work. Currently afaik only way to do something similar is using /dev/uinput as does for instance ydotool , but its capabilities are vastly inferior.

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

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

#245
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…

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.

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

#246

Earlier quoted context omitted.

The problem has been crippling the Linux desktop for many years now and it still remains unsolved in X which must indicate that either it is not realistically possible or it is so much work that no one is willing to do it and likely never will. The transition to Wayland is largely finished now. Electron added support last year and eventually the last of the electron apps will update and everything will be done other…

Wayland has existed since more than 10 years and it has still not been able to release a usable system. I'm not willing to lose things that I use everyday just because some idiots want to move their windows between screens and see that they don't change their apparent size. Seriously, this is not a crippling problem. You can easily change the size of one program once it is on the desired screen. What kind of savage k…

You think that having to close an application in order to move it to a different screen is no big deal, but you think that wayland is lacking critical features? Features more critical than being able to move windows freely?

I really am curious what features you think wayland is lacking. I've been using wayland for years, both using Sway and Gnome, and the thing I've missed the most is xdotool, and perhaps there will be a standardization effort to replicate its functionality securely, but for now it's an understandable omission.

Maybe it's not fair to say that X is broken for mixed-DPI configurations, since I have managed to get it working with X, but it was quite unreliable, whereas on wayland it just works, save for some incompatible electron apps.

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

#247
post #196
post #93

Earlier quoted context omitted.

And for me, this is the main Issue: belief People are flaming and screaming about their beliefs, demonizing systemd, Wayland and what-not with FUD, baseless arguments and non-arguments, because they "believe" these things are bad and must die. If I want to talk about what runs on my workstation as if it was religion, I install Temple OS. If I want a modern (and basically following sane/safe architecture decisions) di…

systemd adds a concrete and substantial set of features for me. I eagerly embraced systemd for that reason - there are things I don't like about it, but it gave me lots of new benefits that justified the effort. Moving to Wayland would force a bunch of changes on me for the sake of no functionality I care about. That's the big difference. Given it provides no benefits to me that I care about, I won't move until stayi…

But that's the thing though. For _you_ systemd had a concrete and substantial set of features, while wayland doesn't for many others it was the other way around. (I don't mind either, but there are annoyances in both).

The problem is that many are complaining that _their_ specific set of functionalities is no longer being catered for, or better not being actively developed. The great thing about linux is that you can do what you are doing and continue running Xorg as long as you want, it might be more work however.

Regarding your wayland would force a bunch of changes on you for no functionality, what are those specifically?

I would encourage you to try out wayland, for me moving from i3 to sway has largely been a seamless experience and I (tell myself that) see notable performance improvements for example.

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

#248

Earlier quoted context omitted.

Wayland has existed since more than 10 years and it has still not been able to release a usable system. I'm not willing to lose things that I use everyday just because some idiots want to move their windows between screens and see that they don't change their apparent size. Seriously, this is not a crippling problem. You can easily change the size of one program once it is on the desired screen. What kind of savage k…

>Wayland has existed since more than 10 years and it has still not been able to release a usable system. Fedora has has it on by default for about 4 years now and its perfectly usable. I use it every day. The problem is much more serious than you are explaining. While using X, on my main monitor, UI and text becomes so small I can not even read it or click the icons. I'm not talking about the window size, but the UI…

My display scalings aren't 100% and 200%, however. They're 125% and 160%.

Can Wayland handle this? If not, what's it really solving?

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

#249
post #23

This is absurd. Author claims that "Wayland breaks automation software". They then use the "py37-autokey" tool as an example. Autokey uses Xorg APIs for key handling. Of course this is not going to work on Wayland since it's written for Xorg and not for Wayland. The author is probably the type of person that buys an AMD graphics card, and then complains that AMD "breaks" software that's based on CUDA...

This list is so full of utter bullshit. I am so sick of this nonsense. Some more examples:

> Wayland breaks screen sharing applications

> https://github.com/jitsi/jitsi-meet/issues/6389 x broken since 24 Jan 2016 ("Closing since there is nothing we can do from the Jitsi Meet side.") See? Wayland breaks stuff and leaves application developers helpless and unable to fix the breakage, even if they wanted.

It's not Jitsi's freaking problem! JavaScript webshit doesn't speak Wayalnd or X. This should be implemented in the web browser, and, surprise - it already has been done for Wayland and shipped in Firefox and Chromium.

I'm not going to break down all of these, but it's just a bunch of vile horseshit. And you know what? I'm tired of debunking this crap. "Wayland devs break things and make everyone else deal with it." Xorg is broken and all of the user applications expect us to just volunteer to maintain a broken piece of shit forever. No matter how you slice it, someone's gonna have to do it, and there's plenty of shit that's permanently broken on X11 which works fine on Wayland, too. Fuck me, I'm so sick of this shit. My new answer to "I don't like Wayland" is "I don't like you." I'm tired of using reason. These people are like fucking flat earthers.

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

#250
post #182

Earlier quoted context omitted.

My external monitor is 3440x1440. Equivalent HiDPI monitors didn't exist. Perhaps maybe they do now, but the pricing would be prohibitive.

My 3840x2160 external monitor has a pixel density of approx. 275 ppi. IIRC it cost approx. $300, not exactly prohibitive.

That's not an equivalent monitor though. Equivalent monitor would have 6880x2880 resolution to achieve same workspace in HiDPI configuration.
Post reply on HN