Live data from Hacker News

An X11 apologist tries Wayland

artemis.sh

201–210 of 453 posts

Re: An X11 apologist tries Wayland

#201
post #83

Earlier quoted context omitted.

You can also use Gimp via a RDP or VNC session, which will give much better performance on low-bandwidth connections, since those protocols do damage detection, only sending updates of what's changed, and (lossy) compression. I'm not an expert, but my understanding is that the whole X11 is network transparent thing worked great when apps used the X11 drawing primitives. These days a significant number of X11 apps jus…

I was around back in the days that X-servers were still very much a thing, and even then many thought they were an expensive and inefficient way of doing things. However, there were many who genuinely believed that networks would get arbitrarily faster and compute would not. Of course, the opposite happened, but in that alternative universe X’s design would have made sense.

There is some strange irony when watching people using quite expensive IBM X Windows thin client terminals to manage xterms, each being a different talk session.

Re: An X11 apologist tries Wayland

#202

From https://wiki.ubuntu.com/Wayland "The X11 protocol was designed around running graphical apps across the network. While some people use this feature, it's far from common. Wayland drops this requirement as a way to greatly simplify its architecture." X client and server are usually the same machine, but they don't have to be. While on the road, you can use your notebook to open a Gimp session on your home machine…

> While on the road, you can use your notebook to open a Gimp session on your home machine and edit an image stored there. That is, the Gimp runs on your home machine while your notebook has the GUI. But that's never where I want the split to be when working across the network. Remote storage? Sure, sign me up. (The POSIX APIs are horribly unsuitable for network filesystems, but I'm speaking about the concept more th…

Remote GUI code works quite well on RDP sessions.

That is how we have been giving development machines since 2011, Windows workstations on whatever cloud vendor the project is taking place.

Re: An X11 apologist tries Wayland

#203

From https://wiki.ubuntu.com/Wayland "The X11 protocol was designed around running graphical apps across the network. While some people use this feature, it's far from common. Wayland drops this requirement as a way to greatly simplify its architecture." X client and server are usually the same machine, but they don't have to be. While on the road, you can use your notebook to open a Gimp session on your home machine…

What percent of Linux users do you think would ever use software this way? What percent of all "desktop" OS users would ever use software this way? It seems like an extremely niche and rare use case and probably not the right thing to target for the main desktop environment. I've been using Linux as my main OS for ~12 years now. I have personally never wanted to do anything like that. For remote software, I would pre…

Using a wayland desktop, remote login into a Linux server, start a graphical text editor like gvim, it fails. This is a very common way to dev on Linux, I too have been doing this daily, and with ssh+X11 it works out of the box. I wonder what is the best way to do this with Wayland. Should I ask an admin to reconfigure the remote server to run a VNC or RDP server, and then use a specific tool to connect? I wonder if VNC/RDP can integrate apps as windows instead of all-in-one window.

Re: An X11 apologist tries Wayland

#204
post #141
post #83

Earlier quoted context omitted.

I was around back in the days that X-servers were still very much a thing, and even then many thought they were an expensive and inefficient way of doing things. However, there were many who genuinely believed that networks would get arbitrarily faster and compute would not. Of course, the opposite happened, but in that alternative universe X’s design would have made sense.

This isn't quite right. Both have gotten arbitrarily faster. That some folks have gigabit fiber is proof of that. Graphics have just outpaced networking. Easily.

Also, network latency has a quite imminent physical limitation, the speed of light. Serial computations do also have a limit, and we are close to it with current technology, but parallel execution doesn’t really have any, and GPUs take massive advantage of that. We can continue to increase resolution /frame rate basically arbitrarily (of course with very diminishing returns after a point)

Re: An X11 apologist tries Wayland

#205
post #173

Earlier quoted context omitted.

>Is there a single Wayland supporter who finds the user experience to be better than X11? The immediately noticeable improvement with wayland is with respect to screen tearing, especially in multi-monitor rotated configurations. Screen tearing has always been an issue on x11, and while intel/amd drivers do a decent job in basic cases, things that don't work will likely never work given that x11 is mostly deprecated.

> Screen tearing has always been an issue on x11 Screen tearing has not been an issue on X11 for like... a decade? Granted, that's after development on Wayland started. Also I just don't get this obsession with screen tearing. I've experienced it on occasion in other context and I... just kinda don't care about it? Certainly if you're a video editing/creating/whatever professional, it actually matters for your job, b…

On X when in a Zoom call, if I drag any window around the whole DE starts tearing wildly to the point of it being very distracting. On Wayland, it's smooth as butter (or Windows or MacOS for that matter).

This is just one very easy to replicate example. There are a bunch of other seemingly simple tasks that lead to some rather hideous tearing in X.

Re: An X11 apologist tries Wayland

#206
One upon a time (or long forgotten concepts?) there did exist a window system with full client-side scriptability, .i.e. it implemented what nowadays is "the browser as a thin client" with Javascript for client-side rendering:

Gosling, James; Rosenthal, David S.H.; Arden, Michelle J.: The NeWS Book: An Introduction to the Network/extensible Window System

NeWS used Postscript as the language for client-side tasks. Seems it was way too early for this good idea at that time.

https://books.google.de/books/about/The_NeWS_Book.html?id=Dd...

Re: An X11 apologist tries Wayland

#207

Earlier quoted context omitted.

You can also use Gimp via a RDP or VNC session, which will give much better performance on low-bandwidth connections, since those protocols do damage detection, only sending updates of what's changed, and (lossy) compression. I'm not an expert, but my understanding is that the whole X11 is network transparent thing worked great when apps used the X11 drawing primitives. These days a significant number of X11 apps jus…

Editing my photos over a layer of video compression artifacts doesn't sound fun. Web apps are a more reasonable replacement for X11, with browser client much more capable to do low latency local processing. The only problem is lack of easy support for local apps and LAN-distributed apps. Probably still easier to add than to support low input latency eventually consistant Canvas over X11 or VNC.

There are lossy and lossless compression algorithms.

Re: An X11 apologist tries Wayland

#208
I'm an obligate kwayland user because x11 apparently cannot keep up with both gaming and having 2 monitors. When playing tf2, a game that came out in 2004, i used to get very hard stutters on x11 that i never managed to exactly track down (ie not immediately visible in whatever monitoring tool you can think of) but on wayland i have no such issue, with everything else the same. Apparently this is an x11 problem som users encounter with multiple screens, i just happen to have a gpu powerful enough to not see the stutters until a game is using all the bandwidth.

Re: An X11 apologist tries Wayland

#209

Earlier quoted context omitted.

You can also use Gimp via a RDP or VNC session, which will give much better performance on low-bandwidth connections, since those protocols do damage detection, only sending updates of what's changed, and (lossy) compression. I'm not an expert, but my understanding is that the whole X11 is network transparent thing worked great when apps used the X11 drawing primitives. These days a significant number of X11 apps jus…

Editing my photos over a layer of video compression artifacts doesn't sound fun. Web apps are a more reasonable replacement for X11, with browser client much more capable to do low latency local processing. The only problem is lack of easy support for local apps and LAN-distributed apps. Probably still easier to add than to support low input latency eventually consistant Canvas over X11 or VNC.

The roles of client and server being force-swapped is another perhaps unfortunate development.

Re: An X11 apologist tries Wayland

#210
post #102

Earlier quoted context omitted.

Each time I tried running Firefox over ssh with X11 it either lagged or crashed. With Wayland's Waypipe it works flawlessly, I could even watch a Youtube video through it. I'm double checking it right now using a remove machine a few blocks away from my home. Running `ssh -X remote firefox` lags a lot worse than `waypipe ssh remote firefox`. The latter feels almost native, very responsive. So no, I don't think we are…

> I could even watch a Youtube video through it. Watching a Youtube video on remote X is rarely a problem, there's no latency involved.

Wat?
Post reply on HN