• wizardbeard@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    5 days ago

    The overwhelming majority of the nags can be disabled permanently with the right configuration, in a way that isn’t trampled on by updates.

    The main issue is that because Microsoft doesn’t have anywhere close to sane defaults, many people believe it isn’t possible to configure sanely.


    It also doesn’t help that Microsoft has crossed the threshold where there’s too many people using it who think they know what they’re doing well enough to speak authoritatively about its “issues” when they don’t. Lots of Dunning Kreuger going on.

    And that MS torched a ton of their learning resources for desktop config and admin stuff when they went all in on the cloud and are only now recreating some of them.

    And people try to use it outside of the intended use case then get frustrated that things get weird. It’s configired to be a daily driver or at least powered on once a week for updates, of course if you only use it every few months things are going to suck. You’d get laughed at if you were using a hammer to drive screws, but Windows is supposed to just work anyway with no rough edges?

    • supamanc@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 days ago

      An operating system isn’t a car or a machine that needs to maintain running hours for optimal performance. If I have an operating system that I only need for one specific function, and only use it for that function, once or twice a month, there is no reason that that operating system should fail to do the one thing I need it to do every time I turn it on.