For many it is simply frustrating because it is not Windows. Just think about how many people have a hard time already to get the most simple things done on Windows. Can you imagine those people to switch to another platform? Those people who cannot find their banking app anymore when something moved the icon on the desktop to another position?
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I have the opposite problem, I find windows or other OSes to be so full of stuff, (feature ritch) but lack low-level "i just wanna poke at this briefly" capability, the (possable) reason why most Raspberry Pis run Linux is because its so easy to address linking this thing to that one. Ive used linux so long that ive become used to
-
its tree mounting scheme
/foo/mountpointFolder
on/dev/disk/by-label/C drive
where symlink resolves to/dev/sdc
rather than a linear oneC:/
on*internal concept*
rather than a(more...)
in Linux's model, the mount system defines the source to be any file with the specified filesystem data in it. The Mountpoint (target) can be any (usually empty for safety) folder. -
symlinks on windows are discouraged so heavily. I looked it up and still don't know how to make them. on Linux, its easy,
it makes a thing that acts almost just like the thing its referencing. in a GUI file manager, you can navigate into a symlink where reference ishow to
doln -s filePath pathToNewLink
or in a GUI file manager, right click find "new" submenu click item with a link as the icon and a name likw "link",.
and not get anywhere to great confusion. on windows this odd support for but insistence on not using a "basic feature" is mind boggling. -
linux with things like Fuse (Filesystem in userspace) allows literally anything and everything to be a filesystem, more non real folders to make a new user's head spin.
(more...)
virtual filesystems that have files and folders that are actually this OS construct that's stored in RAM or a view of folders not representational of how their literally on disk. (Fuse filesystem reading and proxying your multimedia organizing it into folders by artists)
all of these things are about having flexible references and easy access to computer resources, On windows I find myself wondering why I cant open this text based file real quick without needing to go online and get some software that will specifically handle it.
there are very few APIs you can touch in an ELF program (think EXE for Linux) that you cant with a Bash script and relevant programs. I get on windows and all the EXEs have have even more cryptic names than linux and no help menu or offical e-book and are at the mercy of the internee's answer (whats lsass.exe). it all makes me go, screw it! if I want to access the Raw C drive to do a non off the shelf task, I need to make it myself which means learning their programming framework.
My first experience with linux was Ubuntu. Sue me, it was listed under most "most user friendly distro" listicles when I wasn't smart enough to realize those were mostly marketing.
It worked fine for my purposes, though it took getting used to, but it would wake itself up from sleep after a few minutes. I would have to shut it off at night so that I wouldn't wake up in a panic as an eerie light emanated through the room from my closed laptop. I did my best searching for the problem, but could never find a solution that worked; in retrospect, I probably just didn't have the language to adequately describe the problem.
Nothing about the GUI was well-documented to the degree that CLI apps were. If I needed to make any changes, there would be like one grainy video on youtube that showed what apps to open and buttons to click and failed to solve my problem, but a dozen Stack Exchange articles telling me exactly what to do via the terminal.
I remember going off on some friends online when they tried to convince me Linux and the terminal were superior. I ranted about how this stupid sleep issue was indicative of larger, more annoying problems that drove potential users away. I raged about how hostile to users this esoteric nerds-only UX is. I cried about Windows could be better for everyone if the most computer-adept people would stop jumping ship for mediocre OSes.
I met another friend who used Arch (btw) within a year from that hissy fit, and she fixed my laptop within minutes. Using a CLI app nonetheless. I grumbled angrily to myself.
A few years later and everyone's home all the time for some reason, and I get the wild idea that I'm going to be a(n ethical) hacker for whatever reason. I then proceeded to install Kali on a VM and the rest is history.
The point being that some people labor under the misguided belief that technology should conform to the users, and because we were mostly raised on Windows or Mac, we develop the misconception that those interfaces are "intuitive" (solely because we learned them during the best time in our life to pick up new skills). Then you try to move to linux for whatever reason and everything works differently and the process is jarring and noticeably requires the user conforming to the technology--i.e. changing bad habits learned from other OSes to fit the new one. The lucky few of us go on to learn many other OSes and start to see beyond the specifics to the abstract ideas similar to all of them, then it doesn't matter if you have to work with iOS or TempleOS, you understand the basics of how it all fits together.
TL;DR Category theorists must be the least frustrated people alive
The Linux community doesn't understand what "just works" really means.
Whether windows or mac, I plug my machine to the docking station, and it just works.
With Linux, every day a different problem. Out of the blue, screens just stop working. Resolutions change. Every restart different behavior. Zero consistency.
I'm not 17 anymore... I don't have the time to keep tweaking. I need to be productive.
So what do I do? I SSH to a Linux machine whose desktop environment I don't wanna see, and code remotely. Most productive setting.
You asked. Here's the answer.
you hit the nail on the head. When I first got into linux I was watching some youtube video about I think the pine phone and the person basically came to the realization, and you can see the sadness on his face, that people want their computer to work like an kitchen appliance. Plug it in, press button, it does it thing. No need to learn about how it works.
Reading comments, it's soo strange that I never borked my system once during nearly 7 years of linux usage. Playing games were frustrating, but it was improved a lot by now. My ubuntu never failed to boot, the only audio problem I had was with the mic. Even better, KDE Connect introduced new workflow to me. I wonder why my computer always boots well even when it gets borked during shutdown..
Nowadays, I use my own hand-rolled DE. It still refuses to break on me. Guess I am really lucky or something.
In my experience, when Linux works, it’s beautiful (yay package managers). But once you have an issue or go off the beaten path, it can get complex and confusing very quickly. You’ll find a perfect fix… oh wait, that’s for Red Hat. This is Ubuntu and everything is different.
This man page is thirty pages long and has in depth descriptions of all fifty switches in alphabetical order, but all i want is an example on how to do a very simple, common thing with it. And of course, all commands have their own syntax (of course windows isn’t any better, outside of Powershell).
Don’t curl to bash, it’s dangerous. But heaven help the adventurer that tries to do the install manually. And building from the source? Hah!
The registry gets a ton of shit, and yes, it can be opaque and confusing, but hundreds of text files in hundreds of random directories (that might be a different place on a different distro), all with their own syntax, isn’t necessarily all that more intuitive.
You want this to work differently? Then code a fix yourself! What do you mean you’re not a programmer?
I had multiple Ubuntu installs stop updating because the installer by default made the /boot partition (IIRC) something like 100MB. Do a couple updates and that gets filled up with unused files, and then apt craps itself. And this wasn’t all too long ago - well after the point it was supposed to be the district for the everyman.
Like you, I want to like it more, but it’s never smooth sailing. Granted, a lot of that is familiarity with Windows (and believe me, many curses have been thrown MS’s way), but it always seems to turn into a struggle.
Many (most?) Windows users find Windows to be frustrating. I find Gentoo to be extremely frustrating a lot of times. Frustration doesn't really drive people away from tools that are necessary to them.
I've been using Linux for so long that it's hard for me to give an approximation of what a new user might find challenging, but I think that something important to remember is that computers are hard. I've spent my entire life studying computers and I'm still learning every day.
Most people grew up with Windows and learned how to use it over the years, but remember that it took years, and most of them still aren't very good at it. Linux requires different knowledge than Windows, but it doesn't inherently mean that it's harder. If everyone grew up using Linux we wouldn't hear about "how hard Linux is" but instead about "how hard Windows is".
At least when something is broken in Linux, it probably has a cause (usually the user) and solution, and a way to debug what happened. When something breaks in Windows you've got about 3 things you can try before the solution is to reinstall.
As for solutions, I don't know if there's a certified pathway into Linux - I think installing something like Linux Mint and just using it like a computer would go a long way towards getting you comfortable with how Linux works without forcing you to study. Once you're comfortable using the GUI, you can take a peek behind the scenes at your leisure - there is documentation everywhere for everything on Linux.
When Windows 3.1 came out I had a hard time understanding any of it and never left my cozy DOS CLI with its Norton Commander.
Granted I was still a child, but one might think that mouse-first and colorfulness would have driven my curiosity. Instead I switched when Windows 95 arrived.
After using Linux for years now I still don't understand where programs install to, it's always in some random ass folder.
That's more or less my experience too, my installation slowly breaks over time til I'm fed up and reinstall everything. Not sure what I'm even doing wrong if anything at all.
My main draw towards Linux is the exact opposite experience. I have a Linux install that has been carried over three computer and two harddisk changes over 10 years and it's still as good, or slightly better than it used to be.
My suggestion would be to start with something stable like Debian and read the manual when you want to tinker with it. Especially this: https://wiki.debian.org/DontBreakDebian
My suggestion would be to start with something stable like Debian
It's literally broken out of the box rn. The Debian live images are borked
Speaking of myself, I think I'm just too lazy / have too little time and energy to slowly troubleshoot everything.
I am always on a rush, and when you're on a rush and something like apt not working happens, you just implement some workaround that maybe makes everything worse or is not a full solution. As others pointed, putting commands you see on Google without fully understanding them is a bad idea, and a lot of my "Linux troubleshooting experience" is "trying a bunch of Google solutions in a trial and error fashion".
For example a base issue I have with my current installation is that I firstly installed Ubuntu and then installed KDE, instead of installing Kubuntu, and the installation is kind of glitchy. I never put the time to fix the issues that maybe were not that difficult to fix, but they were unimportant and it just worked. That stuff slowly accumulates over time until the fresh install with that characteristic "this time will be different" feel lol
As others pointed, putting commands you see on Google without fully understanding them is a bad idea, and a lot of my "Linux troubleshooting experience" is "trying a bunch of Google solutions in a trial and error fashion".
Right? I have no idea if the solution is right until I've done it, and it's unlikely that the first one or two I try will be it. They're all black magic commands.
So experienced user yet complaining about it not being beginner friendly?