Live data from Hacker News

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

gist.github.com

151–160 of 419 posts

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

#151
post #43

Earlier quoted context omitted.

> [...] 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…

> 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. Many seasoned Xorg developers work on Wayland. All the decades of lessons form Xorg _were_ carried over to Wayland.

Many of the lessons are being carried over no doubt. Others are embodied in the heads of people not working on Wayland or in the codebase itself as emergent properties from interactions never consciously designed.

There will be some loss of lessons with almost no doubt.

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

#152
I don't really understand why such a title has been chosen for HN. Granted, the original one is inflammatory, but this one is just wrong: there is no “Yet”, Wayland will never be a 1:1 compatible Xorg replacement, and is not intended to be.

Wayland has a different approach when it comes to security, which makes it much less flexible in order to increase user security. It has evolved a in way to allow as much legit things as possible, but it will never be 100% compatible with what Xorg offered, by design!

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

#153
post #78
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…

As a complete outsider - ok, I'm a developer, but I haven't had the pleasure (?) of writing something that interfaces directly with Xorg yet - I have been reading for years about Wayland being the way forward and how Xorg is dragged down by a long history of dubious design decisions and features nobody needs anymore, and I was secretly wondering: if this is really the future of desktop Linux, why doesn't it gain more…

> This post is a bit too ranty for its own good, but it has a valid point, and one that is unfortunately common in the open source community: because you have no monetary obligation to your "customers" (=users), there's not really a lot that forces you to maintain backwards compatibility.

And yet, distros like Ubuntu are too conservative, because they are too careful not to break something. Their signalling is then considered as it works, we don't have to fix anything, Ubuntu will keep things broken for us. Due to this attitude, they have slowed down Linux desktop by years, by not switching to Wayland by default in the past LTS release.

Compare with Apple: in the same timeframe they've deprecated and removed support for entire architecture (i386) while Ubuntu just thinks about doing one step. Apple breaks compatibility at much faster rate than Linux world, and everyone is fine with it. The difference is in signaling: Apple decides and does. In Linux world, we have articles like these, that try to slow down everyone.

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

#154
post #43

Earlier quoted context omitted.

> [...] 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…

> 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. Many seasoned Xorg developers work on Wayland. All the decades of lessons form Xorg _were_ carried over to Wayland.

>> Many seasoned Xorg developers work on Wayland.

All of them are either working on Wayland or moved on. There are no Xorg developers.

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

#155

I think I'll wait until every screen sharing, video calling application I use will work with Wayland. Pasting selected text with middle button is also very important to me (huge time saver) and it seems not to work with Wayland yet.

Basic things like embedding windows (and thus classic, non-remote-puppet-over-dbus) systrays are impossible, which funnily enough break things like signing my tax forms with digital signature...

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

#156
post #100
post #83

Earlier quoted context omitted.

> Xorg is 16 years old Xorg is a fork of Xfree86 which started in 1991 but feature parity minus the cruft has been reached years ago. Some people disagree about what is cruft however. For example, I view 90% of the list in the posted articles to be minor softwares relying on undesirable behaviour and unwilling to adapt (the remaining 10% being misrepresentation of actually solved issues listed in bad faith). The orig…

> How can people accept to use a display manager with constant screen tearing is beside me. I never even noticed it, and I never quite understood what people are on about with this. I had to go to YouTube to watch a demo video to see what it really looks like. And if I try it, then yes, I suppose I see some tearing if I move a window and pay close attention to it. But I never even noticed on my own, and am not bother…

It's especially noticeable with fast-moving videos or games.

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

#157
post #130

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…

We (desktop devs) eventually gave up on it and are enjoying our Windows/macOS/Android/ChromeOS setups instead.

It would be funny that at the point where it seems that Linux desktop hardware support is at its peak, the actual use of Linux desktop would be at its lowest. I don't think that's the case, though.

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

#158
post #96

Earlier quoted context omitted.

Firefox has treesyle tabs which has zero good alternatives on chrome. Tridacyl, vim like bindings for your browser + ability to bind javascript or native shell is more powerful than chrome alternatives. Chromium is losing google sync and chrome and chromium are Effectively destroying adblocking sooner or later courtesy of manifest v3. Ublock origin and treestyle tabs alone make a compelling case and are visually and…

Tridactyl is extremely quircky due to the limitations imposed to Web extensions though. I remember good old Vimperator to be more reliable. I get why they did it though, allowing extensions to effectively take over the browser sounds like a recipe for disaster. Too bad there isn't a way to opt into it when it's actually what you want.

I'm experimenting with Pale Moon now.

It actuall feels snappier than the latest Firefox, but a profile reset on my main Firefox might change that (traditionally with my usage patterns there's little improvement to be seen from that.)

So for now the advantages of Firefox vs Chrome are:

- not Google

- less RAM usage

- slightly better extensions

And for Palemoon vs Firefox:

Pro Palemoon:

- snappier (?)

- extensions work

- looks better (subjective) and can be skinned

Advantages Firefox:

- more secure (maybe, Palemoon unlike Mozilla doesn't have a history of abusing extension bundling for various promos)

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

#160

Earlier quoted context omitted.

> The author obviously hasn’t tried plugging a high dpi monitor in to a laptop if they don’t understand what’s wrong with X This is the only actual, honest, problem that I've ever seen about X. Still, it does not seem a really fundamental problem, it must surely be solvable from within X? Do we really need a full-rewrite of X, unstable, with new bugs and less functionalities? (many of us don't use "desktop" applicati…

> Still, it does not seem a really fundamental problem, it must surely be solvable from within X? X gives you two options: set DPI per displays. The thing is, you cannot drag windows between displays, the app has destroy it, connect to another one and recreate it here. There's even no mechanism to detect multiple displays other that user setting up the DISPLAY env variable. Or you can do, as the Xorg does: use multip…

> It is a good thing that they are broken, because what they do is snooping on windows that do not belong to them.

Don't want to derail this discussion anymore, but this argument is nuts. If you are so concerned that programs that you run can spy on other programs that you run, how do you deal that the fact that all of these running programs have full read-write access to all files on your $HOME?

EDIT: I agree that being able to run selected programs inside a sandbox would be a good thing (maybe even all programs). But attacking the problem of visible display before that of hidden files seems ridiculous. Moreso if it cripples copy paste, screen capture, and similar basic stuff (which to me are just like unix pipes: ways to make programs work together!)

Post reply on HN