Let the apologists have a field day in the comments.

  • renzev@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    12 hours ago

    This is such a stupid take. Gui obscures the thing that you want to do behind endless buttons and menus and some bullshit that some self-proclaimed “user experience engineer” thought would be “intuitive”. With cli it’s like you’re talking directly to the computer. Want to stop the networking service? service networking stop. Couldn’t be simpler!

    Also fun fact, Linux has a “wireless devices” tool, command line one and it uses device ID to apply it and the fucking ID changes every time for the device so you can’t make a permanent setting.

    Are you talking about rfkill? Strange, for me the ID’s don’t change. But even if they do for you, what’s stopping you from getting the ID just by grepping for the device name? Something like rfkill list | grep YOUR_DEVICE_NAME | cut -d ':' -f 1 | xargs rfkill block.

    • RejZoR@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 hours ago

      Calls it stupid take, proceeds to give me most absurd noodle of a commandline for something that could simply be a Enable/Disable button on a device list panel that every idiot with no prior knowledge of Linux, CLI or memorized command could do it. I think proved my point once again.

      • renzev@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        3 hours ago

        It would take you less time to put together that one-liner than to find the correct button in an unfamiliar gui. How exactly does that prove your point?