X11 reference books dating from 1989 are still considered current and up to date

>X11 reference books dating from 1989 are still considered current and up to date

Is there anything else in technology that has this kind of staying power?

Attached: g63ayo12k4l21.jpg (3336x2336, 789.39K)

what are criticisms of X?
how does wayland address those criticisms?
what are criticisms of wayland?
how would you make your window system work?

Attached: 1640955356747.png (240x240, 48.91K)

>Is there anything else in technology that has this kind of staying power?
Win32

Imagine having to read an entire book about a fucking window protocol

Hardly.
Current version is X11R7 since 2005, and even then the X11 standard it self is barely anything as there is so much shit bolted on top of X11 that just the reference wont really get you far.

>drop the server-client model
wayland is doa because they didn't have the balls to do this

unimaginably based
it just werks
meanwhile trannyland has been in development for a decade and is still completely unusable

X is the functional equivalent of a temporary government program. Doesn't work, somehow becomes immortal.

The client/server model is why X and now Wayland will never have the latency response that Windows does.

even if the latency was better, they should still drop it

It made sense when X was originally designed so you could have graphical dumb terminals, but since the late 90s, the vast VAST majority of X's usage is completely local on systems, yet it has remote usage as its primary design philosophy.
I really wish Wayland took a MS approach, local first remote second in priority. Ironically, modern RDP does a better job at remote desktop then X or Wayland does.

>>X11 reference books dating from 1989 are still considered current and up to date
Holy based, gayland-trannies will seethe

Attached: Pepe Cheers.jpg (1002x1004, 93.52K)

Which programs even use motif?

lucid-emacs

The fact that redhat weenies think this is a criticism is everything wrong with software today. Not having to "refresh" your knowledge every five years is a benefit, not an issue to be resolved.

Lotus notes
Installshield
Native Instruments LAVA Suite

>windows doesn't use client/server for gui
What the fuck did they mean by this? Client/server over IPC is still client/server.
Wayland uses shared memory buffers, which is an optimization made possible due to local-first design.

Emacs

I wish all programs were like this. Resilience. With beautifully bound documentation by O'Relily Media.

>staying power
>is being actively killed off and replaced

In that the base protocol is the same, yes. These references won't include any of the extensions that everything uses now.
Similarly an HTML 1.0 reference is still usable today apart from a couple tags like marquee and blink which modern browsers ignore since they're annoying.