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 networkingservice? 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.
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.
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?
BS, I looked online for hours and waited for replies on reddit and no one gave me this line. So, no, I’d in fact do it via GUI in minutes where it took me hours for some backwards config that doesn’t look anything like this that made me do what I wanted. With extra steps to copy that stupid file into system folder, of course via stupid Terminal because I couldn’t do it through file manager in any way. The level of stupid Linux has to configure trivial things is just astounding.
And what’s weird is how Linux purists always whine about it. Like, I don’t care, keep using your stupid Terminal, just give me damn GUI for this basic shit. I don’t want to waste time and memorize idiotic noodles of commands to do trivial shit. No one is taking away any of the stupidity you love, just give ME the choice. Instead the only choice is use of stupid CLI. Ugh.
Also it’s not “unfamiliar” GUI. It’s called practical deduction. If I need to do this and this I already know I might need to look under this and that category in settings or just type rough related words in search and it would show me the setting. If whoever makes GUI isn’t a complete moron, it would be easy to find. Good luck with any of that with CLI where you need to input exact command from start. Your logic just makes no sense.
I don’t want to waste time and memorize idiotic noodles of commands to do trivial shit.
Also it’s not “unfamiliar” GUI. It’s called practical deduction.
Can you not see how the two arguments you’re making are completely contradictory and self-defeating? Nobody is asking you to memorize “noodles of commands”. What, do you think we all have little books full of shell one-liners for every task imaginable? You just have to know a few basics: The pipe redirects data, cut splits lines of text, xargs builds up arguments raw text, etc. Put them together in whatever way you wish to accomplish the task at hand. It’s – exactly as you say – practical deduction.
You’re really not making the case in your favor with this argument. So, now I have to memorize even more dumb commands. What in the fuck? You really have no clue about GUI, do you? Youbdon’t have to memorize ANYTHING, just have general idea in which category of settings to go. And that’s it.
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!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 likerfkill list | grep YOUR_DEVICE_NAME | cut -d ':' -f 1 | xargs rfkill block.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.
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?
BS, I looked online for hours and waited for replies on reddit and no one gave me this line. So, no, I’d in fact do it via GUI in minutes where it took me hours for some backwards config that doesn’t look anything like this that made me do what I wanted. With extra steps to copy that stupid file into system folder, of course via stupid Terminal because I couldn’t do it through file manager in any way. The level of stupid Linux has to configure trivial things is just astounding.
And what’s weird is how Linux purists always whine about it. Like, I don’t care, keep using your stupid Terminal, just give me damn GUI for this basic shit. I don’t want to waste time and memorize idiotic noodles of commands to do trivial shit. No one is taking away any of the stupidity you love, just give ME the choice. Instead the only choice is use of stupid CLI. Ugh.
Also it’s not “unfamiliar” GUI. It’s called practical deduction. If I need to do this and this I already know I might need to look under this and that category in settings or just type rough related words in search and it would show me the setting. If whoever makes GUI isn’t a complete moron, it would be easy to find. Good luck with any of that with CLI where you need to input exact command from start. Your logic just makes no sense.
Can you not see how the two arguments you’re making are completely contradictory and self-defeating? Nobody is asking you to memorize “noodles of commands”. What, do you think we all have little books full of shell one-liners for every task imaginable? You just have to know a few basics: The pipe redirects data,
cutsplits lines of text,xargsbuilds up arguments raw text, etc. Put them together in whatever way you wish to accomplish the task at hand. It’s – exactly as you say – practical deduction.You’re really not making the case in your favor with this argument. So, now I have to memorize even more dumb commands. What in the fuck? You really have no clue about GUI, do you? Youbdon’t have to memorize ANYTHING, just have general idea in which category of settings to go. And that’s it.