116
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Jul 2024
116 points (99.2% liked)
Asklemmy
43950 readers
906 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
Thanks, makes sense. But why don't monitors have an "emergency" protocol to let the LEDs rest a while if we can know what's the max stress that they can handle?
So instead of burning out, I'd get a pop up saying that I should do something, or it lowers the brightness in that area or smth.
I have five guesses:
(1) That would require more diagnostics than an LED on a monitor is able to provide at a reasonable cost, (2) if you're leaving the monitor on in a situation where burn-in is likely, you're probably not at the monitor when it matters, (3) monitors are a mission-critical piece of hardware, meaning that them turning themselves off (or even just turning off certain pixels) randomly is not a great idea, (4) it's probably the OS's job to decide when to turn off the monitor, as the OS has the context to know what's important and what isn't, and how long it's been since you've interacted with the device, and (5) it's in the monitor manufacturer's best interest for your monitor to get burn-in so that you have to replace it more often.
The actual answer is probably a combination of multiple things, but that's my guess.
Honestly, setting a screen timeout (or even a screen saver!) is the solution to this problem. So the problem was more or less solved in the early 80s.
very good points, thanks.