At the end there's a little jab towards Wayland:
Today, the Wayland enthusiasts like to talk about how they are modernizing the Linux graphics stack. But Linux is a Unix, and in Unix, everything is meant to be a file. So any Wayland evangelists out there, tell us: where in the file system can I find the files describing a window on the screen under the Wayland protocol? What file holds the coordinates of the window, its place in the Z-order, its colour depth, its contents?
As far as I'm aware nobody has even considered extending the file metaphor to the graphics stack, and it sounds a bit ridiculous to me.
It also reminds me of this talk that suggests maybe trying to express everything as a file might not be the best idea...
Its all about how an application goes from "I would like to display X on a screen" to how X actually gets displayed. Wayland is effectively a language (technically a protocol) that graphical applications can speak to describe how they would like to be drawn. It's then up to a different program more deeply embedded in your OS to listen to and act on those instructions (this program is called a Wayland compositor). There's a lot more to it (handling keyboard input monitor settings, etc), but that's the general idea.
Wayland is a (relatively) new way of thinking about this process, that tries to take into account the wide variety of input and output devices that exist today, and also tries to mitigate some of the security risks that were inherent to previous approaches (before Wayland, it was very easy for one application to "look at" what was being displayed in a completely different app, or even to listen to what keys were being typed even when the app isn't focussed).
Thing is, change is hard, doubly so in the consensus driven world of Linux/FOSS. So, until the last couple of years or so, adoption of Wayland was quite slow. Now we're at the point where most things work at least as well in Wayland, but there's still odd bits of software that either haven't been ported, or that still rely on some features that don't exist in Wayland, often because of the aforementioned security risks.