Wayland does not support screen savers: it does not have any provision that allows screen savers to even exist in any meaningful way. If you value screen savers, that’s kind of a problem.
Adding screen savers to Wayland is not simply a matter of “port the XScreenSaver daemon”, because under the Wayland model, screen blanking and locking should not be a third-party user-space app; much of the logic must be embedded into the display manager itself. This is a good thing! It is a better model than what we have under X11.
But that means that accomplishing that task means not just writing code, but engaging with whatever passes for a standards body or design committee in the Wayland world, and that is… how shall I put this… not something that I personally feel highly motivated to do.
Who even uses screensavers anymore? Just set the screen to turn off after a set amount of time.
a visible locking screen saver on idle workstations is a requirement in many places.
AFAIK screen locking is already possible and widely implemented; it’s just being handled by the display manager (? I think that that’s the right term). It’s just that you can’t install anything that provides a fancy animation, if I understand correctly.
Yes and my screen locks when the screen turns off, don’t need useless graphics bouncing around.
I’m pretty sure automatic locking is part of most Wayland implementations. Maybe the Sway/Hyprland style barebones tiling implementations don’t have it, but I don’t think it’s a problem for the desktop environments you’d use in a workplace with such requirements.
With the increasing popularity of OLED displays, screensavers might make a comeback. Although I still think OLED displays aren’t worth it.
It’s not gonna be better than turning the screen off.
Don’t they typically do minor anti-burn in changes during idle, basically having a built-in screensaver? Still, an additional one could be nice for peace of mind.
That’s what the display makers claim, in order to avoid too many customer complaints. In reality you’re still likely to get burn-in within a few years of monitor use, and when you ask for warranty support you’ll get denied claiming “you used the display wrong”.
Why? Burn-in hasn’t been an issue on my phone and that screen has been on for hours every day for the last three to four years.
Whatever Android does to protect against burn-in seems to work fine on modern OLED technology.
People don’t tend to keep phones for more than few years. On the other hand, I have LCD computer monitors that I still use over a decade later.
What really kills OLED displays is persistent static elements. These are common for desktop usage: persistent taskbar/dock, desktop wallpaper, window buttons, tiling, GUI elements and HUDs in gaming. All of these things significantly increase the chance of getting burn-in within a few years.
OLED fanatics suggest it’s all user fault, that people should just use a solid black background for their desktop wallpaper (ugly), have a auto-hiding taskbar (inconvenient) and limit time spent on programs/games (really). Basically rather than using the computer the way you want, you have to carefully handle it like an egg. An expensive egg at that, since OLED displays are still ridiculously overpriced (often costing more than equivalent TVs).
They try a lot of things, but they still burn in extremely quickly, much more so than any CRT ever did (which really never burned in in a consumer setting).
Oleds have built in hardware screen saver
jwz addressed this, actually, by responding, “Who hurt you?”