Check out my open source game engine! https://strayphotons.net/ https://git.sw0.com/frustra/strayphotons

I have been developing this engine on and off for over 10 years, and still have big plans.

  • 1 Post
  • 1.41K Comments
Joined 3 years ago
Aquileo | cake
Cake day: July 9th, 2023

Aquileo | help-circle










  • and if a display driver can’t be written in 1 line that doesn’t make the thousands of lines unmaintainable slop

    That’s not what I’m saying.

    I’m saying if there’s 1000x more lines of code than necessary, it’s unmaintainable slop. I could understand 2x or even 10x the lines of code just being a difference in architecture, but even 100x is getting crazy.

    I think only EnterpriseFizzBuzz surpasses the 1000x inefficiency metric that this meme is implying.




  • Look, I was trying to understand your issue, since I’m a developer and am curious about this kind of thing. I stated my assumptions to try and make my initial point of view clear and give you the opportunity to provide more information if my assumptions were wrong.

    From what you’ve stated I don’t believe your problem is related to DCC/CI at all, and is likely something else with sleep states failing. Whatever is failing on your system is extremely unusual and is not something that I would expect a “Grandma” to ever encounter. If anything, older hardware should be better supported.


  • I’ve not experienced any of this across many different linux systems… The default screensaver and lock screen work perfectly fine in KDE Plasma, and my monitors turn off when they should. I’ve even had no issues with HDR and variable refresh rates. (And the DCC/CI brightness controls for my TV work out of the box unlike windows).

    I’m sorry you haven’t had the same experience. It almost seems like there could be something broken with your hardware if your monitor is continuing to detect a signal after things are asleep.