←back to thread

Ancient X11 scaling technology

(flak.tedunangst.com)
283 points todsacerdoti | 2 comments | | HN request time: 0.001s | 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 #
sho_hn ◴[] No.44371381[source]
This is nonsensical myth-making. Despite the clickbait title, the APIs called in those code samples are very basic and not some forgotten wizardry.
replies(1): >>44371425 #
1. compiler-devel ◴[] No.44371425[source]
What part is nonsensical? Because Wayland is basically a fulfillment of jwz's CADT.
replies(1): >>44371461 #
2. sho_hn ◴[] No.44371461[source]
The part where we got Wayland because we lost a magic caste of rockstar engineers who could call XRRGetOutputInfo/XRRGetCrtcInfo.