I prefer software rendering, I don't use compositor, and I never will.
In software rendering, CPU only updates screen when changes are detected. And the change completes as fast as the computer can. So that's minimal latency + minimal resource consumed.
If you're on a compositor, the 3D accelerator in your computer has to update the screen 60 times every second. It's even worse when you have a higher refresh rate display. And compositors update the buffer as soon as the previous buffer is pushed after the v-sync signal, and then it just waits until the next signal comes in. So there comes the terrible input delay. As a result, it comsumes more power and has higher latency.
So in conclusion, fuck Wayland, and I'm going with xfce without compositor.
It't true that the ThinkPad display kind of sucks. Though I can upgrade to a 2K OLED panel for additional 80 USD. That makes the E14 30 bucks more expensive than the Neo.
I visited change.org to sign the petition for them, only to get spammed by far-right extremist propagandas supporting nazism like this: https://imgur.com/a/E6LMUcB
I regret giving my real name and e-mail address to that website now.
Having your own ideal and philosophy and not sheepishly following corporate and government propaganda (so called "trend") is what every other person should do.
I tried wayland multiple times before, but the lack of xsct equivalent and the awful input delay (compared to X11 window managers without compositor) made my experience very frustrating. Some might say "it's just a one or two frame delay", but for me that makes a night and day difference. Just an additonal frame delay gives me a feeling of driving a 70s American boat car with worn out tires.
"In his paper, Barss observed that in Papua New Guinea, where he was based, over a period of four years 2.5% of trauma admissions were for those injured by falling coconuts. None were fatal but he mentioned two anecdotal reports of deaths, one several years before. That figure of two deaths went on to be misquoted as 150 worldwide, based on the assumption that other places would have a similar rate of falling coconut deaths."
I don't think machines should rely on an opaque logic to assume and "correct errors" on user input. It's more accurate to "fail" than handling out an assumed output.
And also:
> they need to supply ones specifically engineered to be uncorrelated with the right figures.
I assume most people will understand this way (including me) when it's said to "input wrong figures".
In software rendering, CPU only updates screen when changes are detected. And the change completes as fast as the computer can. So that's minimal latency + minimal resource consumed.
If you're on a compositor, the 3D accelerator in your computer has to update the screen 60 times every second. It's even worse when you have a higher refresh rate display. And compositors update the buffer as soon as the previous buffer is pushed after the v-sync signal, and then it just waits until the next signal comes in. So there comes the terrible input delay. As a result, it comsumes more power and has higher latency.
So in conclusion, fuck Wayland, and I'm going with xfce without compositor.