←back to thread

Ancient X11 scaling technology

(flak.tedunangst.com)
283 points todsacerdoti | 3 comments | | HN request time: 1.164s | source
Show context
compiler-devel ◴[] No.44371326[source]
Brilliant. This is another piece of evidence on the pile of why we got Wayland: it's because people who understood X11 mostly retired and everyone else couldn't be bothered to learn X11 because it's "yucky C code" or something. And it bothers me that we lose remote rendering with Wayland (unless one fights with waypipe) that was just built-in to X11. Yes, it was slow, but actually if you're running a VM on your local system and using SSH to connect to it, then it works great. Sigh. I'm an old person yelling at clouds.
replies(2): >>44371381 #>>44372366 #
nullc ◴[] No.44372366[source]
> Yes, it was slow,

Not particularly if you are on a low latency network. Modern UI toolkits make applications way less responsive that classical X11 applications running across gigabit ethernet.

And even on a fast network the wayland alternative of 'use RDP' is almost unusable.

replies(1): >>44373368 #
kllrnohj ◴[] No.44373368[source]
the approach used in this blog post requires rdp. It's not drawing using X, so there's no vector network transparency.
replies(3): >>44373529 #>>44373763 #>>44378880 #
1. uecker ◴[] No.44373763[source]
Clients can draw locally and composite remotely. I do not see the issue.
replies(1): >>44375558 #
2. kllrnohj ◴[] No.44375558[source]
draw locally composite remotely is literally Wayland's philosophy and is one of the biggest contentious issues for the pro-X11 crowd.
replies(1): >>44379205 #
3. uecker ◴[] No.44379205[source]
This what Wayland copied from modern X clients.