Wayland 1.17 Released With Updated Protocol & Other Improvements

[tildearrow]

Have two sets of clipboards is confusing for many users. The benefit in favor of it is arguably weak.

For me it is very useful. Sometimes I have a URL copied in one clipboard, and a piece of code in the other. I feel it's easier to just select a piece of text and being able to paste it somewhere with a middle click.

Yeah, that sucks the entire desktop goes down when the compositor crashes. I guess it would be good with a compositor written in Rust.

Rust is also capable of crashing, although prevents many crashes.

It is not just GNOME that don't want server-side decorations, I think Wayland have a architecture similar to Windows 10 and macOS.

Both Windows 10 and macOS have SSD as well.

[uid313]

As a GNOME user, I can say this used to suck back when there were bugs causing compositor crashes, but these days it's 100% stable for me on three different systems currently on GNOME 3.30.2

I experienced a freeze followed by a crash some weeks ago when I clicked on a URL in HexChat that was supposed to open in Firefox.

[Brisse]

Yeah, that sucks the entire desktop goes down when the compositor crashes.

As a GNOME user, I can say this used to suck back when there were bugs causing compositor crashes, but these days it's 100% stable for me on three different systems currently on GNOME 3.30.2

[uid313]

Can somebody implement a permission system on X please? I want to respond.

I don't know.
But in Wayland applications cant snoop on other applications.
While on X.Org Server any application can listen on keystrokes intended for another application.

X could also have this property.

I don't think so. X have 30+ years of baggage.
Wayland is very simple, its basically just a render context.

Also, where's my middle click paste? Why does it take down my entire desktop when the compositor crashes? Can I have server-side decorations on every Wayland compositor? (if GNOME does not want so, it does not mean everyone has to follow)

Have two sets of clipboards is confusing for many users. The benefit in favor of it is arguably weak.
Yeah, that sucks the entire desktop goes down when the compositor crashes. I guess it would be good with a compositor written in Rust.
It is not just GNOME that don't want server-side decorations, I think Wayland have a architecture similar to Windows 10 and macOS.

[tildearrow]

It is more secure. Applications cannot spy on other applications.
Perhaps it is more secure.

Can somebody implement a permission system on X please? I want to respond.

Perhaps more light-weight. Perhaps less overhead.

X could also have this property.

Perhaps renders smoother and less frame skips and jitter.

My patched KWin also has this feature.

Also, where's my middle click paste? Why does it take down my entire desktop when the compositor crashes? Can I have server-side decorations on every Wayland compositor? (if GNOME does not want so, it does not mean everyone has to follow)

[uid313]

You misunderstood my question.

What I meant is, what are the benefits of using a Wayland compositor over X.Org? I asked that since you said "Also you lose some of the benefits of running Wayland", which implies Wayland has benefits, but I am not aware of any *real* benefits...

It is more secure. Applications cannot spy on other applications.
Perhaps it is more secure.
Perhaps more light-weight. Perhaps less overhead.
Perhaps renders smoother and less frame skips and jitter.

[tildearrow]

Well, if I am going to run everything through XWayland, then whats the point of using Wayland. Then tha is just extra overhead, and I might aswayll just run X.Org Server instead.

So for Wayland to be compelling, then the software that I most commonly use needs run native on Wayland.
So for me, that is Firefox.

You misunderstood my question.

What I meant is, what are the benefits of using a Wayland compositor over X.Org? I asked that since you said "Also you lose some of the benefits of running Wayland", which implies Wayland has benefits, but I am not aware of any *real* benefits...

[uid313]

Which are?

Well, if I am going to run everything through XWayland, then whats the point of using Wayland. Then tha is just extra overhead, and I might aswayll just run X.Org Server instead.

So for Wayland to be compelling, then the software that I most commonly use needs run native on Wayland.
So for me, that is Firefox.

[tildearrow]

Also you lose some of the benefits of running Wayland

Which are?

[uid313]

Electron doesnt need Wayland supports, it needs to die.

I don't know where you get that from.
But Electron is built upon Chromium, so once Chromium gets support for Wayland then Electron can inherit it.

https://github.com/electron/electron/issues/9056

https://github.com/electron/electron/issues/10915