LinuxLinks has kindly given me the space to publish a semi-regular blog where I share my thoughts on open source, the Linux ecosystem, Windows, and other topics. It’s a place for my opinions and personal perspectives. As you might expect, everything I write here reflects my own views and prejudices.
There is a slightly odd test that some Linux enthusiasts seem to apply to new users. If a person cannot repair a broken package, make sense of a terminal error, or tell you which graphics session they are running, then perhaps Linux simply is not for them. Which, when you stop and think about it, is a frankly daft way to promote an operating system.
Most people do not want a relationship with their computer. They do not want to learn the ins and outs of their printer stack on a wet Tuesday evening. They want to write a letter, sort out a few photographs, watch a film, send an email, and get on with the rest of their day. Quite right too. Nobody proudly announces that their washing machine only works properly if they can interpret diagnostic codes and edit a configuration file. Yet when a Linux newcomer runs into trouble, someone will almost always pop up with three terminal commands and the faint air of “there you go, job done”. As if that settles the matter.
And the funny thing is that Linux can be wonderfully straightforward. In many cases, installing software from a graphical software centre is easier than rummaging around the web for Windows installers and then clicking through half a dozen prompts. Software updates can be handled centrally, without hunting down individual installers, and modern desktops already offer most of the things ordinary users need. KDE Plasma and GNOME have both put years into refining the experience. GNOME’s own design principles, for instance, explicitly aim to reduce user effort and avoid demanding specialist knowledge.
But the mood changes very quickly when something goes wrong. Suddenly the advice involves three different packaging formats, a distribution-specific command, a kernel parameter, and a mysterious configuration file tucked away somewhere under .config or /etc, or possibly both if you are especially unlucky. To someone who’s been using Linux for a decade, the fix might seem obvious. To someone who installed it last weekend, it’s just another problem they didn’t have yesterday.
I use Linux every day, and I still get caught out. Recently, fractional scaling on my 4K monitor left me with blurry screenshots. I’ve spent far too long trying to fix something that ought to be straightforward. And I’ve been using Linux for years.
We should separate power from needless complication. A capable terminal is a real strength, and no sensible person is suggesting we should get rid of it. I use the terminal constantly, often because it’s quicker than clicking through menus. But trouble starts when command-line workarounds become a substitute for actually fixing rough edges in the graphical experience. If plugging in an ordinary printer or changing an app permission means spending half an hour searching forums, something has gone wrong. And telling someone to learn the command line isn’t much of an answer. It is, if we are honest, passing the buck.
I’ve made my feelings fairly clear. But I’m interested in what LinuxLinks readers think. Just how much technical knowledge should someone need to use Linux comfortably?
Then there’s the old excuse that the user has brought the wrong expectations from Windows. I’ve heard this argument more times than I care to remember, and it doesn’t get any more convincing with repetition. Yes, Linux does things differently. Sometimes those differences are genuinely better. Other times, we’re using “different” as a polite excuse for an awkward interface, ropey documentation, or a feature that clearly needed a bit more work before release.
I’m not suggesting Linux should become a pale imitation of Windows. Heaven forbid. There are plenty of things about Windows that I’d rather Linux kept well away from. But being different doesn’t give us a free pass to make simple things unnecessarily difficult.
A computer should reward curiosity without demanding it. You should be free to tinker, experiment, break things and put them back together again. That’s one of the great pleasures of Linux. But you shouldn’t have to muck about with the plumbing just to print a document.
If Linux really wants to attract ordinary computer users, why does it still expect so many of them to think like system administrators?

Please read our Comment Policy before commenting.
The craziest rebuttal to all this has to be the people who openly say they don’t want non-experts using Linux. And they don’t care about having more users. Seriously? Since when did you need to pass some sort of technical competence test to use an operating system? It’s elitism, pure and simple. You’d think people who champion free software would be pleased to see more people using it, not trying to keep it as some sort of exclusive club.
I seem to recall that Linux has about 4% of the desktop operating system market.
Yes, latest estimate is about 4.65%
I think that’s overinflated tbh
I think most desktop OS numbers are over inflated as we probably need to rethink our definition of a desktop. I see a lot of people using their tablets with a keyboard to do the things we traditionally associate with desktops.
However, in the way of Linux vs Windows vs Mac I would believe that Linux is 5ish (heavy on the ‘ish’) percent of desktop installs. The number of tech savvy people installing their own OS is always going to be higher, but I have seen a fair number of people with less technical knowledge running Linux as well.
Heck my wife’s grandfather was right around 80 when I first met him just over 20 years ago and he was comfortably running SuSE Linux, which he had installed himself. He was a farmer his entire life without special technical expertise and he had successfully transitioned away from Windows XP and never once asked me or my wife for help with his computer.
I’m not convinced the average desktop user will ever really take to Linux. Remember the fuss when Microsoft simply moved the Start button? People were up in arms over something so trivial. Now imagine asking them to get used to a completely different operating system. I’d love to be proved wrong, but I wouldn’t hold my breath.
I think you’re right that many people are reluctant to change something they’re familiar with. But that makes it even more important that Linux provides a straightforward experience. If someone is already nervous about switching operating systems, encountering unnecessary complications isn’t going to encourage them to stick with it.
With the recent AI craze, CLIs and TUIs are back, so “GUI should handle it all” is a bit behind the times. All the rest, you’ve just stolen my words.
The issue with desktop Linux is that it’s not, and never has been, “you can tinker with your system”. Instead, it used to be “you have to tinker with your system to get anything usable” until quite recently. I’ve got an issue with sound ceasing to work about a month ago because wireplumber went to a different configuration layout and converted its old stuff in quite a half-baked way.
Trump renamed Artificial Intelligence (AI) to Super Intelligence (SI)
It hasn’t reached our corporate yet 😉
You cannot use the words ‘Trump’ and ‘intelligence’ in the same sentence. In fact not even in the same paragraph.
Your WirePlumber example is a good illustration of the problem. There’s nothing wrong with using the command line, but people shouldn’t have to dig into configuration files just to get their sound working again.
For a start, updates shouldn’t break working configurations. And when something does go wrong, there should be a simple way to fix it through the desktop. WirePlumber already has ways to reset its configuration, so why not make those available through a graphical tool? It wouldn’t solve every audio problem, but it would be better than expecting users to dig through configuration files and run terminal commands.
I disagree 100% with this entire article. You don’t have to be an “expert” to use Linux; that sounds just like something I’d expect from someone who doesn’t use Linux in the first place.
Take me, for example: I compile my own kernels, modify a lot of config files for my own use cases – heck, I’ve been known to write a few scripts in Bash and Python.
Am I a Comp Sci major? Do I work in IT? Am I a developer? The answer is “no” to all of the above. I drive a semi for a living.
If some knuckle-dragging truck driver can do Linux, what everyone else’s excuse?
Hi Jim
Compiling kernels, editing configuration files and writing scripts might be second nature to you, but they’re hardly everyday activities for the average computer user. Whether you drive a truck or work in IT is beside the point IMO.
You’ve clearly developed considerable technical knowledge, which is great, but most people simply aren’t interested in doing that. They just want their computer to work without having to understand what goes on under the bonnet. And that’s really the essence of the article.
This is a false argument. Windows, and macOS are just as difficult, if not MORE difficult to use than Linux. The difference is that people are trained, some from a very young age, how to use Windows, macOS, iOS, and Android. Stick a non-computer user in front of ANY operating system and they will have a VERY hard time.
The issue isn’t that “Linux” should be made easier for new users. The issue is that Linux is NOT a GUI operating system. It is a collection of utilities and a kernel that some people have chosen to package together with a GUI. But the GUI is an add-on. Every desktop environment and window manager that exists for Linux is an add-on that has its own design goals, priorities, and features. The “plumbing” of the terminal allows users to work around whatever limitations a particular DE or window manager has. The same can be said for macOS and Windows, as there are LOTS of features and tools that they both have that are completely hidden from users unless they know the appropriate terminal commands.
Now as for packaging formats – yeah that’s a complete mess.
I agree that familiarity plays a big part. Most people have spent years using Windows or macOS, so naturally they’re more comfortable with them. But I think you’re missing the point a bit. Ubuntu, Mint and Fedora are sold as desktop operating systems, and it’s perfectly reasonable to expect their graphical interfaces to do the job. Whether the GUI is technically an add-on doesn’t really matter to the person sitting in front of the screen. There’s nothing wrong with using the terminal. I use it all the time. But there’s a big difference between wanting to use it and having no other choice.
“Windows, and macOS are just as difficult, if not MORE difficult to use than Linux”. They are much easier to use but harder to troubleshoot. Linux is easier to troubleshoot once you understand how to use it.
“The issue is that Linux is NOT a GUI operating system.” Spot on. And while it is like this, “Linux desktop” is just wishful thinking.
“Stick a non-computer user in front of ANY operating system and they will have a VERY hard time.” I’m in the middle of such “experiment” with my extremely non-technical mother-in-law. She got really tired of endless ads in Windows casual games, so I installed WSL/g with a couple of games on her system. Guess what – these games are “very incomfortable” for her.
I think you’re mixing up the Linux kernel with a desktop Linux distribution. Linux Mint, Ubuntu, Fedora and plenty of others are very much graphical operating systems. Some are even marketed specifically at people moving away from Windows. So the idea that Linux isn’t a GUI operating system is a bit daft.
I’m not convinced Windows and macOS are inherently easier to use either. Most people have simply spent years getting used to them. Put a lifelong Windows user in front of a Mac and they’ll probably struggle with a few things too.
I’m not sure what your mother-in-law’s experience proves. You’ve installed a couple of Linux games through WSLg on Windows, which is hardly the same as sitting someone down in front of a proper Linux desktop. Perhaps she just doesn’t like the games? At the end of the day, ordinary users shouldn’t need to know what’s going on under the bonnet just to get on with everyday tasks. That’s the whole point of making Linux accessible.
You can run a Linux system without any GUI whatsoever, and it shows quite a lot once you try to introduce a proper GUI. Windows is built GUI-first, IIRC Windows GUI applications can’t even access a terminal.
“Some are even marketed specifically at people moving away from Windows”. Since when is “marketing” equal to “truth”?
I know. I’ve been using Arch for 22 years or so.
I didn’t just talk about marketing. Linux Mint, Ubuntu, Fedora and plenty of others are very much graphical operating systems.
I voted for Minimal. I’m a Windows user and occasionally have to use the command line (with PowerShell) to fix problems.
I’m thinking of trying Linux but it still looks a pig’s ear to be honest. That’a different story though.
You should have tried SLS. I still have the 30 floppies. They are available to borrow 🙂
That’s why I created XXRI OS Lite! , 0 terminal required, very lightweight, you can run it in 300mb of ram, it has Translucent UI first experience, you dont need terminal to install app, you can basically do it in xxri store, it provide all package needed just one hit lile macos, also, for those that unavailable, you can install it like windows, just download an appimage, double click, it will install it like it was exe in windows , for software update, you can just go to settings, hit update software, done.
Hi
Erik published an article on your distro yesterday. It’s included in the Big List too.
https://www.linuxlinks.com/xxri-os-lite-lightweight-linux-distribution/
Is it possible to troubleshoot this system without touching a terminal?
OK, I use Archlinux and you just can’t use it without being able to use the terminal. But I worked in IT for 40 years before retiring. I moved my then 65 year old wife to Linux Mint over 10 years ago, she never uses a terminal, and Mint seems to be fine. I occasionally check if she’s done the updates and upgrades, but she has! So I have told several old folk round here to try Mint, and quite a few have (I just hope it’s not ‘cos they expect me to dig them out of the…)
You might have signed up as tech support!
So at the pharmacy I run, we do a lot of community activities, including having several old guys (myself being the youngest by far at 49) that fix various tech problems for people on Saturdays. These problems involve various platforms including Windows, iOS, Android, Macs, Linux, various wearables, and even going outside to work on things like Apple Car Play. That said, the things that break on any of these platforms are generally beyond the average Joe (one of our former Apple employees and old school Unix grey beard is named Joe and we usually let him know that we consider him to be an above average Joe). Maybe it’s because I’m a Linux user, but I usually find the Linux fixes easier, quicker, and more logical to understand why it went wrong when I’m explaining it to the client. I think most distros are ready for mainstream use by the masses as they often work better and more reliably than other platforms and are just as easy (sometimes easier) to navigate when compared to other platforms.
Linux is easier to troubleshoot because it’s harder to use (the knowledge delta is smaller).
Linux may well be easier to troubleshoot, and it may well be harder to use, but I don’t see why one necessarily follows from the other. Linux is often easier to troubleshoot because it provides better access to logs and diagnostic information. That doesn’t mean it has to be harder for ordinary people to carry out everyday desktop tasks.
Installing desktop software is a good example of where Linux frequently confuses newcomers. Depending on the distribution, they might encounter traditional packages, Flatpaks, Snaps, AppImages and third-party repositories. Each has its own way of doing things. Experienced Linux users may find this perfectly straightforward, but it’s easy to forget how bewildering it can be.
I don’t generally find most of the people that come to me with Linux problems are struggling because of competing package formats. Both Android and iOS have taught people to use an app store/repository for installing and upgrading apps. I also don’t find people coming to me not understanding how to launch their browser or write a document on Linux, but I do have people coming to me with problems with trying to install Office 365, especially when they want it on more than one device.
The general idea that I am trying to make is that every OS has some rough edges and nontechnical users get hung up on them. Linux does not seem harder based on the subset of people that walk into our store.
As a weird aside, I am a little sad to see that Chromebooks are going to be phased out. In the past decade that we’ve been offering this help, I may have occasionally been asked to help someone set up a Chromebook (by a technophobe), but I rarely ever had any problems from those clients afterwards.
by 2018 we put on a rake of laptop a ubuntu lts from that time a couple of older men over 75 years who had not yet gotten their hands on a mouse and by the pc had only heard on TV, I learned to use skype to talk to their daughter emigrated to England, the gentleman also wanted a game of chess, in less than an hour they both knew what to do, obviously and took some notes, I was called once after a year because they no longer operate skype, I see that some talk about compilations but who out of users compilates something in the last 10 years?! The problem that arises is not why the population wants it or not, but is reliable, when you buy something, there is a certain liability on the part of the seller, if something goes wrong, you can ask for compensation or even go to justice. If science fiction wonders overnight, Windows will disappear, all the problems in that operating system will surely be in Linux (including gratuity). You really want this? That leads me to more philosophical questions but that’s not the case for this topic. I’ve been enjoying linux for more than 15 years and my son is surprisingly conservative than me, has a Debian Mate 11 and is not going to change it anytime soon, according to the principle that you don’t change something that’s been working well for a long time.
I agree there’s no point changing software just for the sake of it. But working doesn’t necessarily mean secure.
Debian 11 stopped receiving official security updates in August 2026, so sticking with it carries risks. Moving to Debian 13 with MATE would give your son much the same experience without those security concerns.
the other day I noticed that in linux mint no longer printed at HP lj pro m130nw although the scan could scan, I could solve this myself, but for fun I put on opencode with the muse spark free model to solve, so everything free solved in 10 minutes, so I did to some friends who had recently installed 26h2 with dozens of problems in drivers, opencode free resolved in 30 minutes everything without me looking for the drivers on the manufacturer’s website. So what skills do you think you need to have users in the future? I think A.I. (or fck SI) in the future somehow unifies all operating systems
I tried an experiment with someone who had virtually no computer experience. I gave him two laptops, one running Windows 11 and the other Ubuntu, and asked him to install Krita. All I provided was the download URL:
On Windows, he downloaded the installer, double-clicked it, followed the prompts and had Krita running in about five minutes.
On Linux, he downloaded the AppImage and double-clicked it. Nothing happened. He had no idea that he needed to make the file executable. After eventually finding that out, he ran into another problem involving FUSE, which meant absolutely nothing to him.
After an hour, he still hadn’t got Krita running.
Of course, he could have installed Krita through Ubuntu’s software center, but that wasn’t the task. Both systems were given exactly the same download page and instructions.
It’s just an example, but it illustrates how something straightforward for an experienced Linux user can be thoroughly confusing for a newcomer.
First, It sounds to me like you tried to sabotage the results by taking someone that hasn’t really used Ubuntu long enough to think about their repository and sent them to a download hyperlink instead of just telling them to install Krita. I would like to point out at this point that anyone helping a new user with an install should always show them the system’s package manager and briefly explain repositories.
Second the people in charge of Krita’s website could have included a statement like, “It is recommended for Linux users to install Krita using their distributions repository unless they specifically need to install the latest version.” Then, when they clicked on the download link, a statement like, “Newer Linux users should be warned that your system’s package manager will not be able to automatically update this version, proceed knowing you will be responsible for manually installing updates.”
Sabotage? That’s a ridiculous accusation. I gave the same inexperienced user the same starting point on both systems and let him work things out for himself.
You’re saying I should have explained repositories and package managers first. But that’s exactly the problem. Why should someone need a lesson in how Linux handles software before they can install a program from its official website?
You’re not challenging my argument. You’re demonstrating it.
Sorry Ben, I see the situation differently. You took someone used to MS Windows and gave them the starting point that makes most sense for Windows users. Normally I don’t send Linux users, Android users, or iOS users to a download page. I tell them to check their repository, Play Store, or App Store. I would show a new user of any of those platforms how those items work prior to cutting them loose if I am the one helping them get set-up for the first time.
I can see the idea that you thought it was a fair comparison, but I respectfully disagree. However, I do think that package maintainers for AppImage, Flatpak, and Snap should be encouraged to mention repositories as well.
Sean, I made it very clear that this person had virtually no computer experience. He wasn’t a Windows user. He was a complete beginner on both systems.
You keep arguing that I should have taught him about repositories and package managers first. But that defeats the whole purpose of the experiment. I wanted to see how he’d manage without guidance.
You’re looking at this through the eyes of an experienced Linux user. That’s precisely the problem I’m highlighting.
Ben, if he/she were truly a complete newbie to computers altogether and had to learn how to use a mouse, a keyboard, and a web browser then I am impressed that you were able to send him a URL and he was able to install it on Windows. It sounds like this person has reasonable potential for being able to do a lot on computers moving forward.
The download URL was still biased towards the primary installation method for Windows. If you handed him the following URL:
<was going to include URL here, but comment posting guidelines prohibited>
and said, “Go to this website in your browser and install Krita.”, that is how it is done on Windows.
If you had handed that same person a note that said:
Krita
and said, “Go to your package manager and install Krita.”, that would have been equally biased towards the Ubuntu user although it is in the Microsoft Apps Store for $14.99. Neither is a fair way to prove which has a more intuitive method for a new user.
If you had just handed the completely uninitiated computer user a slip of paper that only said:
Krita
Then asked them to figure out how to install it on each it might have been more interesting. However, even at that, whichever system they attempted it on first would likely skew how they would attempt it on the second.
I know you are upset on my push for education on repositories, but I would not feel good about avoiding teaching a Windows user about safe vs unsafe places to get software downloads and things to be cautious of. I would even teach them about S Mode, since I’ve seen an increasing number of Windows computers initially set-up that way. So I would still bore the poor soul with some technical details for their own benefit.
Ben, I am sure your attempt had very good intentions, but it is difficult to create a system of tests that do not create biases if we don’t educate users on both systems before we cut them loose.
Sean, it was never intended to be a scientific comparison, just a simple illustration of one beginner’s experience. We clearly see things differently, so I’ll leave it there.
Ben, this is exactly how usability testing works. Companies regularly give inexperienced users tasks without guiding them through every step, to see where they struggle. Teaching someone how to do something beforehand rather defeats the point. I agree your experiment wasn’t a scientific study (it’s a sample size of 1), but it does highlight a genuine usability problem.
I will acquiesce that the “Let them struggle” testing procedure is more common than “System familiarization”, although both are used. However, you don’t generally give them a specific URL that biases them towards a particular methodology but instead offer up a specific task; which is generally how the “Let them struggle” methodology is done if were attempting a fair test.
At least one of my problems is that I’m looking at it from the perspective of someone that is often helping clients to learn new skills, which is why I over focused on wanting to provide familiarization.
I really am sorry if I came across as, to use the Pittsburgh vernacular, a jag-off.
“ However, I do think that package maintainers for AppImage, Flatpak, and Snap should be encouraged to mention repositories as well.”
It’s for quite a good reason they don’t. You don’t really want to “be responsible” for gazillion maintainers compiling the software in parallel with you, in heck knows what way.
I thought most ditros primarily used repositories from just half a dozen distributions (Debian, Ubuntu, Arch, Fedora, SUSE, Gentoo). I do have reasonably high expectations that their package maintainers will generally do a good job of compiling. The ones that roll their own packages are generally more niche, and I expect their users to be more tech savvy.
I have seen some sites offer suggestions on how to install from some repositories depending on your base distribution before going down the path of AppImage, Flatpak, snap, and compiling yourself. I kind of like those sites.
The second download choice on krita.org is a flatpak. You simply single-click “install” and Krita is running in about five minutes…
Yes, Krita offers a Flatpak, but clicking Install on Flathub doesn’t necessarily install the application. It depends on whether Flatpak and the appropriate software-centre integration are configured. On some distributions, it simply downloads a .flatpakref file. Ubuntu, for example, does not include Flatpak support in its default App Center.
The experience should be straightforward for inexperienced users, without requiring them to understand Linux packaging systems.
I don’t agree with this statement. If you read between the lines, a Windows user does not need to know a thing about how Windows works as everything works as advertised. This is absolutely not true. There are countless occasions a ‘normal’ Windows user has no clue about what to do when a specific problem occurs. The difference with Linux is that this Windows user will probably find it easier than a Linux beginner to find someone to help and assist.
Dear sir,
I read your article twice and, overall, I agree with you.
I think there ought to be an article like yours on every topic or issue or aspect that is suspected (or considered) to be a disadvantage (or a major difficulty) to the general adoption of Linux by ordinary non-computer-savvy people. Allow me to list a few here:
You wrote: “Most people do not want a relationship with their computer. They do not want to learn the ins and outs of their printer stack on a wet Tuesday evening. They want to write a letter, sort out a few photographs, watch a film, send an email, and get on with the rest of their day.”
Exactly! And this is where Linux distros should focus on and improve.
Linux overall adoption did not increase after Windows Vista and Windows 8 releases and despite the fact that Windows Vista and Windows 8 were (widely acknowledged) market and product failures.
In August 2026, statcounter.com measured Linux desktop worldwide usage at 8.76%, after 3 consecutive months (May: 3.81%; June: 5.59%; July: 7.51%) of increase. In September 2026, it dropped back to 4.54%.
Thanks, I’m planning on writing more articles where Linux really needs to step up.
tbf, Linux is amazing.
I just want to say, I completely agree with Ben on this 🙂
I agree. Linux has come a long way, but I still think it could be so much better for desktop users. What’s missing is some real leadership.
I’m not suggesting one organisation should control Linux, but wouldn’t it be great if the major distributions and desktop projects worked together on a few common goals? Make installing software straightforward, agree on some basic usability standards and put more effort into testing with ordinary users.
Linux doesn’t need to lose its diversity, but a bit more coordination could make a huge difference. Imagine if Linux became as successful on the desktop as it already is on servers. That would be something special.
”
”
Both fixed and rolling releases have one “little” deficiency – it’s either fixed for everything or rolling for everything. And if I want the user-facing GUI applications as fresh as they get, with the rest being updated as seen appropriate by the distro maintainers – too bad. The “immutable system + snap/flatpak for user-facing applications” seems promising. And how ironic is that Windows has had such approach for years…
I know quite a few users who run a stable distribution and use Flatpak to keep their desktop apps up to date. Personally I avoid Flatpak.
Having different ways to install software is fine if you know your way around Linux. For someone new to it, though, it’s just another layer of confusion.
Immutable system + software center that recognizes only Flatpak or has a good rating system so it can show what is preferred.
Updates on Windows are applied in an “atomic” way and the whole system can be rolled back to the previous state? I wasn’t aware of that…
Updates in Windows are also extremely slow to download and install.
I started using linux in january, starting out using linux mint with zero prior experience. Personally I’m ready and willing to learn, it’s just that finding good resources to learn from isn’t always easy or straightforward. I appreciate manuals and guides that I can use as a reference while I’m still practicing these new skills. Stepping stones to help bridge the gap from beginner to expert.
I can see where you’re coming from. There’s loads of Linux documentation out there, but finding something that explains things without assuming you already know the basics isn’t always easy. And lots of documentation is out of date or incomplete.
PCmag says 1998 will be Year of the Linux Desktop and I cannot wait for it to get here!
No one reads magazines these days.
Time is money, or so goes the saying. In life, we all learn that something either costs money, or time, or varying proportions of each. When I had both my feet firmly planted within the Windows world, it used to be that you paid your money and walked away with Windows, which mostly used to work fine… until it didn’t. But then MS got greedy, and your money wasn’t enough anymore.
I was already fairly tech-savvy when I switched to Linux, and being no stranger to assembling my own desktop PC’s, as well as knowing how to get myself out of most IT issues, I was lucky enough to learn it the right way, and enjoy doing so. It also helped to have the right attitude about it all, and instinctively understand that, while Linux didn’t cost anything up-front, it instead asks you to spend enough time to learn it well enough… just so you can make it work for you, and not the other way, as Windows did. And granted, just like anyone else venturing in this universe, I encountered, and still do, my fair share of problems. Did any of them make me wish that Linux was simpler, easier, or less time consuming than what it is? No. Why? Two reasons.
Not long ago, I found out that The Linux Foundation fields over 10,000 monthly requests for changes to the kernel, and it releases an update to it every 6 months. At the other end of the spectrum, there are over 700 separate distros, with thousands of pairs of hands and millions and millions of work hours put into it to keep the whole galaxy turning. Just try to wrap your mind around the amount of work that goes into it, and yet, it doesn’t ask from end users like myself for one single brass razoo upfront. The least I can do is to validate it all by taking time to learn as much as I can out of all that’s so freely available, warts and all. It would be a shame not to.
Secondly, given its FOSS premise, open collaborative transparency and its largely egalitarian, generous sharing, Linux is the ultimate symbol of free creativity. Yes, that also means that not everyone is marching in lockstep to a single tune, but instead plodding along competing agendas, uncoordinated, with all the associated contradictions, arguments, oversights and duplications, not to mention the self defeating inherent element of deterrence such an immense diversity of choices offers upfront. It’s like walking into an ice cream parlor that offers over 700 different flavors. Choice paralysis, anyone? But, on the other hand, what would be the alternative? If all you want is one single, highly coordinated product, with no room for uncertainty, or freewill, for that matter, then look no further than MS or Apple.
Let’s just all remember that Linux, after all, isn’t a consumer-grade product. Instead, Linux, from the ground up, was primarily designed for servers, not end-user PC’s. From the unmistakable importance of being familiar with using a terminal, all the way to its ability to process updates without the need of a reboot, Linux just screams “I’m meant to rule servers, not sit cramped within the confines of a single PC that just sits longer casting a shadow than giving off light, to look after one single, hapless end-user”. In comparison with MS Windows’ haste to abandon its visible reliance, or underpinnings in DOS, from its earliest iterations, Linux’s stubborn insistence to remain a CLI-centric creature that’s just forced to wear a GUI mask for the sake of making itself ‘more user-friendly’, means that it’s not long before those brave enough to explore its ecosystem get to find out how futile it is to pretend that Linux can be anything else other than what it is already.
Unlike those who’d rather point at one distro or another, as ‘its similarity to Windows being what makes it a perfect choice for its replacement’, I’d say that you’d be better off asking yourself if you are ready for Linux. Fortune favors those most prepared, so do yourself a favor. It would be a shame no to.
Gabe, thanks for such a thoughtful comment. I agree that learning Linux can be enormously rewarding, and its diversity is one of its greatest strengths.
Where I disagree is your assertion that Linux isn’t a consumer-grade product. Linux began as a project for personal computers, not servers, and there’s nothing inherently preventing it from delivering an excellent desktop experience.
The Steam Deck is a good example of what happens when Linux hardware and software are properly integrated.
I also don’t accept that users should feel obliged to invest substantial time learning an operating system simply because it’s free.
There’s an important distinction between having the freedom to explore how your computer works and being forced to do so just to accomplish everyday tasks.
Linux can retain its flexibility, transparency and powerful command line without expecting everyone to become technically proficient.
The problem isn’t that Linux cannot be consumer-grade. It’s that the desktop ecosystem doesn’t consistently deliver a consumer-grade experience.
And that’s precisely what I think needs to change.
Jess, you’re right, the Steam Deck is a good example of Linux working well on a consumer device, but we’re talking about a gaming console that’s nowhere in the same hardware category as desktop PC’s, even though they can also be used that way. And Valve couldn’t exactly get MS to put its own OS in it instead, as MS already flopped miserably in its partnership with Nokia, to get the Lumia smartphone series to become a serious challenger to the army of Android-powered portable devices. I had one, and I couldn’t even get its Windows mobile OS to pair up with my Windows 8 desktop PC, in the same way I can get my current Android smartphone to connect with the Linux on my PC. It was one helluva cluster-fudge.
And just how much of an after-thought on the Linux priority list is its readiness to compete with Windows in the desktop PC world? Well, let me share with you another ridiculous fiasco. Not long ago, I’d installed a Swann CCTV system that, despite having its DVR box using a Linux 4.8 based GUI, it only offered a Windows EXE, an Apple DMG and and Android APK to let you install the remote access program on a desktop PC. No matching Linux app! The damn thing runs on Linux, but it doesn’t let you install a Linux app to access it remotely. That, right there, is just another cluster-fudge! But then again, it’s not like the blame rests squarely with Swann, given how many different installers they would’ve had to supply separately just to accommodate the mainstream Linux distros… that only live on 4 percent of PC’s worldwide. For starters, they’d have needed to put out a DEB file, an RPM, a DNF, a Snap, a Flatpak, an AppImage, a TAR.GZ, and maybe even the source code binaries for prospective fringe Linux users to compile the installer themselves. God help us all! And then, how long before any of them would just become obsolete and incompatible with whatever other dependencies that installer file needed? Yeah, there goes the customer satisfaction, right out the window!
No, Linux is about as consumer grade as a hand-grenade with its pin pulled out.
Gabe, I think you’re missing my point. I’m not saying Linux is consistently consumer-grade today. I’m saying there’s no reason why it couldn’t be.
Your Swann CCTV example actually reinforces that argument. It’s an example of a poor consumer experience, not proof that Linux is inherently unsuitable for everyday users. And developers don’t need to produce half a dozen different packages. Flatpak and AppImage already help address that problem.
The Steam Deck shows what Linux can achieve when hardware and software work well together. Being a gaming handheld doesn’t make that achievement irrelevant.
I enjoy learning Linux as much as you do, but I don’t see why everyone should have to. There’s a big difference between choosing to explore an operating system and being forced to understand its complexities just to get things done.
Linux doesn’t have to sacrifice its strengths to become more accessible.
Get any CLI-based AI (e.g. Claude), prompt, et voilà! So far, using it since a couple months on a handcrafted bare Arch setup, it saved me countless hours of struggle: any problem is solved in about a min. Am I gradually losing my Linux skills? I’m afraid so. Do I need my Linux skills anymore though? This trending toward nope.
Get a Mac.
“Get a Mac”? That’s a rather expensive workaround for a problem Linux should be fixing itself.
Reasons not to use a Mac:
Here’s my top 10:
When I first used Linux mint it was like using windows. Finding and installing apps was easy too.
I was using 12 year old laptop and desktop that couldn’t run windows.
The one common issue people may have is configuring printers. Otherwise the difficulty of Linux is overestimated. In the last 8 years I’ve not had to reinstall Linux and it hasn’t slowed down.
If anyone has a problem now, chatgpt will solve it. I’ve learnt some arcane stuff from it.
Natural inertia stops people trying alternatives to Windows and macOS. And usually good enough is good enough.