• PeriodicallyPedantic@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    I mean, you don’t HAVE to do any of that stuff in Windows, it’s just helps a bit.

    I’m sure there are plenty of windows horror stories. But almost every Windows computer I’ve had in the last decade, both custom and OEM, has worked pretty well out of the box. And almost every Ubuntu computer I’ve had over the last decade has had problems that weren’t trivial to fix.

    I like Linux, but when people compare these problems like they’re the same just are missing the point.

    • BargsimBoyz@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      8 months ago

      Yep exactly this. The user friendliness and likeliness it just works is much higher for Windows.

      If it doesn’t work for Linux I’ve found it also will generally take much longer to figure out and fix.

      • Macros@feddit.de
        link
        fedilink
        arrow-up
        0
        ·
        8 months ago

        Sure because Error Code 0x8007057 tells you immediately how to solve the problem.

        Linux error messages like error: kex_exchange_identification: client sent invalid protocol identifier "GET /robots.txt HTTP/1.1" are completely arcane tough.

        I support both systems. And Linux support is so much easier. Mostly in runs out of the box. If it runs I continues to do so and If you have an error you get a specific message like above.

        With such a message you either:

        • See right away how to solve the problem
        • Search it online and get a specific solution for exactly you problem
        • Or you can ask Experts for a solution for your specific problem.

        With Windows: No systems runs out of the box, I always have to install additional software (7zip, sane browser, …) and also for anybody remotely privacy concerned have to adjust many settings (for which tools exist thankfully)

        If an error occurs under Windows and I get a code like above:

        • I can sometimes guess by my experience what the reason is and solve it.
        • If not I search the error code and circumstances which lead to it online, then apply the 20 solutions presented one by one in hope one works
        • Ask experts which ask me to run a bunch of diagnostic utilities because the error message does not tell you anything. (Yes by now I can also guess which utility could provide relevant information, but not because Windows told me)
        • In a noticeable amount of cases the solution is: We can not determine the reason for the error, please reset everything (First a restart, then run this cleanup tool and if this doesn’t help just reinstall!)