Comments by "eDoc2020" (@eDoc2020) on "The Wayland Linux Screensaver Dilemma" video.

@BrodieRobertson Since 3.8 the Linux kernel itself has dropped support for the 386. Only 486 and higher are supported these days. As for Debian, recent versions need a 686.
3
 @keit99 That's why screensavers are harmful, they just add more burn-in.
2
@keit99 How is that possibly better? Whenever a pixel is on it is getting burned. If your screensaver displayed the exact opposite of your normal desktop it would even out the burn-in but I don't see how burning more pixels helps at all.
2
I don't remember how it worked in earlier versions of Windows but at least in XP with Fast User Switching enabled this is not the case. Before starting the screensaver Windows opens a new desktop and on my particular setup the display obviously loses sync whenever this happens.
1
Windows (at least XP and newer) actually handle screen savers in a better way, they're (mostly) just regular GUI applications. When the timeout is reached the OS opens a new desktop object and the screensaver is launched with the '/S' option. Once the screen saver is dismissed the login UI is launched or it switches back to the original desktop with all the windows. I see no reason why a compositor which already has a screen locker also couldn't launch an external executable and display this over the login screen. After all they already have the ability to display the output of external applications.
1