3 ms·
> Especially since learning about Linux means reinstalling your OS many times until you finally learn how to keep it clean and rescue it from any situation. Su
by eru 3y ago
> Especially since learning about Linux means reinstalling your OS many times until you finally learn how to keep it clean and rescue it from any situation.
Surely, you are dramatizing a bit here. Or are you assuming that everyone shares the same need to fiddle with everything?
- dagw 3y agoAre you trying to actually learn Linux or just how to use Linux to get other work done. Learning how to use Linux to get work done doesn't require a 'need to fiddle' as you put it, but you're not going to really learn actual Linux (as in how the kernel and core operating system works and hangs together) without getting your hands dirty and breaking a lot of things along the way.
- eru 3y agoAgreed. Well, these days you can do use VMs to destructively 'learn Linux' without messing up your real system.
- Gordonjcp 3y agoYes, but do you actually need to know that? I know that, I've been using Linux since the whole thing fitted on four 1.44MB floppies. I don't *care* though, and if my machine is fatally screwed up I just bust out the latest Ubuntu LTS, flatten, and reinstall. I haven't got time to muck about with rescuing a broken system. I've got stuff to do.
- dagw 3y agoYes, but do you actually need to know that? Do you actually need to know JavaScript? Or C? Or Japanese? As I said, if Linux is just the OS you use to do something else, then no. If your job/hobby is to actually develop Linux or tools that tie very tightly to Linux and how Linux operates, then yes.
- Gordonjcp 3y agoOkay, but if your job is actually to develop Linux and Linux tools, you'd be better off with a sensible distro like Ubuntu. You're not productive if you're constantly having to fiddle about with broken tools.
- dj_mc_merlin 3y agoNo, just personal experience. I started learning Linux as a young teenager and have broken dozens of installations (breaking system python, deleting /usr/ via rsync, doing an incomplete system update, writing a love letter to my boot sector, etc. etc.) Eventually I have failed in so many ways that there are not a lot of ways I can fail now that I don't know how to rescue myself from. Also I've learned what not do to keep things saveable. > Or are you assuming that everyone shares the same need to fiddle with everything? Why else would you use Linux? This fiddling is literally necessary to learn it. Otherwise you have to ask somebody else for help, who has done the fiddling.
- eru 3y ago> Why else would you use Linux? Because you just want to get work done, or play your game or browse the web etc? Yes, learning Linux is fun (for the kind of people who find this fun). But we don't expect people who just want to get on with their lives to eg break Windows or MacOS a lot, either.
- dj_mc_merlin 3y agoI'm pretty close to this at work since about 1/3rd of my job is helping the non-Linux people deal with Linux. Programming is their 2nd language so to speak, and the use of Linux is incidental, it's just what's easiest to give them to keep everything in our company compatible. They require a person who knows Linux in order to keep working. It's not optional -- they just wouldn't be able to get everything running otherwise without it breaking every couple of days. The fixes they find without us usually end up masking the problem and causing a truly unfixable problem later. This is one of the biggest flaws of Linux IMO -- you have to dedicate yourself to learning it to be able to use it as a daily driver effectively. So: if you don't have to, and you don't know how, you shouldn't use Linux at all. There's no point, just use macOS. The macOS people eventually fix their problem on their own anyway since it's so standardized.
- eru 3y agoWhat are your people doing that they break stuff all the time? I found I had more trouble with macOS than with Linux. I mostly use ArchLinux, and I don't have those weird problems you are talking about.