• Count Regal Inkwell@pawb.socialOP
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    On my end, like –

    I have about as many tech issues with Windows as with Linux – It comes with me enjoying tinkering as a hobby I think?

    BUT, and this is important, when shit breaks on Linux, there is always output on the terminal, or a log file, or something else you can check, and even when I don’t know what to do about it, a simple copypaste of the error on internet search usually gets me some answers.

    When shit breaks on Windows? HOLY FUCKING SHIT. It just sorta dies and leaves you in the dark with nothing to go on for troubleshooting. Windows wants to make computers into magic boxes that “just werk”, but it never really gets there, and instead what you get is something that breaks just as often, but is a lot more opaque.

    That BSOD with an emoticon lives rent-free in my head. Like who the fuck thought it was a good idea?

    • laurelraven@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      Also, even when you actually get an error message (which you probably had to dig through the awful mess that is the event viewer… Seriously, the only update they’ve made to it in the last twenty years was to split a bunch of things into a ton of individual logs that are more than painful to dig through), it’s cryptic (if it tells you anything at all) and pasting it into search gives you nothing relevant, and quoting it gives you nothing at all (even the part that’s obviously the generic part of the error), or if it does, it’s a couple hits with people asking for help and either getting no replies, unhelpful replies that misunderstand the issue, or tells them they’re asking in the wrong Microsoft support forum

      Like… Come on, Microsoft. You clearly coded this error in the operating system. Put at least one page in documents online with at least something useful about it…