News for hackers. Stuff that matters.
Re:An X11 apologist tries Wayland by giantdude on Sunday September 18, 2022 @05:59PM (#32891883)
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 and edit an image stored there. That is, the Gimp runs on your home machine while your notebook has the GUI.

This is a lot to give up for cool compositing effects...

Re:An X11 apologist tries Wayland by adamzegelin on Sunday September 18, 2022 @06:11PM (#32891968)
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 just render _everything_ (often including window decorations) "server-side" as bitmaps and then send them over the wire to the client to composite them. Essentially the X11 wire protocol has become a bitmap pipe.

Wayland does the "bitmap pipe" thing more efficiently than X11.

Re:An X11 apologist tries Wayland by amelius on Sunday September 18, 2022 @07:03PM (#32892309)
Very much this. Running the X11 protocol over the network is usually not a good idea anymore.

By the way, does anyone know of a VNC-like solution that can use MPEG compression?

Also, VNC could be better if it could increase the quality of parts of the screen once they stop updating. E.g. in TigerVNC setting a low bitrate doesn't improve the quality of text once the text stops changing.

Re:An X11 apologist tries Wayland by aidenn0 on Sunday September 18, 2022 @07:42PM (#32892521)
Nomachine's server and client are closed-source but work great.

For open-source solution for quickly remoting into an existing display, I use freerdp-shadow-cli which is way more stable than x11vnc and uses the RDP protocol instead.

Re:An X11 apologist tries Wayland by RealStickman_ on Monday September 19, 2022 @12:21AM (#32894248)
Nomachine used to be open source. X2Go is the open source continuation of that.
Re:An X11 apologist tries Wayland by aidenn0 on Monday September 19, 2022 @01:38AM (#32894650)
I think their current version is unrelated to what is now x2go
Re:An X11 apologist tries Wayland by izacus on Monday September 19, 2022 @03:54AM (#32895523)
XPRA uses H.264, PNG or JPEG compression. Chrome Remote Desktop will use VP9 these days.
Re:An X11 apologist tries Wayland by chpatrick on Sunday September 18, 2022 @07:22PM (#32892410)
Re:An X11 apologist tries Wayland by msla on Sunday September 18, 2022 @09:24PM (#32893227)
> Running the X11 protocol over the network is usually not a good idea anymore.

It works well, though, and I'm not really interested in hearing that my own experience with it working well is a lie or some trick. Wayland gives up some things, and pretending that those things have no value isn't going to convince those of us who know they do.

Also, those of us who use non-mainstream window managers (such as Window Maker) are not interested in hearing that we should switch to some UI which doesn't support our workflow just because it's more fashionable these days.

There's a debate to be had here, and it needs to be had on the basis of facts, not lies.

Re:An X11 apologist tries Wayland by gbin on Sunday September 18, 2022 @10:10PM (#32893496)
TBH This response is way too aggressive for the original comment.

The facts stated are simply that today it is more efficient to encode video for remote graphical sessions because the X11 applications already changed a long long time ago to adapt to the modern world of GPUs and accelerated compositing. BW, latency, efficiency, everything became better because a super computer with thousands of cores can do that and lighten the load on the CPUs.

It doesn't say it doesn't work... It doesn't prevent you neither from running X11 or even booting up a PDP-11 if this is your favorite workflow!

Re:An X11 apologist tries Wayland by d110af5ccf on Monday September 19, 2022 @12:01AM (#32894152)
The problem is that the Wayland fans have a tendency (at least I feel) to significantly misrepresent things in their favor. Statements like "oh that's actually more efficient on Wayland". No, Wayland is incapable of the sorts of optimizations X can do by design. It is only more efficient if the X app is doing things in a specific way that doesn't take advantage of huge parts of the X protocol. Granted, most modern apps do exactly that at this point. That doesn't make such statements any less of a misrepresentation though.

A much more reasonable claim would be that the network transparency afforded by the X protocol adds significant complexity which is no longer utilized by the majority of mainstream apps today. As such there's a reasonable case for dropping all that complexity from the core system and leaving it to peripheral libraries to handle on a case by case basis for the apps that want to make use of it.

And the idea of lossy compression while using an image editing program being a desirable thing (as suggested elsewhere in this comment chain) is laughable. It's already bad enough reading text that's gone through lossy compression. I would never want compression artifacts while manipulating an image.

My impression of Wayland so far is that I like the technicals but absolutely detest the people I encounter pushing it as a solution (it's quite similar to Rust in that regard I suppose). They would probably meet less resistance if they took more care not to misrepresent the overall state of things. I'll leave the link to KDE Wayland "showstoppers" for reference. Certainly that list is far shorter today than it used to be and many (not all) of the items are now solely on KDE's end. Nonetheless, fanboys have been claiming that Wayland is "production ready" the entire time. https://community.kde.org/Plasma/Wayland_Showstoppers

I'll switch to Wayland once it "just works" out of the box in terms of app integration on stable distributions including things like screen capture, fractional scaling factors, color management, all the stuff that works on X.

Re:An X11 apologist tries Wayland by cycomanic on Monday September 19, 2022 @12:54AM (#32894416)
Well the people who are pushing wayland are the same people that are maintaining xorg, so I would argue they know what they are talking about.

I have also not heard of any one who loudly proclaims xorg is much beter and should instead be maintained to step up to actually do that.

Re:An X11 apologist tries Wayland by michaelmrose on Monday September 19, 2022 @03:19AM (#32895296)
Look at this very statement it's completely inaccurate in a trivial fashion that ought not required analysis but here we are.

The people who actually develop x or wayland are a tiny number of people. The people expressing opinions on the internet on tech is 1000x larger. The implications that the proponents are correct in their analysis because they develop it is fatally flawed if for no other reason than the subject is obviously not solely the tiny number of actual devs. Furthermore the arguments even of devs needs to stand on their own feet.

Look at the prior comments where someone complains that random crashes result in the entire session going down.

Who cares what anyone says about the theoretical design decisions regarding manifestly unsuitable tools.

Re:An X11 apologist tries Wayland by customkitchen on Monday September 19, 2022 @07:37PM (#32905630)
You can make all the arguments you want but it won't do anything meaningful. If those 1000x people expressing opinions have the necessary domain expertise, and aren't just tossing out their feelings on what they think might be cool or might be nice in a perfect world, then they should start contributing to these projects and fixing the bugs.

I mean, I think it would be cool if my PC never crashed. Isn't it easy and fun to say things like that?

Re:An X11 apologist tries Wayland by michaelmrose on Saturday September 24, 2022 @03:40PM (#32965928)
PCs running either Windows 10 or Linux with appropriate quality software and hardware almost never crash now so wish virtually granted I guess.
Re:An X11 apologist tries Wayland by ongy on Monday September 19, 2022 @12:58PM (#32900904)
You are saying that as if the part of the X11 protocol that's reasonable to run over the network was the better API that application developers are simply too lazy to use.

While the reality is, that toolkits (and applications) used to use those APIs and were revamped to use the DRI APIs and general bitmap based windowing. The old APIs don't support double buffering, access to GPUs with modern APIs (both opengl[indirect sucks] and Vulkan). They don't provide modern font rendering, or any kind of graphical effect (distortions) that UI people might want to play with.

They would be significantly worse for anything displaying animations and one of the most common client libs (libx11) is serial and thus horribly latency sensitive.

The advantage of VNC isn't lossy compression. Which isn't forced by it either. But it handles networking better with bitmaps. And has improvements like acting as a screen/tmux style connectable session for graphical applications. Both VNC/RDB can also support showing the server's desktop if it has one, not just running other applications than currently open elsewhere.

The only advantage of old style X11 was that it's ubiquitous. But since it hasn't been used in ages since it doesn't work well with modern computers/UI frameworks that advantage is gone. And there's 0 reason to try and reimplement that in a new windowing protocol, when there's objectively better choices out there already. Local optimized windowing is a different beast than network capable.

Re:An X11 apologist tries Wayland by customkitchen on Monday September 19, 2022 @07:51PM (#32905757)
You might also want to note that the fantasy of being able to use the same protocol to drive the local display and also operate over a network, is long dead. It seems like a clever idea but it doesn't actually work. It ceased to be a thing entirely the moment wide area networks became popular. The local and remote cases are two completely different situations that need their own individual attention. Even when developing against X11 protocol you still have to consider this in modern times because the DRI extension is not available over the network.

Compare to a protocol like RDP which is extremely optimized for efficient and secure network operation, but is also way more complicated as a result, and it would be foolish to use it on a local display server.

Re:An X11 apologist tries Wayland by ziftface on Monday September 19, 2022 @09:20AM (#32897928)
It does just work for some workflows. I think that's really what it boils down to. It is production ready for some people, but it's clearly not for you yet. Maybe that will change.
Re:An X11 apologist tries Wayland by Amezarak on Monday September 19, 2022 @06:06AM (#32896332)
Yes, I see this come up again and again. Meanwhile, I use X11 over the network every day with Firefox, GIMP, various custom apps, and a zillion other things. And it works fine, and great, and VNC isn't an option for most of it for me.
Re:An X11 apologist tries Wayland by customkitchen on Monday September 19, 2022 @07:32PM (#32905593)
>and I'm not really interested in hearing that my own experience with it working well is a lie or some trick.

Your own experiences with it aren't a lie, but they're probably based around ignoring the last 20-30 years of advancements, and ignoring many actual statements from the X11 developers saying that it's bad for remoting.

>Wayland gives up some things

Well in the case of X11 fowarding, no it doesn't. That still works.

>Also, those of us who use non-mainstream window managers (such as Window Maker) are not interested in hearing that we should switch to some UI which doesn't support our workflow just because it's more fashionable these days.

By insisting on using these obscure, non-mainstream and under-maintained environments you are setting yourself up for an extraordinary amount of pain for very little benefit. The more time you spend avoiding the issue the harder it gets to figure out how to adapt your workflow to something else. I'm sure you understand that more deeply than anyone else here. So why keep up with the charade? It is not doing you any favors. At some point we have to let bad habits die.

Re:An X11 apologist tries Wayland by torginus on Monday September 19, 2022 @03:30AM (#32895379)
If you're not afraid of big brother, I can recommend Chrome Remote desktop. You just install a server on the shared machine, and you can access your stuff using a regular browser thanks to the wonders of WebRTC.
Re:An X11 apologist tries Wayland by j1elo on Monday September 19, 2022 @04:15AM (#32895637)
I recently had to uninstall Chrome Remote Desktop, because it was breaking my (Ubuntu) system's ability to handle some basic permissions, such as mounting USB disks.

It turns out that CRD is well known for breaking other seemingly random things, such as accessing your printer:

https://askubuntu.com/questions/1196248/automount-when-click...

Re:An X11 apologist tries Wayland by baq on Monday September 19, 2022 @03:37AM (#32895425)
> By the way, does anyone know of a VNC-like solution that can use MPEG compression?

try this: https://xpra.org/

Re:An X11 apologist tries Wayland by stuaxo on Monday September 19, 2022 @04:33AM (#32895769)
Not sure on the exact compression but I'm sure Nomachine/NX must use some video compressing n, I'm even able to watch video over it without it dying.
Re:An X11 apologist tries Wayland by aappleby on Sunday September 18, 2022 @10:52PM (#32893753)
Parsec, I think?
Re:An X11 apologist tries Wayland by satya71 on Sunday September 18, 2022 @09:31PM (#32893281)
I think TurboVNC had some extensions in that direction. But it’s been a while since I looked at it.
Re:An X11 apologist tries Wayland by mark254 on Monday September 19, 2022 @05:13AM (#32896038)
> By the way, does anyone know of a VNC-like solution that can use MPEG compression?

You want xpra.

Re:An X11 apologist tries Wayland by LtWorf on Monday September 19, 2022 @09:27AM (#32898003)
but doing ssh -X is scertainly easier than setting up vnc.
Re:An X11 apologist tries Wayland by POPOSYS on Monday September 19, 2022 @12:20AM (#32894239)
X2GO is the way to go!
Re:An X11 apologist tries Wayland by cbm-vic-20 on Monday September 19, 2022 @12:25AM (#32894268)
> my understanding is that the whole X11 is network transparent thing worked great when apps used the X11 drawing primitives.

It did. It was awesome to be able to run one of the expensive academic apps from any X terminal on campus. Network security was largely non-existent then, and you could run X apps not just across campus but across the Internet. I remember a really early web page that had a text field (for your host name) and a button that would start a particular app on their side and would display on your local X server. It wasn't very fast.

Anyway, all that died as Athena and Motif began to look dated as newer applications in the mid-90s started using more and more bitmaps.

Re:An X11 apologist tries Wayland by Rediscover on Monday September 19, 2022 @05:33AM (#32896148)
Completely off-topic, and I wish I could DM You without extra spam here, but great handle. Commodore Business Machines... Ever use a PET? Loved those things.
Re:An X11 apologist tries Wayland by moomin on Sunday September 18, 2022 @07:53PM (#32892610)
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.

Re:An X11 apologist tries Wayland by taeric on Sunday September 18, 2022 @10:33PM (#32893644)
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.
Re:An X11 apologist tries Wayland by cycomanic on Monday September 19, 2022 @12:51AM (#32894400)
The problem with X over the network is not bandwidth it is latency. The X11 protocol is very chatty so even very simple things will cause several roundtrips which makes X over the network so painful.
Re:An X11 apologist tries Wayland by destructionator on Monday September 19, 2022 @10:52AM (#32899148)
> The X11 protocol is very chatty so even very simple things will cause several roundtrips which makes X over the network so painful.

This simply isn't true. Some operations require roundtrips, drag and drop comes to mind, but very simple things absolutely don't. Events come one way, draw commands go the other.

Re:An X11 apologist tries Wayland by cycomanic on Monday September 19, 2022 @12:57PM (#32900898)
Well that's not what the xorg website says: https://www.x.org/wiki/Development/Documentation/Performance...

Essentially xlib is latency limited because its a synchronous protocol. Xcb can help if you redesign your applications for it, but we are talking about old applications (motif...)

Re:An X11 apologist tries Wayland by destructionator on Monday September 19, 2022 @03:25PM (#32902751)
You know xcb and xlib are just different client libraries for accessing the exact same wire protocol, right?

Moreover, notice the example they gave there is atom interning, which is a roundtrip on the wire (though you can batch them even in xlib...), and they say "most real applications will see less benefit than this" since that's the worst case - most applications do atom work at startup, not in the main use cycle, which is famously both async and buffered (it used to be a FAQ on xlib tutorials reminding people to run the event loop, and error handling is complicated a bit by it).

Re:An X11 apologist tries Wayland by taeric on Monday September 19, 2022 @12:53AM (#32894413)
Though, even there, networks are far faster than they used to be. Especially for the size is windows they used to push.
Re:An X11 apologist tries Wayland by Schroedingersat on Monday September 19, 2022 @03:26AM (#32895342)
Latency hasn't really improved. Dial up or isdn to nearby cities was 25-50ms. Same as I get with hfc or 5g. Cable was slightly better where it was available. International pings got much worse from australia in the 2010s but since improved roughly back to where they were.

Bandwidth has increased by 3 orders of magnitude though.

Re:An X11 apologist tries Wayland by icedchai on Monday September 19, 2022 @11:54AM (#32900038)
Dial up latency was never that low. ISDN, yes, but traditional dialup modems were pretty bad. The analog-to-digital conversion introduced a couple hundred milliseconds of latency.
Re:An X11 apologist tries Wayland by toast0 on Monday September 19, 2022 @06:59PM (#32905318)
I remember having latency under 100 ms within the metro area, but I could easily be misremembering, and I don't have a PPP account anymore to test. (And I'd have to visit my MIL who has a real POTS line with it's low latency)... But I did find a reference mentioning 150 ms round trips regionally, which I think was US west/east/central, so I think this 150ms is including some intercity latency as well.

https://web.archive.org/web/20160305000336/http://www.thefre...

Re:An X11 apologist tries Wayland by icedchai on Wednesday September 21, 2022 @10:45AM (#32925916)
Hmm. Wikipedia is claiming 150 ms latency on dialup: https://en.wikipedia.org/wiki/Dial-up_Internet_access

I remember higher, but it's been over 20 years now (we got broadband pretty early here), so who knows.

Re:An X11 apologist tries Wayland by Schroedingersat on Monday September 19, 2022 @03:22AM (#32895318)
Latency hasn't really improved. Dial up or isdn to nearby cities was 25-50ms. Same as I get with hfc or 5g.

Bandwidth has increased by 3 orders of magnitude though.

Re:An X11 apologist tries Wayland by hakfoo on Monday September 19, 2022 @12:19AM (#32894235)
I think one thing that sort of disappeared was the vision of thin clients everywhere. X11 is an obvious thin-client solution.

Thin client for home use seems like a winning proposition. Rather than giving the kids a Raspberry Pi 400 or garage-sale P4 when they want their own computer, you could hook up another X terminal to a large shared Ryzen box. The hardware gets more efficiently used, files can easily be shared and centrally backed up, and nobody ends up being the guy with the cast-off or otherwise inferior PC.

Re:An X11 apologist tries Wayland by moring on Monday September 19, 2022 @01:16AM (#32894531)
I think quite the opposite happened, just not on X11 level. The web browser is essentially a thin client nowadays. The fact that you have full client-side scripting is one thing that was IMHO a bit underdeveloped in classical thin-client systems because with that you can mask network latency much easier (though, admitted, I don't know a lot about how X11 handles this).
Re:An X11 apologist tries Wayland by moomin on Tuesday September 20, 2022 @07:44AM (#32910402)
Don't agree at all. The web browser is essentially a standardized computer on which to run your fat client systems like SPAs. The browser can run arbitrary computation locally.
Re:An X11 apologist tries Wayland by moomin on Tuesday September 20, 2022 @07:47AM (#32910419)
The problem being that X thin clients back then were more powerful than desktop PCs at the time. Even now they're more expensive than a Raspberry Pi, so it's more economically efficient to buy one of those.
Re:An X11 apologist tries Wayland by kaba0 on Monday September 19, 2022 @02:12AM (#32894835)
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 by pjmlp on Monday September 19, 2022 @02:07AM (#32894802)
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 by testermelon on Sunday September 18, 2022 @06:36PM (#32892133)
> These days a significant number of X11 apps just render _everything_ "server-side" as bitmaps and then send them over the wire to the client to composite them.

Inferring from the quotation, I take it you mean application server-side (instead of display server-side)? Just confirming.

Re:An X11 apologist tries Wayland by gunapologist99 on Monday September 19, 2022 @03:33PM (#32902847)
Exactly. If GP doesn't even know how X11 works, then the opinion probably shouldn't carry a lot of weight.

The "server" in X11 is the display that's sitting in front of you, not the application running on a remote workstation.

Re:An X11 apologist tries Wayland by retcore on Monday September 19, 2022 @05:15AM (#32896050)
>which will give much better performance on low-bandwidth connections,

Er, IRIX was pushing 12 bits and alpha channel around over X on twisted pairs c.a. 1993.

Re:An X11 apologist tries Wayland by destructionator on Monday September 19, 2022 @10:45AM (#32899034)
> since those protocols do damage detection, only sending updates of what's changed

So does X.

> and (lossy) compression.

This is legitimate though, the X protocol has no support for any kind of bitmap compression and it can sometimes be pretty painful. Though internets getting faster and faster too so it isn't necessarily a big deal especially since it does have bitmap caching and some display-side rendering capabilities, but it sure would be nice if you could send other formats on the wire.

Re:An X11 apologist tries Wayland by ciphol on Monday September 19, 2022 @04:50AM (#32895876)
Is there a user-transparent way to run Gimp over RDP/VNC, similar to "ssh -X" for X11?
Re:An X11 apologist tries Wayland by razemio on Monday September 19, 2022 @04:55AM (#32895911)
If I understand you correctly, yes. freexrdp has an option to render only a single window instead of the hole desktop. This works amazingly well and feels native. This is the trick WinApps uses.

You could either use WinApps or create your own script and add it to a desktop entry. Users can then open RDP Gimp like any other application without even noticing.

Re:An X11 apologist tries Wayland by cat_plus_plus on Sunday September 18, 2022 @11:27PM (#32893963)
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.
Re:An X11 apologist tries Wayland by kaba0 on Monday September 19, 2022 @02:14AM (#32894845)
There are lossy and lossless compression algorithms.
Re:An X11 apologist tries Wayland by ncmncm on Monday September 19, 2022 @02:16AM (#32894865)
The roles of client and server being force-swapped is another perhaps unfortunate development.
Re:An X11 apologist tries Wayland by msh on Monday September 19, 2022 @05:25AM (#32896108)
Why?

I think who should be client and who should be server is entirely context/application specific.

Sometimes I want to be able to connect to a server from any random client and continue the session.

Re:An X11 apologist tries Wayland by ncmncm on Monday September 19, 2022 @05:49AM (#32896237)
Because now you never know which is which without a separate explanation. Might just as well call them A and B.
Re:An X11 apologist tries Wayland by scottlamb on Sunday September 18, 2022 @06:16PM (#32892018)
> 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 than the current implementations.)

Remote heavy computations, like AI workloads and compilation? Definitely.

Remote GUI code? No ugh. Compare the experience of VS Code Remote vs just running VS Code remotely with ssh X11 forwarding, using a high latency connection.

You are fighting the speed of light. It won't go well.

Re:An X11 apologist tries Wayland by gnull on Sunday September 18, 2022 @08:55PM (#32893042)
I never had to do it myself, but I have a feeling it will work better with Wayland. The delay of 50-80ms introduced by the network is not terribly much (everything under 110ms is fine for playing Dota), so if your software doesn't lag itself, like X11 did, maybe it will work.

You could also use something like Zerotier-one to recover from network being shortly disrupted. This service connects your machines into a virtual network with static IPs, so the IP addresses through which your machines talk will stay the same and TCP connections will recover and ssh will keep working if a device briefly goes offline.

Re:An X11 apologist tries Wayland by rcoveson on Monday September 19, 2022 @02:02AM (#32894774)
> The delay of 50-80ms introduced by the network is not terribly much (everything under 110ms is fine for playing Dota)

I don't think you're giving the Dota client enough credit there. Game clients don't wait for network to pretend to respond to user input, because it absolutely is noticeable at 100ms latency. Instead, they predict as much as they can client side and display it as fast as possible. For this reason, the client is not at all thin. It knows how to run the whole program by itself. Not so with remote X11. With remote X programs, the client doesn't know what happens on click for anything, so the user really does get hit with a 100ms delay for every interaction with the program.

Re:An X11 apologist tries Wayland by gnull on Monday September 19, 2022 @10:22AM (#32898728)
You're right. I just tested it connecting from laptop in Sweden to a VPS in Sweden through a German VPN server. The total ping was 30-40ms, and running `waypipe ssh remote firefox` was right on the edge of being unusable. Navigating and clicking on links was fine with a bit of delay, but typing when the feedback is delayed is annoying.

Although if I connect to something that's 20ms away (within the same country), the experience is really good.

Re:An X11 apologist tries Wayland by sph on Monday September 19, 2022 @02:42AM (#32895049)
50-80ms of non-predicted input lag is not terribly much? Surely you must be joking.

Dota is fine because it has network prediction and a finite and well defined set of inputs.

And that's also ignoring video compression artefacts which are that you introduce if you send a modern GFX pipeline across the network. Computers screens can no longer be described with just filled rectangles and text.

Re:An X11 apologist tries Wayland by pjmlp on Monday September 19, 2022 @02:10AM (#32894818)
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 by bluedino on Sunday September 18, 2022 @07:12PM (#32892361)
NICE DCV works really well as a remote Linux desktop. Not sure what it runs underneath.
Re:An X11 apologist tries Wayland by scottlamb on Sunday September 18, 2022 @08:57PM (#32893059)
It's certainly possible to do better than raw X11 across the network. Other folks mentioned VLC, RDP, and NX too. I assume these protocols reduce bandwidth usage by compression. Sometimes you can even do prediction (as with mosh for ttys or Stadia for games).

The best is always going to be to use a local copy of the logic and data needed most frequently/immediately. E.g. in the VS Code example, they keep the buffer you're editing locally, the logic for cursor movements, the errors you're flipping through, and maybe even some precached autocompletion/highlight stuff. You don't have to wait for a round trip to see your keystrokes show up. That's the advantage of splitting the system in the right place.

Re:An X11 apologist tries Wayland by bayindirh on Sunday September 18, 2022 @06:34PM (#32892118)
I don't know whether you used Remote X, but I used it in a project, and it's extremely inefficient, esp. in thin client applications, and if you try to carry anything like a video, a 100mbps connection could easily be saturated by one pair of X server and client. In other words, it doesn't work in any way unless you have a gigabit LAN.

NoMachine developed a couple of libraries called NX back in the day, which transferred images and image deltas over with high compression. We used this instead via in the same project (with X2Go), and I reimplemented the same stack to my university where 20 something users connected remotely to a single "terminal" server to do remote research, and it worked like a charm.

While I like Remote X, it's still very inefficient even today. So, unless it's made extremely efficient over normal internet, over residential connections, it won't be missed.

Moreover, the rarity of projects using Remote X, or abstracting it with libraries like NoMachine kinda validates the idea is the feature is considered a novelty and not used much.

While I like the feature, I have feeling that it won't be missed or sought after much.

On the other hand what killed X is its code state, rather than the complex architecture. It's haphazard development over the years which made the code unmaintainable.

Addendum: Remote X made sense back in the day. Carrying minimal data, mostly terminal windows between terminals and central mainframe/time sharing system, over relatively short distances. I guess it's never designed and considered for long distances like today's internet, hence it's left to the wayside.

Re:An X11 apologist tries Wayland by aliqot on Sunday September 18, 2022 @06:45PM (#32892207)
Remote X has been a godsend for me. I'm not always able to lug around a worthy machine, so being able to use lesser hardware as a 'thinclient' to my wireguard'd assets is very handy. Obviously I'm not going to expect high definition video or realtime gaming, but that's not what it's billed as either, so within the scope of what it's for I'm wholly satisfied.

People on both sides sound somewhat fanatic, and I've never understood that. I just want to use what serves me best with the fewest interruptions.

I ran wayland for 3 years in various forms, and could not reconcile the bumps and stumbles in the process. Maybe next year I'll give it a shot again. There has to be something that it's doing for everyone for me to be hearing this much about it still.

Re:An X11 apologist tries Wayland by jacob019 on Sunday September 18, 2022 @08:11PM (#32892749)
xrdp is so much more comfortable to use than X forwarding. A PITA to set up though. VNC is a sensible choice too.
Re:An X11 apologist tries Wayland by jeroenhd on Sunday September 18, 2022 @08:43PM (#32892953)
I'm so glad modern GNOME has xrdp support built in. It's just a toggle in the settings.

My previous attempts to make it work have ruined the standard configuration so I'll probably need to do some serious purging/reinstalling to get it to work, but for new installs I'm sure remoting into GNOME must be a LOT easier.

Re:An X11 apologist tries Wayland by fsckboy on Monday September 19, 2022 @04:36AM (#32895787)
can xrdp or vnc display individual remote windows on my local desktop side by side with local windows? I don't want to import an entire remote desktop. That's what I've always used X for, with seamless mouse X select and middle button paste.

> more comfortable to use than X forwarding. A PITA to set up though.

X port forwarding is painless, not sure what aspect you're referring to?

Re:An X11 apologist tries Wayland by jacob019 on Monday September 19, 2022 @09:19AM (#32897921)
Yes, it is possible to display individual windows with rdp. X forwarding works ok with a fast LAN, it's very slow to draw over a slower link. SSH compression can help a little. If it works well for you then that's awesome, keep using it.
Re:An X11 apologist tries Wayland by aidenn0 on Monday September 19, 2022 @02:24AM (#32894928)
Is it more of a pain to setup then just running freerdp-shadow-cli?
Re:An X11 apologist tries Wayland by jacob019 on Monday September 19, 2022 @09:44AM (#32898193)
I use xrdp for headless remote sessions, and vnc for remote access to live sessions. I'll give freerdp-shadow-cli a try, thanks!
Re:An X11 apologist tries Wayland by jacob019 on Tuesday September 20, 2022 @06:15PM (#32918529)
Tried freerdp-shadow-cli, didn't work very well. Vinagre RDP client was unable to authenticate at all and just showed a black screen. I only knew that it was an authentication issue due to the server log. FreeRDP client didn't work with my multimonitor setup, it only showed the secondary screen. It doesn't scale the display properly either. The client must be set to the same resolution as the host. I'll be sticking with VNC for screen sharing, and continue using RDP for headless sessions.
Re:An X11 apologist tries Wayland by misnome on Sunday September 18, 2022 @06:50PM (#32892233)
> Moreover, the rarity of projects using Remote X, or abstracting it with libraries like NoMachine kinda validates the idea is the feature is considered a novelty and not used much. > While I like the feature, I have feeling that it won't be missed or sought after much.

It’s not used or won’t be missed _by you_. It’s extensively used today by science and HPC facilities and clusters, where it’s at best complementary to things like NX (with the problems of basically having a second desktop instead of integrating into the existing system), but often the only option for remote GUI to heavier duty systems available, not to mention the remote OpenGL capabilities which although out-of-date and clunky, allows more efficient local rendering than just streaming bitmap deltas.

Re:An X11 apologist tries Wayland by bayindirh on Sunday September 18, 2022 @06:53PM (#32892246)
As an HPC cluster administrator, I (and my colleagues) don't see its use on our clusters, either.

Instead, researchers either post process their data in the user interface and download it to visualize, or get the raw results and post process and visualize in their systems.

Once in a blue moon, a user generates some output window which requires very few interactions to look at their preliminary data, that's all.

Re:An X11 apologist tries Wayland by mbreese on Sunday September 18, 2022 @10:51PM (#32893739)
Yeah, I’m an HPC user (and small cluster admin by necessity). Remote X11 windows haven’t really been common for years. Occasionally you’ll see an Rstudio server instance, but this is tunneled through an SSH port forward and uses HTTPS.

The last time I needed and X11 remote session in a cluster, it involved Matlab and some kind of toolkit.

The performance of using a GUI remotely is nothing compared to just copying a terminal figure through an SSH tunnel and viewing the figure locally. I’d say that the low performance of remote X11 was the biggest factor in this shift.

Re:An X11 apologist tries Wayland by skybrian on Sunday September 18, 2022 @06:55PM (#32892257)
Also, I suspect that the bandwidth used by a typical X app was far lower back when it was invented. I remember seeing some greyscale X terminals, and probably not many levels of grey either.
Re:An X11 apologist tries Wayland by fulafel on Monday September 19, 2022 @03:18AM (#32895287)
It's interesting how our networks have gotten relatively much slower. When X11 was designed and for a long time afterwards, networks were fast enough. But now end user networking performance has plateaued much earlier and faster than computing power and app bandwidth requirements.

100M became the norm in the mid 90s, 1G in the mid 00s, but there was no 10G norm in 2010s or 100G norm in 2020s, we're still at almost the same spot of the curve 20 years later. Save for some tragicomic attempts at 2.5G etc end user networks.

Part of the reason of course is wireless, apps adapted to flakiness and bandwidth unpredictably alternating between slow and very slow, and also last mile consumer uplinks adapted to this.

Re:An X11 apologist tries Wayland by bayindirh on Monday September 19, 2022 @03:27AM (#32895351)
I think it has two reasons, first the price of the hardware required to do these speeds (plus the cable requirements + range limits), and WiFi.

These slowdown is offset by improvements in video and audio codecs, transparent compression and better static compression formats.

So, having 100mbps WAN connection at home is arguably provides more utility than having 100mbps 5 years ago.

Unless you do professional photo/video work, a 10G connection at home makes no sense. A good 802.11AC network plus some gigabit nodes is more than enough for a nice smooth experience at home, for most people.

P.S.: As a sysadmin, I know delights of having a lightning fast network at any place you live/work, but no, I'd rather spend time with my family rather than maintaining that.

Re:An X11 apologist tries Wayland by fulafel on Monday September 19, 2022 @03:42AM (#32895451)
The price of hardware is a red herring. All the other ethernet hardware was also pricey at start and then with volume became cheap. The cost and volume normally develop hand in hand (into opposite directions).

And yes, our apps adapted to working with less bandwidth. We don't know what kind of apps and computing we would have in the alternative universe where the norm would have been 10G connections 10 years ago.

For example lots of P2P stuff has been badly hampered by performance problems resulting in the centralization of the net in hands of big players.

There are lots of hard problems resulting from bad connectivity that result in big $$ tech funneling traditional net uses onto their services, by investing engineering efforts (and complexity) into heroic engineering feats to work around the bad connectivity. The complexity means high barrier to entry to compete with them. Codecs yes but also clever distributed caching, cloud storage, UIs that predict what the user does next, video calls have to go through corporate encoding/multiplexing proxies instead of p2p, file sharing has to be of the hard "sync most likely needed needed files" variety with proprietary server side smarts, instead of just "mount remote share", etc.

Re:An X11 apologist tries Wayland by nikau on Sunday September 18, 2022 @07:49PM (#32892575)
A long time ago I used a Citrix xserver that translated everything to ica, it was very fast and hid the latency well even over an isdn connection.
Re:An X11 apologist tries Wayland by Rediscover on Monday September 19, 2022 @05:51AM (#32896248)
By any chance, was that at Boeing?
Re:An X11 apologist tries Wayland by nikau on Monday September 19, 2022 @10:19AM (#32898693)
Nah it was an Australian finance company running some in house trading and market data apps.

Would have been very late 90s I think.

I remember it was even faster than the Windows ICA apps at the time which I think were hosted on a NT4 Citrix server.

Curious to know if Citrix even sell the Xwindows version any more.

Re:An X11 apologist tries Wayland by skykooler on Sunday September 18, 2022 @06:08PM (#32891950)
On the other hand, this works increasingly poorly as most desktop environments and software assumes there is no network involved (for example, last time I tried running Firefox over a forwarded X session I got a bunch of errors about a broken GL context). And you can do the same thing, with usually better results, by using VNC instead (and there are indeed VNC servers for Wayland, for example wayvnc).
Re:An X11 apologist tries Wayland by ajb on Sunday September 18, 2022 @11:14PM (#32893889)
Just had to use Firefox remotely (to use WeTransfer to ship a giant file, they dropped support for their cli, grr), and had exactly this issue - it works incredibly slowly over X over SSH. In the end had to use vnc over SSH.

(Note that tightvncserver seems to silently ignore the -localhost option now, which means it's completely insecure to run on an internet connected machine. Tigervnc still has the option)

Re:An X11 apologist tries Wayland by benibela on Tuesday September 20, 2022 @02:07PM (#32915581)
The issue is the new webrenderer or how it is called. There are options in about:config to disable it and force the old webrenderer.

Then it can runs rather fast on X over SSH in LAN and somewhat okayish through the internet.

Ten years ago I was using it all the time and it was very fast over the internet and perhaps even through Tor. I do not know how they could mess it up so badly

Re:An X11 apologist tries Wayland by fsckboy on Monday September 19, 2022 @04:45AM (#32895845)
I'm not sure what experience you're describing, for me the real crime trying to run a remote Firefox over a forwarded X session is that it figures out you're doing that and instead decides to run another window of your local Firefox instance. It's been like that a few years now. I can't imagine what they're doing under the hood, haven't looked into it, but it sure is irritating.
Re:An X11 apologist tries Wayland by drdec on Monday September 19, 2022 @07:30AM (#32896923)
It's not detecting that you are trying to run remote. That's just the default behavior of the firefox command, to use the running instance of there is one. IIRC, there is an option you can pass on the command line to get around it.
Re:An X11 apologist tries Wayland by resoluteteeth on Sunday September 18, 2022 @06:08PM (#32891951)
Without x2go most apps aren't usable over the internet now because x11 was designed around assumptions that are no longer correct and you end up with multiple round-trips during rendering.

Even X2go provides an experience that's strictly worse than using windows via rdp.

It just seems completely pointless to even bother with something x11's network transparency if you're designing an x11 replacement nowadays.

It would be much better to focus on a new vnc replacement for Linux that can use low latency video codecs when needed for games, etc.

Re:An X11 apologist tries Wayland by sprash on Sunday September 18, 2022 @06:27PM (#32892082)
> x11 was designed around assumptions that are no longer correct

Nothing could be further from the truth. If you use Xrender properly you can make very sophisticated drawing operations that are extremely efficient over the wire and that are GPU accelerated even when the process does not run on the local machine.

It is Gtk and Qt that for wahtever reason decided to ditch their Xrender backends.

> multiple round-trips

This is also a problem introduced by badly designed tool-kits like Gtk and Qt. It is trivial to design tool-kits in X11 that require no round-trips.

> It just seems completely pointless to even bother with something x11's network transparency

This is mostly true because desktop software on Linux is mostly written by highly incompetent developers that produced abominations like Gtk3+.

Re:An X11 apologist tries Wayland by amaranth on Sunday September 18, 2022 @08:46PM (#32892976)
> It is Gtk and Qt that for wahtever reason decided to ditch their Xrender backends.

It was often slower and more likely to run in to driver issues than just doing software rendering and sending pixmaps. They're now moving to GL and Vulkan because they can be faster and while they have the same risk of driver issues at least that's the same stack used for video games and CAD and such so more people care about it working well.

Re:An X11 apologist tries Wayland by sprash on Monday September 19, 2022 @01:04AM (#32894465)
> It was often slower

Any data on this? I can remember that your typical Cairo backend ran much faster on a PC from 2004 than todays GNOME/Gtk runs on current machines. If performance is your only argument you clearly lose with the modern GNOME/KDE + wayland stack. The only way you could make GLAMOR accelerated Xrender faster is by putting the spline tesselation step into a shader. (This was not possible when Xrender was introduced but can be done today without breaking any APIs)

Re:An X11 apologist tries Wayland by anthk on Monday September 19, 2022 @05:48AM (#32896227)
This. I remember KDE3 being fast as hell doing 2D with a GeForce2 MX, much faster than a Geforce 8200 trying to run a similar rendered desktop but with OpenGL doing Xrender's job.
Re:An X11 apologist tries Wayland by cycomanic on Monday September 19, 2022 @01:09AM (#32894490)
I saw a breakdown of how the X11 protocol over a network works (IIRC It was by one of the wayland proponents who also was a an xorg maintainer so he knew what he was talking about).

The protocol was very poorly designed everything needed essentially several trips back and forth between the client and server. That applies also if you're using Athena or motif widgets, it just becomes much worse with QT or gtk because they also transmit bitmaps, because otherwise they can't guarantee the look.

So it's latency not bandwidth which kills the performance. If you need 3 or 4 roundtrips just moving a window around, that's fine on your home network where you have a ping of 10ms, over the Internet with 100ms latency 3 roundtrips become 300ms so just a cursor move becomes painful.

Re:An X11 apologist tries Wayland by Sunspark on Sunday September 18, 2022 @07:22PM (#32892413)
You cannot say a developer is highly incompetent if you yourself do not have the ability to be at least as incompetent as them.

I agree there are problems with various stacks and widgets, but it isn't going to change anytime soon. At the end of the day, it requires someone who can create something from scratch, and those people are few and far between due to the amount of vision and work required. Especially if it's a non-paying task.

Re:An X11 apologist tries Wayland by customkitchen on Sunday September 18, 2022 @09:29PM (#32893268)
Most of your comment is pretty bad misinformation. X11 was not designed to use Xrender. That was an optional extension that came later. And on many drivers, the drawing of XRender is still not actually GPU accelerated either. Remember that XRender was designed long before GPU drivers were in the state they are now, back in the era when people still thought 2D acceleration was going to be a thing. And, XRender is extremely limited to a small handful of primitives that were mainly used to implement the postscript drawing model used by cairo.

It is also not trivial to reduce the amount of roundtrips in an X11 program. If the program uses Xlib then it probably needs to have significant portions of it rewritten to use xcb, which is a lot more complicated than it seems because Xlib handles a lot of caching and logic that xcb simply does not. In some situations X11 roundtrips are simply unavoidable. Complaining about GTK or Qt will not change this. Even if it were possible to fix those, there are less and less contributors to those projects who are willing to spend time to maintain X11 support.

Re:An X11 apologist tries Wayland by jcelerier on Sunday September 18, 2022 @06:32PM (#32892101)
Qt didn't ditch it. I use it all the time. If you have Debian it's compiled-in by default - just set QT_XCB_NATIVE_PAINTING=1
Re:An X11 apologist tries Wayland by customkitchen on Sunday September 18, 2022 @08:47PM (#32892986)
That flag has been broken for years: https://bugreports.qt.io/browse/QTBUG-70387

I doubt it will ever be fixed, because it offers no benefits when the application itself uses actual hardware rendering with GL or Vulkan. XCB can't speed that up at all.

Re:An X11 apologist tries Wayland by jcelerier on Sunday September 18, 2022 @09:00PM (#32893076)
...? the bugreport you pasted seem to have been fixed and merged 3 years ago.

The vast, vast, vast majority of the apps i use daily don't do any GPU rendering, just plain classic widget-based productivity apps

Re:An X11 apologist tries Wayland by customkitchen on Sunday September 18, 2022 @09:25PM (#32893236)
Sorry, I didn't clarify. The bug was fixed with some use of pixmaps, in other situations it's still broken.

It sounds like the vast majority of apps you use are very old. Even plain productivity apps benefit from GPU rendering. If they don't it's because those apps are far behind, compare to things like Electron apps where everything has been GPU accelerated for quite some time because of Skia.

Re:An X11 apologist tries Wayland by jcelerier on Monday September 19, 2022 @09:14AM (#32897853)
I find electron apps absolutely horrendous to use. The apps I use most are Zim, QtCreator, Strawberry, and the KDE apps: Okular, etc. - most of the time when I remote ssh it's for pavucontrol-qt, dolphin (the file manager) or mainly the app I develop, https://ossia.io (for instance for working on a show that is taking place over a raspberry pi). None of those force any kind of GPU rendering.

Also apps that do gpu rendering make my laptop really heat up and loose battery quickly compared to when it's not in use - I don't use a compositor partly for this (+ the occasional frame lag)

Re:An X11 apologist tries Wayland by customkitchen on Monday September 19, 2022 @12:19PM (#32900383)
That's not really relevant. You can personally choose to not use Electron apps, but many people cannot or do not want to choose to do that. Like it or not, it's a thing now. I've noticed a lot of developers seem to have this confusion that anyone else can avoid Electron. I guess you can if you spend all day in the terminal and the IDE but most other people cannot.

And that sounds like something is seriously wrong with your machine or your drivers. GPU rendering has massively improved performance and battery life on every machine I've ever tried. And especially on embedded devices with a low power mobile GPU, see for example here: https://social.librem.one/@dos/104984930233748319

Compositing should do so as well by avoiding unnecessary redraws. That sequencer would probably benefit greatly on a Raspberry by using GPU rendering, the screenshot even shows it rendering video and shaders...

Re:An X11 apologist tries Wayland by jcelerier on Monday September 19, 2022 @10:32PM (#32906988)
> Compositing should do so as well by avoiding unnecessary redraws.

I use a tiling WM so I doubt it would help much. If anything, if I run a whole system profile with perf, rendering does not even show up when compared to just running a git status here.

> That sequencer would probably benefit greatly on a Raspberry by using GPU rendering, the screenshot even shows it rendering video and shaders...

Sure, the video & shader parts use GPU of course. But for the main GUI, it can be rendered with OpenGL or with Qt's software renderer ; from my tests (and lord knows I've spent entire weeks profiling and doing everything I could to improve rendering performance) the OpenGL backend for the main GUI only becomes more worth it when using a 4k resolution - and GL is absolutely full of bugs on e.g. windows ; yes there are still people with GMA500 GPUs. Qt's software renderer has no issue rendering at a 1080 screen size on a Pi 3.

Re:An X11 apologist tries Wayland by prmoustache on Monday September 19, 2022 @04:23AM (#32895698)
Unless you are writing applications using motif and/or contributing to a better remote X11 experience, the why and how do not really matter if most popular applications are using GTK/QT and electron.

It was really nice and convenient at the time but it is going the way of the dodo the same way cars with manual gearbox are because almost nobody cares and there are other ways to connect remotely.

Re:An X11 apologist tries Wayland by fsckboy on Monday September 19, 2022 @04:52AM (#32895892)
> It just seems completely pointless to even bother with something x11's network transparency

this kind of statement astounds me. The internet is essentially based on network transparency, it's the gold standard for local area networking too. If it hadn't been invented yet and somebody just proposed a viable scheme to create network transparency, your eyes should light up with the possibilities... imagine a Beowulf cluster of these.

network transparency is what networks should provide, not for graphics, but across the board. It's the Apples and Microsofts of the world who don't give it to you both because they never understood it, and because it disrupts their walled gardens. You are thinking of a few network features that you want, and instead of conceiving it as properly architected orthogonal software features, you just want special purpose code for your two features (video and video games) in the current context.

Re:An X11 apologist tries Wayland by arghwhat on Monday September 19, 2022 @05:24AM (#32896104)
This is a big misunderstanding. Network handling is stripped from the core design, but is very much available on all compositors.

The equivalent to X11 forwarding is waypipe[1], which is far superior to X11 forwarding. Rendering happens entirely on the host and clients can therefore use accelerated resources as they wish, and the (accelerated) h264 encoded buffer feeds means much lower network utilization.

1: https://gitlab.freedesktop.org/mstoeckl/waypipe

Re:An X11 apologist tries Wayland by _flux on Monday September 19, 2022 @05:41AM (#32896187)
Low network utilization yes and perhaps superior to X11 core protocol, but it doesn't come for free, for example in terms of latency. And what if said app was actually a video player in it own self? Then you get to decode the video on server and re-encode it again for transport, whereas a primitive-centric protocol could allow decoding the original video directly on the client.

The higher the window size the higher the requirements for the encoder (though Waypipe does say "This way, Waypipe can send only the regions of the buffer that have changed relative to the remote copy.", or is it talking about the video encoder?), whereas with primitive-based systems the requirements are only correlated to the amount of changes done on the display—while still allowing to use image or video encoder for tasks better suitable for it.

I just fondly remember the times when (possibly two decades ago) I run

  xlockmore -mode ifs 
at work accidentally from my home computer and it was running fine over the 100Mbit network, so I didn't realize my mistake until coming back from lunch. Basically just a bunch of pixels running around smoothly, but I think it would be quite a quality test for a video encoder..

I understand though that coming up with a great protocol for user-interface primitives would be a research project in its own right, however. Perhaps something based on JavaScript, WASM, or EBPF fragments sent to the client would be a realistic options. Time has certainly gone past the primitives provided by X11.

But I also think that just "forget about it, we'll video stream it" is just giving up on the problem altogether.

Re:An X11 apologist tries Wayland by arghwhat on Monday September 19, 2022 @08:50AM (#32897652)
> Low network utilization yes and perhaps superior to X11 core protocol, but it doesn't come for free, for example in terms of latency.

You can have your cake and eat it too: You can disable the compression if it's a problem. It's highly configurable if you want to play with it.

The compression means trading a little bit of hardware resources at either end for a better UX (lower latency, higher throughput).

> The higher the window size the higher the requirements for the encoder (though Waypipe does say "This way, Waypipe can send only the regions of the buffer that have changed relative to the remote copy.", or is it talking about the video encoder?).

The core wayland protocol mandates communicating which parts of a "surface" (read: window) has changed when a new buffer is submitted in a "surface commit". Neither a compositor nor waypipe will do anything if nothing has changed.

> I also think that just "forget about it, we'll video stream it" is just giving up on the problem altogether.

Each surface has its own stream, and is updated independently. E.g., a video player on a webpage will generally be a subsurface, a context menu or plugin is a popup surface. They're all processed independently, with each their own damage tracking (and if applicable, video compression). If content is stretched or scaled up, only the original source buffer will be transmitted, allowing the display server to take care of this.

This is not giving up, this is the maximum effort, optimal implementation.

> I just fondly remember the times when (possibly two decades ago) I run ... over a 100Mbit network

For reference, a single 4k 60Hz display takes ~15Gb/s to keep fed with bitmaps. Even a quarter of the screen takes 3.7Gb/s. Not even cinematic refresh rates would be able to fit within a 1Gb/s line.

Re:An X11 apologist tries Wayland by _flux on Monday September 19, 2022 @11:42AM (#32899868)
> You can have your cake and eat it too: You can disable the compression if it's a problem. It's highly configurable if you want to play with it.

Well you've of course lost the game at that point if your surface is very tiny, given you have no primitives to express "write text hello at x, y" e.g. for a terminal; without compression the bitmap presentation of a terminal—or a text document—is very large. Scrolling will damage the whole screen.

> Each surface has its own stream, and is updated independently. E.g., a video player on a webpage will generally be a subsurface, a context menu or plugin is a popup surface. They're all processed independently, with each their own damage tracking (and if applicable, video compression). If content is stretched or scaled up, only the original source buffer will be transmitted, allowing the display server to take care of this.

That's pretty nice and better than I assumed! Some hardware has limited number of hardware video encoders, though, for example in NVIDIA 1080GTX it's four for the _complete system_. I think for this reason waypipe reuses the contexts for different surfaces, resulting in lost video quality? Without reuse I expect one to run out of contexts quite fast—and then you spill to CPU.

Video sending can be a nice way to provide remote frames because it naturally batches all drawing operations into one compressed frame and really works if your task is to send 4k 60Hz video. But can it really beat display server -side composition or even things such as text rendering? As a tool in the toolkit it's a very nice thing to have, but it shouldn't be the complete toolkit. For X11 Someone(TM) could implement XPutVideo.

I think the bad performance of many X11 apps is not inherent to the protocol but inherent to the programs written in synchronous style (libX11 included; libxcb fixes this), assuming immediate access to the display server, instead of putting in requests while waiting for the answer for previous ones. Worst offender: Virtualbox. Access to a local surface and sending that surface as a whole can be a good solution to such code. And this kind of code is possibly so common because doing everything asynchronously can be tedious, and even more tedious in some enviroments such as C..

Re:An X11 apologist tries Wayland by arghwhat on Tuesday September 20, 2022 @03:34PM (#32916684)
The X11 draw APIs are not really used outside stuff written in Motif or hand-written X11 clients like st. Instead, modern X11 clients sidestep all this for performance reasons and render on their own and post buffers (e.g. GLX, cairo, vulkan, whatever they may like). This means copying bitmaps when forwarding, over a protocol that is not made for doing so efficiently.

Sure, if an application is just rendering nothing but text through X (and not using e.g. pango rendering to a cairo context), and you do not prefer using the resources on the machine running the application rather than the one displaying it, and you don't care about performance when using the application locally, then X11's might be more efficient. But for a purely text application, SSH puts X11 and Wayland to shame.

Re: encoder limits, Intel Quick Sync (built into Intel CPUs since 2011) documentation suggests the only limitation there with respect to parallel encoding is whether or not you can keep up with frame-rate requirements - an old example being 10 streams at full HD 30fps. I believe waypipe only focuses on video-memory buffers right now for video encoding right now as a simple heuristic, as CPU memory (shm buffers) are only used for "low performance" content on Wayland.

> I think the bad performance of many X11 apps is not inherent to the protocol but inherent to the programs written in synchronous style ... And this kind of code is possibly so common because doing everything asynchronously can be tedious, and even more tedious in some enviroments such as C.

I believe even libxcb has forced synchronous parts, which are annoying Wayland compositor developers a lot as Xwayland-supporting compositors need a bit of X11 WM code.

The Wayland protocol is asynchronous by nature, and the primary client and server library exposes this with no synchronous pretenses in idiomatic C. Every function you call only queues a request that will be sent when your event loop dispatches next time, and when you receive events your event loop will fire callbacks in bulk.

Nothing is synchronous, and updating your window requires no wait. In the simple case, the only message you'll get back at some point is one informing you that the previous buffer can now be reused (buffer release).

Re:An X11 apologist tries Wayland by gnull on Sunday September 18, 2022 @08:44PM (#32892965)
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 giving up a lot. X11 was designed to work over network, but it never really did.

Re:An X11 apologist tries Wayland by benibela on Tuesday September 20, 2022 @02:08PM (#32915594)
The issue is the new webrenderer or how it is called. There are options in about:config to disable it and force the old webrenderer.

Then it can runs rather fast on X over SSH in LAN and somewhat okayish through the internet.

Ten years ago I was using it all the time and it was very fast over the internet and perhaps even through Tor. I do not know how they could mess it up so badly

Re:An X11 apologist tries Wayland by ur-whale on Sunday September 18, 2022 @09:55PM (#32893409)
> 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.

Re:An X11 apologist tries Wayland by gnull on Monday September 19, 2022 @05:46AM (#32896221)
Problem is horrible lags, and I mean just program working bad, not latency. I tried doing it with X11 now, and I gave up before I could even type "youtube" to address bar. Then I tried doing

  ssh -X remote firefox https://www.youtube.com/watch?v=XqZsoesa55w
and it wasn't better. I saw the new firefox window, but it stayed unresponsive.

And I bet part of the problem is due to Youtube (and browser generally) involving some non-trivial drawing technologies, rendering a video is not like showing a GTK interface.

Re:An X11 apologist tries Wayland by kaba0 on Monday September 19, 2022 @02:18AM (#32894876)
Wat?
Re:An X11 apologist tries Wayland by ur-whale on Monday September 19, 2022 @04:09AM (#32895604)
Streaming is most sensitive to how much data you can push through the pipe in a given amount of time, not to how long it takes for a question/answer pair to travel between the server and the client.

Latency (how long it takes for messages to travel back and forth), which is where X11 over the network has major issue, doesn't matter in the specific case of watching a video.

Essentially, once you press 'play', there's just a torrent of data flowing down from the server to the client with very little need for two-way banter between the machines.

Re:An X11 apologist tries Wayland by arghwhat on Monday September 19, 2022 @05:37AM (#32896169)
Yeah, no - X11 forwarding a video is at best "eh" when you're network local, and horrible otherwise. X11 forwarding burns a lot of bandwidth, and even when that bandwidth is available, going over TCP and SSH makes it implicitly quite latency sensitive.

It's not even fair to compare it to waypipe's h264 compressed buffer feeds.

Re:An X11 apologist tries Wayland by dbrgn on Monday September 19, 2022 @04:00AM (#32895548)
I guess GP meant input latency (since there's no input if you're just consuming a video stream).
Re:An X11 apologist tries Wayland by kaba0 on Monday September 19, 2022 @02:05AM (#32894787)
And any program not made with goddamn XMotif will be slow as fuck on anything non-ethernet.

It is a strictly worse solution to remote desktoping than what followed it — we are no longer drawing things with CPU and the things we draw are not 3 rectangles. A bitmap crossing the wire for an icon/image/whatever is insanely inefficient through the X protocol, you want to compress it with a modern compression algorithm for much better outcome.

Re:An X11 apologist tries Wayland by admax88qqq on Sunday September 18, 2022 @07:58PM (#32892644)
> While on the road, you can use your notebook to open a Gimp session on your home machine and edit an image stored there.

Have you ever tried this? I've never had X11 network transparency be a good experience.

It would be cool but to be good all apps would have to be designed with it in mind. And they are not.

The software moves on from X11 as a protocol for remote computing.

Even well before Wayland, all the things you'd use X over the network for were moved to web browsers.

Re:An X11 apologist tries Wayland by II2II on Sunday September 18, 2022 @08:38PM (#32892921)
> Have you ever tried this? I've never had X11 network transparency be a good experience.

I did, nearly 20 years ago. The computers were over 2500 km apart, though it was over a good university to university connection. The Gimp was certainly usable, though I will not go as far as saying it was good since 20 year old memories can be hazy and the standards of the day are different from the standards of today.

I also experimented with X over a 14.4 kbps modem a few years earlier. It was mostly while writing papers (plotting graphs and viewing dvi files, not the actual writing). It was slow, but it got the job done and was better than juggling documents between software on two computers.

The one really nice thing about X was the ability to use individual applications across a network connection, rather than dealing with an entire remote desktop. All of this remote desktop stuff strikes me as being better suited for accessing a remote system, rather than for running remote software.

Re:An X11 apologist tries Wayland by kaba0 on Monday September 19, 2022 @02:21AM (#32894902)
> The one really nice thing about X was the ability to use individual applications across a network connection, rather than dealing with an entire remote desktop

That sounds like a UX problem that’s quite trivial to fix, not a technical one and absolutely not inherent with Wayland.

Re:An X11 apologist tries Wayland by II2II on Monday September 19, 2022 @09:18AM (#32897901)
If you're talking about shipping a singular rectangular region across the network, possibly. Yet not all windows are rectangular and many applications use more than one window. Then there are issues with how the application interacts with the desktop environment, where the application thinks it is being on computer A when it is actually being displayed on computer B. It is not a trivial UX problem.
Re:An X11 apologist tries Wayland by gpm on Sunday September 18, 2022 @08:06PM (#32892717)
I've used it in the past month to impromptu demonstrate something that I had set up on a GUI app at home (with a lot of dependencies) from my laptop.

Yes, it's laggy, but it's nice to have the option, and it's really nice that it's already integrated with ssh and doesn't need extra setup (past passing `-Y` to ssh). If this was the only thing I'd lose by switching window managers it wouldn't be a dealbreaker.

Re:An X11 apologist tries Wayland by erik_seaberg on Sunday September 18, 2022 @08:45PM (#32892973)
This is what I keep coming back to. A backend that targets Javascript can take advantage of the desktop/laptop GPU. A backend that targets Wayland has to render everything locally in software (no GPU), and nobody I’ve ever worked for wants to build a system that runs this way.

Xaw and Motif worked okay, and it’s getting hard to imagine a heavy user who has access to only one computer, yet newer GUI toolkits have lost interest in X11 as a platform for remote rendering.

Re:An X11 apologist tries Wayland by kaba0 on Monday September 19, 2022 @02:22AM (#32894911)
You honestly believe that Wayland software are not GPU-accelerated?
Re:An X11 apologist tries Wayland by erik_seaberg on Monday September 19, 2022 @04:22AM (#32895682)
Our datacenters don’t have GPUs, Wayland doesn’t make my desktop’s GPU available to them, and local desktop-only software is getting pretty rare.
Re:An X11 apologist tries Wayland by kaba0 on Monday September 19, 2022 @11:15AM (#32899490)
That sound like a self-made problem. There are waypipe and several other options for using the desktop’s resources.
Re:An X11 apologist tries Wayland by erik_seaberg on Monday September 19, 2022 @04:18PM (#32903355)
I was excited about Waypipe until I read that it has to ship compressed pre-rendered video frames over the wire, and all the desktop can do is decompress and composite them. I believe VNC and RDP are much the same, sending bitmaps rather than structured GPU commands from the app.

We could expect everyone to start investing in datacenter GPUs, but architecturally “one GPU per display, plugged directly into the display” always made a lot more sense to me.

Re:An X11 apologist tries Wayland by kaba0 on Tuesday September 20, 2022 @01:48AM (#32908107)
As mentioned in the thread, X server does the same thing in practice as we are not using XMotif apps anymore with CPU rendering.

Icons, textures, all these things will be passed as bitmaps with X remoting, in a strictly worse way than a modern compression could do.

Re:An X11 apologist tries Wayland by mccorrinall on Sunday September 18, 2022 @06:07PM (#32891941)
I actually still use this feature a lot. I run some linux software on a server and can see the window on my main desktop without any need for rdp, vnc or similar. It’s really great!
Re:An X11 apologist tries Wayland by kelnos on Sunday September 18, 2022 @11:21PM (#32893931)
I used to use X11's network transparency features a lot in college[0], but it's been a good 20 years and I haven't used it since -- even once.

I, too, am not comfortable with throwing away such a potentially useful feature (though I believe there's a wayland "protocol" or something that allows for network transparency now), but I personally don't have a need for it.

[0] One of our VLSI design labs was a FreeBSD lab, and the machines there had a bunch of proprietary/paid simulation software on them. It was amazing to be able to ssh in from my dorm room, and run those apps "locally", with access to all my files on the network share. A few of my classmates wondered why I never pulled all-nighters in the lab with them... I never needed to! They all ran Windows at home; back then it was pretty difficult (or at least just kinda unknown) to run an X server on Windows.

Re:An X11 apologist tries Wayland by galangalalgol on Sunday September 18, 2022 @11:31PM (#32893985)
I use it quite often. And I am dreading the day the office switches to wayland. I like having terminals open to several machines on the premises and being able to fire up individual applications from each. I don't really like having a workspace devoted to a vnc for each machine. It doesn't work as well. It makes me use the mouse more. I don't want windows into those machines. I want a gui on my machine hooked to the heavy lifting on another. I'm sure I'll adapt. But sonfar, its a productivity killer.
Re:An X11 apologist tries Wayland by melling on Sunday September 18, 2022 @06:51PM (#32892237)
“The Network is the Computer”

For a time I had lots of xterms, emacs sessions, etc running across the network. It’s a great feature.

Re:An X11 apologist tries Wayland by ISL on Sunday September 18, 2022 @06:15PM (#32892013)
I used X tunneling over ssh regularly from 2001-2020, when I left that line of work.

For some applications it is radically faster than other options.

Re:An X11 apologist tries Wayland by reidacdc on Monday September 19, 2022 @09:11AM (#32897830)
It's in the "critical path" for certain niche applications. I do HPC operations, and every now and then, I run across some (usually commercial) scientific software application whose installer and/or configuration manager is a GUI. I am not sitting in front of the cluster head-node, I am ssh'd in to it.

With X, I can just go ahead and fire up the GUI, and it will appear. Maybe a bit laggy, but as long as its only one application, it's usually good enough to complete the task I need to complete.

With remote work and thin pipes, it's laggier, but "xpra" also allows per-application X forwarding, and removes a lot of the lag.

Of course I could set up full VNC and set up a whole desktop environment on the cluster head node, and remote into it, and maybe in the glorious Wayland future, I will have to do that.

Sometimes when I talk about this, someone in the comments says that Wayland is working on some kind of per-application forwardability -- that would be nice if it's true.

I get that my use-case is niche, and so I don't expect it to be a high priority for the devs, but it's one of those things that, once in a while, is a critical link in my administrative workflow, and I'm not looking forward to the eventual kludging of workarounds.

Edited to add: I have now seen the comment below about "waypipe", this sounds very promising!

Re:An X11 apologist tries Wayland by xani_ on Sunday September 18, 2022 @08:46PM (#32892980)
I used that feature very rarely but the times I did it was insanely useful. Mostly running some debug software so debugging session could run locally but I could control it remotely, without installing whole graphical environment and somehow setting up vnc session just to run single app
Re:An X11 apologist tries Wayland by 2OEH8eoCRo0 on Sunday September 18, 2022 @06:13PM (#32891985)
> While on the road, you can use your notebook to open a Gimp session on your home machine and edit an image stored there.

How practical is that? I have horrible upload speed at home which ruins all these "just remote into your home machine" workflows for anything more than a terminal.

Re:An X11 apologist tries Wayland by loeg on Sunday September 18, 2022 @08:31PM (#32892882)
Not at all practical. Remote X11 isn’t really practical on a LAN, much less over a slower internet link. It’s cool in theory but not especially useful.
Re:An X11 apologist tries Wayland by atq2119 on Sunday September 18, 2022 @06:13PM (#32891990)
Realistically speaking, what matters is that openssh comes with X11 forwarding built-in.

Somebody should go and provide equally seamless "Wayland forwarding". That might end up looking more like VNC under the hood, but there's nothing inherently wrong with that.

Re:An X11 apologist tries Wayland by seba_dos1 on Sunday September 18, 2022 @06:50PM (#32892231)
Wayland forwarding has been there for years now: https://gitlab.freedesktop.org/mstoeckl/waypipe

Is it seamless enough for what you had in mind?

Re:An X11 apologist tries Wayland by aidenn0 on Sunday September 18, 2022 @07:45PM (#32892536)
I think GP was talking about how ssh has the -X and -Y flags for forwarding X, but you need to do something like -L XXXX:localhost:YYYY to ssh forward.

TigerVNC (and some others) will do e.g. "-via foo@bar :1" which GP might not know, but is rather convenient.

Xpra is still a better replacement for -X when launching a single application though.

Re:An X11 apologist tries Wayland by atq2119 on Monday September 19, 2022 @05:02AM (#32895970)
Yes, that's what I meant, and thanks, those are interesting points.

My main use case is launching one-off visualization tools on a remote system that I'm ssh'd to anyway. ssh -X is hard to beat in terms of convenience for that use case, and e.g. a persistence setup would be overkill.

Re:An X11 apologist tries Wayland by pedrocr on Monday September 19, 2022 @06:25AM (#32896459)
From the linked waypipe page the usage is:

    waypipe ssh <user>@<server> <app>
That will call ssh with the correct parameters on both sides and start the app. Seems just about perfect for what people want out of a remote solution that's not a full desktop.
Re:An X11 apologist tries Wayland by colordrops on Sunday September 18, 2022 @06:10PM (#32891961)
It's a lot more than just cool compositing effects. If you are just trying to get some work done reliably with a dynamic multimonitor setup, Wayland is vastly superior.
Re:An X11 apologist tries Wayland by aaaaaaaaata on Sunday September 18, 2022 @06:13PM (#32891994)
> This is a lot to give up for cool compositing effects...

Wait, you think this is what this is all about?

How about the cool security effects...?!

Re:An X11 apologist tries Wayland by dijit on Monday September 19, 2022 @02:33AM (#32894995)
Support for mixed DPI effects?

Lack of tearing without vsync… effects?

Re:An X11 apologist tries Wayland by tryauuum on Sunday September 18, 2022 @06:08PM (#32891949)
...and it's usually extremely slow, even if you are connected via 1Gbit wire.

Edit: replaced 10Gbit with 1Gbit. And also I love using this feature even with all its slowness

Re:An X11 apologist tries Wayland by tails4e on Sunday September 18, 2022 @06:46PM (#32892212)
I use remote display of apps daily as part or work. I've a Linux VM, and all compute or memory intensive programs run on LSF with x11 forwarding or via direct login. Sure desktop users don't need the remote part, but enterprise / high end compute definitely does
Re:An X11 apologist tries Wayland by wazoox on Monday September 19, 2022 @06:15AM (#32896390)
I use X11 remotely daily (and did so for 25 years). It comes for free with a simple ssh login and doesn't require setting up any server on the remote machine. It just works (even if slowly at times). It beats setting up x2go/VNC/etc hands down.
Re:An X11 apologist tries Wayland by mkl on Sunday September 18, 2022 @06:07PM (#32891940)
https://arewewaylandyet.com/ lists Waypipe as a kind of equivalent for that. I haven't tried it; does anyone know how well it works?

It also lists FreeRDP and wayvnc.

Re:An X11 apologist tries Wayland by kirbyfan64sos on Sunday September 18, 2022 @07:18PM (#32892398)
I've used it successfully several years ago, it was a bit rough around the edges but already worked well; I'd imagine that's only improved since.
Re:An X11 apologist tries Wayland by pizza234 on Monday September 19, 2022 @04:25AM (#32895708)
I'd be a big fan if that worked, but I haven't found an open remote desktop solution on Linux that works out of the box and acceptably fast¹, to the point that I have to use proprietary software to perform remote desktop sessions - there is a huge gap between the open solutions and the proprietary ones².

¹=they're all either incredibly slow, or clunky to configure/use. interestingly, X2Go, which I think was working out of the box, but was too slow, is based on an old version of the Nomachine (NX) protocol.

²=the recent RustDesk tries to fill that gap.

Re:An X11 apologist tries Wayland by arghwhat on Monday September 19, 2022 @05:32AM (#32896141)
waypipe[1] is the wayland equivalent people are looking for. It gives you the UX and ease of use of X11 forwarding, but with the performance and efficiency of things like RDP (which is gross, but can run quite well on Windows Server if you throw enough money at Microsoft).

Wayland applications will render entirely on the host using host resources and acceleration as needed, buffer content gets transmitted using (hardware accelerated) h264 encoding, while messages in general get passed as-is to give a fully local experience.

And it of course works over SSH.

1: https://gitlab.freedesktop.org/mstoeckl/waypipe

Re:An X11 apologist tries Wayland by lostapathy on Sunday September 18, 2022 @08:39PM (#32892925)
> That is, the Gimp runs on your home machine while your notebook has the GUI.

Have you actually tried that in recent years? In my experience not much actually works this way anymore, the performance is just terrible.

Re:An X11 apologist tries Wayland by lucb1e on Sunday September 18, 2022 @08:57PM (#32893060)
This. It takes hundreds of megabits per second to work smoothly.

If you're doing this while on the move, your mobile data is going to be gone in a literal matter of seconds, if the network were fast enough to support it, which it isn't so in reality you're going to be frustrated and wondering why you didn't use a different protocol. From VM to host or on gigabit LAN it works okay, which is where I've used it before.

I used X forwarding a lot until last year, so I can find various arguments for it, but "while on the move" makes absolutely no sense.

Re:An X11 apologist tries Wayland by mariusmg on Monday September 19, 2022 @04:27AM (#32895731)
>you can use

When was the last time you used this feature ?

X11 is a protocol designed for machines which didn't have the power to draw a GUI locally. That time has long passed.

Re:An X11 apologist tries Wayland by modeless on Sunday September 18, 2022 @06:52PM (#32892244)
RDP works better in practice than X11 over medium bandwidth and/or high latency connections. Nothing is being lost.
Re:An X11 apologist tries Wayland by tjoff on Monday September 19, 2022 @03:50AM (#32895508)
You don't loose anything.

Open up gimp remotely on the road, try it. It isn't usable ny any stretch of imagination.

That is why we need hacks such as x2go to make it usable.

Even the worst RDP solution is orders of magnitude better in performance than X11.

Re:An X11 apologist tries Wayland by mgraczyk on Sunday September 18, 2022 @11:00PM (#32893796)
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 prefer a web UI or a VNC/remote-desktop tool.

Re:An X11 apologist tries Wayland by dima55 on Sunday September 18, 2022 @11:03PM (#32893811)
X-forwarding (over ssh, or directly like this person is doing) is extremely useful and powerful. I use it this way, and I know plenty of people that do too. On top of that, wayland doesn't solve any problems that I have, so there's your data point.
Re:An X11 apologist tries Wayland by mgraczyk on Sunday September 18, 2022 @11:05PM (#32893830)
Sure, but my guess is that <1% of Linux users currently use X forwarding, and probably <0.01% of desktop OS users would ever want something like this. It's a cool feature that should exist, but rare enough that it doesn't need to be fundamental to desktop architecture.
Re:An X11 apologist tries Wayland by drdebug on Monday September 19, 2022 @02:10AM (#32894820)
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 by mgraczyk on Monday September 19, 2022 @02:57AM (#32895155)
I do something similar with vim, no gui. I use vim over ssh with tmux. Others I know use vs code with an ssh backend. These two make up the workflow of roughly 60000 Googlers. None of them need X forwarding.

Some people may benefit from X forwarding, but the vast majority of Linux users do not.

Re:An X11 apologist tries Wayland by drdebug on Monday September 19, 2022 @04:42AM (#32895823)
Your colleagues don't need X forwarding, so requirements from people that are not in the vast majority don't need to be addressed, they'll just have to use RDP/VNC even if it's a step backwards for them. Fortunately X11 is open source, so life can continue for those of us who need it.
Re:An X11 apologist tries Wayland by Shish2k on Monday September 19, 2022 @05:34AM (#32896153)
Same at FB - vscode with ssh backend is the recommendation, ssh+vim works perfectly fine; last time I checked X forwarding did work, but even with a multi-gigabit connection and 20ms latency it was too painful so nobody did that...
Re:An X11 apologist tries Wayland by phkahler on Monday September 19, 2022 @09:15AM (#32897858)
>> X client and server are usually the same machine, but they don't have to be.

When I was in college there were rooms full of X-terminals which would be used to remote into various bigger workstations. You could also sit locally at one of those machines, but plenty could be done over the network and by more people on lower cost hardware.

Re:An X11 apologist tries Wayland by michelb on Monday September 19, 2022 @04:07AM (#32895589)
I think that is a great feature. I'd also like to see how often it is used given today's workflows.
Re:An X11 apologist tries Wayland by lucideer on Monday September 19, 2022 @04:40AM (#32895805)
> This is a lot to give up

For whom?

Nobody is arguing it's not a great and powerful feature, nor that it's not "a lot to give up". The only argument posited is that not a lot of people will actually have to make that sacrifice (as not many actually use that feature). Is that not true?

Re:An X11 apologist tries Wayland by knorker on Monday September 19, 2022 @03:46AM (#32895475)
As someone who used to run actual X terminals, diskless purpose built appliances that only ran the X server, I'd say this only really worked on a LAN.

It never actually worked "on the road".

VNC and windows remote desktop was always better.

Re:An X11 apologist tries Wayland by zitsarethecure on Monday September 19, 2022 @08:18AM (#32897299)
X11 is way too slow to run something like gimp remotely, unless perhaps you are sitting near the other machine connected via gigabit ethernet. Giving that up is an easy win for better everything else.
Re:An X11 apologist tries Wayland by thedougd on Monday September 19, 2022 @02:48PM (#32902279)
This also gives you the freedom to remote selective applications rather than the whole desktop.

X11 remoting took me to a new level in college, when I needed to use Solaris workstations to complete assignments.

Re:An X11 apologist tries Wayland by diffeomorphism on Monday September 19, 2022 @01:07AM (#32894478)
Considering there is waypipe, what exactly is being "given up"?
Re:An X11 apologist tries Wayland by donatj on Sunday September 18, 2022 @07:35PM (#32892477)
A friend had an oscilloscope that worked like this. X across the network.
Re:An X11 apologist tries Wayland by seba_dos1 on Sunday September 18, 2022 @06:46PM (#32892209)
You don't need to have it baked into the core protocol for it to work. Waypipe works pretty well for running Wayland clients remotely.
Re:An X11 apologist tries Wayland by echelon on Sunday September 18, 2022 @06:13PM (#32891987)
> This is a lot to give up for cool compositing effects...

I've used networked X windows and it's always felt like a kludgy, crash-prone hack. The better solution is to render the entire desktop remotely and stream it over wholesale, such as with VNC and other protocols.

If companies like YC's Mighty have their way, the future will be thin-client based. And it won't be built on X Windows, because that's the wrong layer of abstraction.

Re:An X11 apologist tries Wayland by jcelerier on Sunday September 18, 2022 @06:34PM (#32892119)
streaming the entire desktop is an absolutely horrendous experience when compared to just ssh -X and running the app I want
Re:An X11 apologist tries Wayland by aseipp on Monday September 19, 2022 @03:38AM (#32895429)
Run 'waypipe ssh user@machine firefox' and you are done.
Re:An X11 apologist tries Wayland by XorNot on Sunday September 18, 2022 @06:53PM (#32892253)
Under Wayland you'd just be sending the window you want instead. RDP can do this too, the point is that rendering remote is just plain more efficient.
Re:An X11 apologist tries Wayland by luckydata on Sunday September 18, 2022 @10:58PM (#32893783)
It's nothing anyone actually needs.
Re:An X11 apologist tries Wayland by stefan_ on Sunday September 18, 2022 @06:14PM (#32891997)
X11 is the worst remote protocol in the world because save for about one year, it was never developed with that application in mind.