this post was submitted on 07 Mar 2024
8 points (100.0% liked)

linuxmemes

21180 readers
805 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    8
    That's LTT in the bottom (lemmy.dbzer0.com)
    submitted 8 months ago by 0x4E4F@lemmy.dbzer0.com to c/linuxmemes@lemmy.world
    49 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] DingoBilly@lemmy.world 0 points 8 months ago (1 children)

    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 0 points 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!)