Man, people really overstate the barrier to entry to the terminal. Windows troubleshooting is full of command line stuff as well.
It’s not the terminal, it’s the underlying issues. Having more GUI options to set certain things is nice, but the reality of it is that if an option isn’t customizable to the point of needing quick GUI access it should just never break, not be configurable or at least not need any manual configuration at any point. The reason nobody goes “oh, but Windows command line is so annoying” is that if you are digging in there something has gone very wrong or you’re trying to do something Windows doesn’t want you to do.
The big difference is that the OS not wanting you to do things you can do is a bug for people in this type of online community while for normies it’s a feature.
As a normie (at least in these circles), I think I agree with your last point. Windows being heavily restricted in its customizability is a feature. A bad feature, but a feature nonetheless.
You can reinstall a driver without ever touching the command line on windows.
Can you do that with Linux? Idk maybe on some distros but the default would just be to uninstall the package from terminal.
Pretending these are equivalent is not cool and it just drives new users away for not understanding things the community takes for granted. It takes effort to learn the terminal if even tech-savvy windows users may not even use the command line
Not what I’m saying. I’m saying that a) copy pasting into the terminal isn’t the horrifying breakdown of usability Linux advocates seem to believe it is, and b) there are more pressing issues about how often you need to troubleshoot something in the first place.
On both Linux and Windows it’s relatively rare to have to reinstall a driver in the first place because both are able to pick up your hardware, set themselves up and keep themselves updated with minimal user intervention.
The real problem isn’t whether fixing the exceptions to that involves typing. The real problem is how often there are exceptions to that. In Linux it’s way more likely that the natural process of setting something up or customizing something will require some fiddling, while Windows is more likely to make you install some bloatware or not give you much choice, but most likely will get things working for you the way it wants them to work.
That is very much a user-friendly approach, despite its annoyances. The problem isn’t that there is a command line interface, the problem is that it’s littered in the middle of doing relatively frequent, trivial things. On purpose, even.
The deliberate misrepresentation here is that the Windows registry supports importing keys from a text file, so most of the time you have to mess with it you just download a file and double click on it.
Is that super secure? Nope. But hey, anytime you need to do something on a Linux terminal you’re also copy/pasting random crap you found online, don’t pretend you’re not.
The ultimate point still stands. None of these matter to normies, it’s how often you need to tinker or troubleshoot to begin with. For most users the acceptable number is zero.
Man, people really overstate the barrier to entry to the terminal. Windows troubleshooting is full of command line stuff as well.
It’s not the terminal, it’s the underlying issues. Having more GUI options to set certain things is nice, but the reality of it is that if an option isn’t customizable to the point of needing quick GUI access it should just never break, not be configurable or at least not need any manual configuration at any point. The reason nobody goes “oh, but Windows command line is so annoying” is that if you are digging in there something has gone very wrong or you’re trying to do something Windows doesn’t want you to do.
The big difference is that the OS not wanting you to do things you can do is a bug for people in this type of online community while for normies it’s a feature.
As a normie (at least in these circles), I think I agree with your last point. Windows being heavily restricted in its customizability is a feature. A bad feature, but a feature nonetheless.
The linux terminal is really easy to get into & the UNIX file-system is just nicely organized
You can reinstall a driver without ever touching the command line on windows.
Can you do that with Linux? Idk maybe on some distros but the default would just be to uninstall the package from terminal.
Pretending these are equivalent is not cool and it just drives new users away for not understanding things the community takes for granted. It takes effort to learn the terminal if even tech-savvy windows users may not even use the command line
Not what I’m saying. I’m saying that a) copy pasting into the terminal isn’t the horrifying breakdown of usability Linux advocates seem to believe it is, and b) there are more pressing issues about how often you need to troubleshoot something in the first place.
On both Linux and Windows it’s relatively rare to have to reinstall a driver in the first place because both are able to pick up your hardware, set themselves up and keep themselves updated with minimal user intervention.
The real problem isn’t whether fixing the exceptions to that involves typing. The real problem is how often there are exceptions to that. In Linux it’s way more likely that the natural process of setting something up or customizing something will require some fiddling, while Windows is more likely to make you install some bloatware or not give you much choice, but most likely will get things working for you the way it wants them to work.
That is very much a user-friendly approach, despite its annoyances. The problem isn’t that there is a command line interface, the problem is that it’s littered in the middle of doing relatively frequent, trivial things. On purpose, even.
You know whats worse than doing things in windows command line or powershell? The registry
“Nooooo! I cant $sudo nano /etc/some.conf!!!”
Regedit -> HKEY_USERS/microsoft/windows/system/some_setting --> value=FUCK type=DWORD
This is a common meme but essentially is never needed
The deliberate misrepresentation here is that the Windows registry supports importing keys from a text file, so most of the time you have to mess with it you just download a file and double click on it.
Is that super secure? Nope. But hey, anytime you need to do something on a Linux terminal you’re also copy/pasting random crap you found online, don’t pretend you’re not.
The ultimate point still stands. None of these matter to normies, it’s how often you need to tinker or troubleshoot to begin with. For most users the acceptable number is zero.
That’s because you are sending your Fucks to the wrong key. You are missing the /feedback folder under system