• MystikIncarnate@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 days ago

    IMO, this is a demonstration of the problem. You’re blaming the poster/their equipment. Rather than any real solution to the problem the defacto answer is “well, it works for me so what’s wrong with you?”

    I’ve never heard this kind of toxicity from other communities (like the apple/Windows crowds). Often you’ll get useful answers indicating what to check or pointing to another resource. There’s always the chance that the hardware is busted, but let’s face it, in the modern era, that’s far less likely to happen now than it was even 10 years ago.

    Immediately blaming the user for their issue isn’t going to solve the problem, nor does it endear any average user to the Linux community or the Linux OS. This attitude is not going to help adoption even if the posters concerns are invalidated by newer/better drivers/software, and all they need to do is update, and/or try again.

    This kind of statement actively harms Linux adoption.

    • _carmin@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 days ago

      Sorry I meant to say I dont even remember how many years ago I saw anyone with Bluetooth problems. Look how you conveniently ignore the fact Kde and Gome dont use the terminal contrary to what you had stated. Your shit is all fucked up.

      • MystikIncarnate@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        Bitch please.

        Just try to install a program that isn’t in the repo without dropping to the CLI.

        I dare you, I double dare you.