• rbos@lemmy.ca
    link
    fedilink
    English
    arrow-up
    9
    ·
    3 days ago

    That does seem like a dumb thing to be complaining about. Human UI interactions should be given pretty high priority, and pinning the CPU to max clock speed sounds like a sensible optimization.

    I feel like there’s some other issue here the author isn’t touching on, maybe.

    • MartianSands@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      32
      ·
      3 days ago

      Pinning the CPU clock uses more power, and generates more heat. If it were “sensible” to do so, then the CPUs for consumer devices wouldn’t have variable clock speeds to begin with.

      Since people do care about devices getting hot in their hands, and draining batteries, this is a stupid and lazy fix for a problem of their own making and they’re expecting users to put up with the problems it causes in exchange for Microsoft being able to treat their operating system the same way social media companies treat their feeds

      • Kogasa@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 hours ago

        It’s not permanently running at max frequency. It’s raising it as needed, which is exactly the point of having variable frequency. Generally the user can provide guidelines for the cpu governor to control or guide its behavior according to power, performance, and thermal constraints. I think Windows has power plan modes for this.

      • fuckwit_mcbumcrumble@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        2 days ago

        As the article points out, both Linux and Mac OS do the exact same thing. And I don’t see people giving them shit for it. Is it stupid and lazy when they do it?