Congratulations, you've managed to "compress" PDF files by rasterizing every page to JPEG, while destroying all the vector and textual information in it.
The resulting PDF is nothing like the input -- it's just a bunch of blurry JPEG images wrapped in a PDF format.
You can't search or copy the text, and trying to print it will just make a blurry mess of the text.
Because astigmatism or other refractive vision errors.
Think about how astigmatism affects vision, then take into account the effect on pupil size based on incoming brightness, and how this affects the depth of field, and you may understand why.
He is referring to input lag: the delay from input to visible change on the monitor. The double buffering and compositor step added by Wayland adds some delay.
You may not personally notice it, or be used to it, but it's always there. Some people are more bothered by input lag than others, and there are so many compounding factors today that make it worse than ever. It's not only the double buffering in graphics subsystems like Wayland. Monitors are also often adding a frame or two delay to bump up their pixel "response times" and reduce ghosting by looking at future frames.
I swear, using Wayland or MacOS or Windows 10 on the fastest hardware today still feels slower and laggier than 10 year old hardware running plain X11 or Windows 7 (with the compositor turned off).
Given the choice between tearing and input lag, I'll take tearing any day.
Linearized (a.k.a. web optimized) PDF files only help for displaying the first page quickly. The rest of the file is still in pretty much random access order.
Congratulations, you've managed to "compress" PDF files by rasterizing every page to JPEG, while destroying all the vector and textual information in it.
The resulting PDF is nothing like the input -- it's just a bunch of blurry JPEG images wrapped in a PDF format.
You can't search or copy the text, and trying to print it will just make a blurry mess of the text.