I swear it feels like for a lot of the things I do on Linux there's a GUI app for it, but then if I wanna do something as basic as adjust my fan speed I gotta use the freaking terminal.
Like it's always at the worst possible time.
Edit: I’ve installed a distro on my gaming PC that I really liked, used it on my laptop. Sensors and fans were fully supported. Did not work at all on my PC so I told it to fuck off. It’s just too much of a pain to set up.
I’ve noticed over the years a LOT of Linux users do no have their system sensors / CPUs setup properly. Mostly missing fan information, missing / incorrect sensors and most importantly improper AMD CPU PSTATE and governors. For example, the past few years I’ve had to ensure I had correct kernel drivers and boot kernels parameters for my AMD 5950x to properly use the correct governor and idle at 500mhz and for correct sensor information and control for my viii dark hero MB.
There's coreCTRL for AMD and apparently nvidia-setting for Nvidia?
AMD GPUs got more tools due to them being open source, while Nvidia's isn't and you are beholden to Nvidia bothering to implement support, which they often don't.
Also, idk if I would call fan curves that basic, haha. For the vast majority the default curve is sufficient.
Not sure if you're being sarcastic or serious. I've been using computers for decades and not once adjusted fan speeds, so that function doesn't seem very basic to me.
I think it's a matter of habit, really. After using a somewhat minimal Arch install with a WM instead of DE, I get frustrated when an app doesn't have a CLI version, using GUI now feels less comfy almost
While this is not a serious post I'm going to take it seriously, so here are some of the reasons:
Nobody can easily remember the precise file name and if you don't get the first letters right you're screwed(did I mention capital letters matter?)
Wtf is --vo=tct? No sane person is remembering all of that (same goes for the rest 10000 parameters and options)
Again, waaayyy too many parameters, who remembers their playlist name? There is no autocomplete here, you're on your sad own in your sad little room with your sad little feelings, because there's no one there to tell you the song's precise name, because computers are assholes and don't hate you.
So why GUIs? Because they make computers seem like friendly fellas which actually care about you and give you options, tell you the available functions(without deciphering a 50 pages manual if done well)
If you take it seriously, then at least your complaints should be reasonable, not meme-worthy.
Autocomplete is a standard feature in CLI nowadays, so no need to remember everything.
And parameters usually have names chosen to make the most sense and to be memorable (e.g. vo = video output).
You' can try installing yt-dlp. That one is still actively maintained. YouTube also actively trying to broke it, so the one available in debian repo might be out of date.
Exactly! Takes so much of the pain away. And you know what would be really useful? If those scripts were accessible easily through simple buttons or sliders on which you could click, or something like along those lines.
For basic functionality I agree, but I don't think any dev would put the time and effort to implement buttons (much less pipe into another totally different software) for my extremely specific use cases. In the command line I'm presented with a toolset where I can do so myself.
IMO it's not even a Windows vs GNU/Linux debate (although yeah, maybe more of the users of the latter would be familiar with the CLI), it's about using the right tool for the job. Image or video editing? Good luck even starting to do anything without a mouse. Installing something? Yup, even on Windows I'd prefer doing scoop install foobar2000 instead of opening a store app or a website.
I use CLI daily for git and nano, but it's far from necessary for the average user. I'm not sure why some people want to propagate the idea that Linux is hard when it's just a little different than what most people are used to.
Here's a novel idea, read what you're about to paste and try to understand what it does at least on high level. You can man each command to check what it does and whether the parameters provided make sense.
My brother used to constantly try to tell me this. I don't know how many times I had to compare number of keystrokes to number of clicks before he finally admitted GUI programs are easier even if you already know exactly what you're doing.
There is also that obscure forum post from 2012 that refers to a post from 2004, from someone who gives some cryptic advise with commands not even in the manual that are outdated from 5 major releases ago but somehow still work. Except for one command tgat you then google and find a forum post from 2016 that it has been renamed, but the functionality stayed the same.
Anyways you put it all together and your problem somehow got solved, but you seemed to have created a black magic incantation because now a three headed demon has appeared and eaten your neighbour alive.
powershell is pretty great for windows tbh. I use arch and i love python and shell scripts but on windows powershell gets shit done. PS is great for vmware too. There's a lot of 'microsoft bad' that i agree with but powershell is not one of them.
I think the only reason Windows users are afraid of terminals is that they're not used to them. They're not that bad. Most terminal programs have a -(-)help command that shows you what you can do as well, in case you get stuck.
Powershell is pretty interesting but I haven't learnt much of it and it's hard to discover commands, arguments and fields within results. All the commands have really similar generic names and cryptic mnemonics. And an annoying amount of them are text based and don't actually interoperate with the ecosystem.
I'm more used to slinging around text with bash and the basic Linux utilities so I'm not inclined to learn more than I have to on the Windows side.
Let me tell you a story of checking a signature and unzipping an exercise file for uni every week on my linux distro that was named 01_ML-exercise_Bayesian-sep.zip.gpg followed by 02-Ml-exercise-FisherLinearDiscriminant.zip.gpg
Hello noobs! I'll let you in on a secret. Pros use command line interface (CLI) both on Linux and on Windows for a lot of tasks. You know why? Because it's easier. Be like the pros, choose the easy path, use CLI!
Depending on the time availability of that pro. Sometimes I have the time to tailor to the needy's sensibilities. Other times all I can do spit out what I have whether it's GUI or CLI, take it or leave it.
Same here. I didn't imply that we only use CLI. Simply that for a lot of tasks CLIs are easier than GUIs. And therefore the CLI aversion is something to shed. The reverse is also true for other tasks too. Windows has historically put many tasks easier achieved via CLI behind a GUI. You wouldn't see me dead playing videos via CLI. I'd launch Plex, search and play instead. 🥲
Forget gui, I just want to git clone something and then type the name of the application I cloned into a command and have it run. None of this infinite searching for dependencies that didn't get installed with the initial run dependency installer.
I use Arch btw, and we don't have this kind of problems usually. Everything is in the repo, all the dependancies are accounted for. Or if not, they are in the repo.
I use Arch btw.
I mean, it obviously depends on what you're doing, but usually it's easier to find the right command than the right GUI, because implementing a CLI is a magnitude less work than implementing a GUI...
Shells offer a significantly faster and more powerful way of running programs when you know how to use them. The "helpful" Windows user is kneecapping the noob by offering a shiny but limiting GUI. Once you get a grasp of basic command line tools, you'll wonder why you bothered with pointing and clicking stuff.
I feel like the shell becomes much more complicated when you want to use configs. Or anything other than basic commands. At that point it becomes a pain in the ass, or tedious.
Other than that I agree. Also, GUI file managers are still superior. Sue me.
I still don't get why people like vim. Like sure, I use it to edit config files and stuff that needs sudo permissions, but in all honesty, if I could use any gui for that, like Kate, I wouldn't see any reason for using vim. Why do I need to relearn years how to Ctrl+ f or exiting the editor? buT iT'S FaStEr. Really? You spend how long looking up guides and cheat sheets on how to use it and it's faster? I mean sure, use what you are comfortable with but can you really say it's that much faster than just any text editor out there?
And everything can be easily automated on shells, i love how i can setup a task on my pc and once finished send a request over wifi to my phone and use termux to generate a notification