[compiler-devel]

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.

[sho_hn]

This is nonsensical myth-making. Despite the clickbait title, the APIs called in those code samples are very basic and not some forgotten wizardry.

[compiler-devel]

What part is nonsensical? Because Wayland is basically a fulfillment of jwz's CADT.

[nullc]

> 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.

[kllrnohj]

the approach used in this blog post requires rdp. It's not drawing using X, so there's no vector network transparency.