Basically what he was saying was that one installs stuff on UNIX, it works, it ain't broke, don't try to fix it |
I'm sure plenty of things work on installation in Linux, but compared to Windows, more things just.. work.
The UNIX way of doing things basically means having human readable/editable config files. |
I've gone through many config files and altered them on Windows. Haven't really on Linux, so I can't tell you if its a better experience, but it never gave me issues on Windows.
For example, I recently wanted to remove the windows installation that came with my new laptop, so I could run it in a VM. I needed to get the product key, and I eventually discovered a way to do it using a wmic command in the shell, but then discovered that wmic had been deprecated, so I had to use a power-shell cmdlet instead. |
I'm not 100% sure on what you were trying to accomplish, but I don't think you needed a shell for it.
I've used CMD/Powershell a lot, but I've rarely found that its the
only. The one example I had where it was the only way to accomplish something was when I accidently screwed up my Microsoft Store! And the only way to get it back was some command line stuff.
But you can see how these are things that only happen because we tend to be niche users. And I'm not against using the command line or whatever, but Linux is command line dependent!
I wonder if your opinions are colored by your (seemingly) lack of experience with Linux? |
Well.. it could be. When I was an early teen, I was influenced into getting Ubuntu. I got it and wasn't very impressed I suppose.
Many things you can just do on Windows require command line in Linux and can go wrong. For example... When I was programming my Raspberry Pi Pico with a bluetooth module, I used Windows after attempting to do it on Linux first...
Windows Microsoft Store had a simple app for testing bluetooth connections, seeing if data is coming through, etc.. Linux had two options, command line or an application. I of course went with the application.
Tried for hours, nothing could get that application to work and detect anything. Move over to Windows, not a single issue, data going through no problem.
I didn't even get to try the command line because it was NOT a nice process to setup.
So, I programmed the pico, tested the bluetooth module, etc.. all on Windows (Thonny was amazingly simple!), easier than Linux.
Windows is just a more reliable OS in terms of applications and a trusty OS.
weren't happy having to use the shell to do some things, because you are used to the windows way of doing things? |
Some things just shouldn't require the shell, either because they should be simple GUI applications or the shell way is too long and complicated.
Can you give examples of the things you need to mess with?
For a normal user Linux is just the same as Windows, one doesn't really have to do anything, IMO. |
What's a "normal user"? Someone who doesn't program? Someone who only uses Microsoft Word and browses the internet? Why would they go to Linux anyway when the more supported OS is Windows?
I'd argue no matter who you are, you'll end up using the terminal at some point if you're on Linux, you simply won't be able to avoid it sometimes.
On Windows, you might never even know that Powershell/CMD even existed.