Okay:

You don’t have to deal with scripting and command-line stuff, but all the major tinkering under the hood depends on it. The amount of customisation and tinkering is fairly infinite, so past a certain point you just can’t build graphical stuff to cover every single possible choice - and that’s where the gibberish comes in.

Baseline concepts:

‘Operating system’ means different things in different contexts, and this can be confusing.

---

Context 1: technically correct

Your computer has a big chip that runs programs, and a bunch of hardware that actually-does-stuff: network card, graphics card, disk drive, mouse, keyboard etc. Programs need to talk to the hardware and make it do stuff, or else they don’t actually… do… anything.

There’s two problems with that:

There’s a gazillion kinds of hardware out there, that all has its own language for talking to it, and your program would either only run on one EXACT set of hardware, or it would have to speak all gazillion languages and be too big to fit on your machine.

The second problem is that in order to do more than one thing at a time, you need a bunch of programs all running at once, and they all need to use the hardware, and without something to coordinate the sharing, they’ll all just fight over it and everything falls down in a tangled heap.

A good analogy for this is a restaurant. They aren’t just public kitchens where you can just wander in and start preparing your own meal, taking ingredients/equipment/space however you want, then just carry it to whatever table takes your fancy - and you definitely can’t have all the customers doing it at once. Especially if they don’t know how all the equipment works, where the different ingredients are kept, etc - it would be an absolute disaster, and there would be fights, injuries, fire and food poisoning.

So instead there’s an agreed-upon system with rules, and people that do the cooking for you. You make a reservation or queue at the desk, you are told which table you can have, you go sit there and a waiter brings you a menu. You pick the food - and depending on the place, maybe ask for customisation - then wait and they bring it out to you, then you sit there, eat it, then leave.

That system-with-rules is the operating system, or more specifically the operating system kernel. Any time a program wants to do more than think to itself, it has to asks the OS to do it, and bring it the results.

In this analogy, fundamentally different operating systems (windows / linux / OSX / android / etc) would be like different kinds of (5-star / sushi-train / pizza place / burger joint / etc) that have different rules and expectations and social-scripts to interact with them. A program written for one OS would have no idea how to ask a different OS for what it wanted, and wouldn’t be able to run there.

---

Context 2: what people usually mean

It’s all well and good to have a machine that can run programs and do things, but the human sitting in front of it needs to be able to interact with the thing, so you can poke buttons and move files around and move windows and stuff.

And so there needs to be a crapton of programs all working with each other on the thing to provide all this functionality, and the whole user experience - preferably with a consistent design language and general expectation of how everything should work: you need a desktop environment.

In restaruant terms, this would be the specific brand/franchise/corporate-culture that runs the place. Yes, the general idea is that it’s a burger joint, but specifically it’s a mcdonalds, or a wendy’s, or whatever that homophobic chickenburger place is called - it’s got the decor, it’s got the layout, it’s got the specific combo meals, etc etc, the same uniforms, the same staff policy, etc.

Now here’s the thing:

Let’s say there’s only one sushi franchise in the world. That’s like Windows - there’s updates new versions and some slight variations (server versions aside), but you walk into one, you’ve walked into them all. There’s one Windows kernel, and one windows desktop environment that goes with it.

And say there’s only one pizza-place franchise in the world, and they all look the same, have the same menu. That’s like OSX: there’s one kernel, and similarly one OSX desktop enviroment to go with it. A mac is a mac, and it does mac things.

But linux… linux is different. With Linux, it’s there’s 900 different burger-joint franchises in the world, and literally anyone can go start a new one if they want to put the time into designing one from the ground up. The paradigm is the same - order at the counter at the back, menus on the wall overhead, grab bench seating wherever or get it to go - but every place can design the look and feel, the menu, the deals, the other amenities, the staffing structure, etc.

And the different franchises - that’s what distros are.

It’s the set of programs all working together that create a whole working enviroment, but everything uses the standard kernel to actually get stuff done. If your program can run in one linux distro, then it should be able to run in a different one, because your program uses the same standard set of requests in order to do things.

The windows and the menus and the desktop apps and the way the interface behaves and how you configure everything can be different, but the core functionality that the software uses, is the same.

---

Now, for the most part, Windows is like NO USER-SERVICEABLE PARTS INSIDE, all the fiddly internal bits are carefully hidden away and made deliberately opaque. You don’t need to know, we don’t want to tell you, we’ll let you change the wallpaper, but for everything else, we decide how it’s wired up. If you want it to do things slightly differently to suit your own workflow, tough.

Macs are kind of the same deal: for the most part it’s no-touchee, you’ll break stuff. Just push the very shiny buttons and be happy that everything Just Works ™.

But Linux… doesn’t seal anything in plastic. All the gubbins are not only there on display, they’re mostly all human-readable and human-tinkerable with. Instead of mysterious monolithic chunks of software communicating with each other via hidden channels, with configuration in databases you don’t get to see… it’s mostly scripts you can read and tinker with, and plain-text config files you can edit, all writing useful details in highly-visible log files that you can read through when things don’t do what they’re supposed to.

Now with a lot of distros, you absolutely can just push buttons and treat the thing like a Windows box, and never have to tinker with the fiddly bits. You’ve got a browser, you’ve got apps, you’ve got games, it just does the thing. But if you want to start getting technical, you absolutely can - unlike windows or mac.

But this very ability to configure and tinker and patch bits on - and the fact that most distros don’t have a gigantic microsoft-sized coordinated team all following one shared vision, but are wired together like a kind of junkyard frankenstein from thousands of separate teams as a labour of love - means that occasionally you will need to get technical to deal with small annoyances or use-cases they didn’t think of.

Just by reading the first sentence I can tell you that you will enjoy Linux. Don’t worry about all the technical stuff it seems complicated because you don’t know it. Just install Linux and use it and you will learn what all that stuff means. Since you’re building a new PC you got nothing to lose from trying out a few different Linux distros.

It’s a multifaceted answer for me, I feel.

Linux is weird, on a technical level. It’s funky and broken and has weird quirks you have to remember. But it’s not malicious. Wendel from Level1Tech said it best in one of his videos: the headaches with Linux are haphazard, the headaches with Windows are adversarial.

It’s not a perfect solution to Windows, but at least for some people, the respect that it has for its users (ie, no ads, not trying to fight you on everything you’re trying to do, gives you the ability and freedom to tinker as you please) offsets its technical problems.

Additionally, Linux is missing a lot of core applications. There’s many applications that do have a Linux version, and many that can run through a compatibility layer, and out of those that are left, many have really solid replacements. Heck, you might be surprised to find that some of the software that you use already were originally intended to be replacements for Windows-only applications.

But there’s still a handful of core applications that don’t work on Linux and don’t really have a good replacement, and even missing 1 can easily break someone’s work flow. No, LibreOffice isn’t a full replacement of Microsoft Office, no, GIMP can’t actually replace Photoshop.

As for terminal, there’s no way around it. You will have to open terminal at some point. To be clear, most, if not all, things that you might imagine yourself doing likely has some way of doing it through a GUI. The issue is that as a new user, you don’t know where the GUI is, or what it’s called, or how to even ask. And when the tutorials that you find online tell you to just use terminal, that ends up being the only practical way of getting things done. So it’s a weird Catch-22, where only experienced users who know where all the menus are will know where the GUI options are, but it’s the new users who need it the most.

My understanding is that Linux developers in the past several years have been explicitly trying to make the OS more accessible to a new user, but it’s not quite there yet.

Overall, I think Linux is deeply flawed. But seeing how Microsoft seems to be actively trying to make Windows worse, Linux ends up being the only OS where have faith that it will still be usable in 2 years.

If anything, the more people switch to Linux, the more pressure there will be to make the OS more accessible to new users, and also for software companies to release a Linux-compatible version of their software. Some brave people just need to take the dive first

The reason why people talk so much about the terminal is:

1. It’s easier to tell newbies “input this command” than to guide them through a GUI.
2. The terminal gives you a lot of flexibility to customise stuff.

You’ll probably want to learn the terminal for any serious customisation. However, you don’t need to deal with it in your everyday usage.

I’d suggest you to use a Live USB, like other users recommended. Linux Mint, plus plenty other distros, can run straight from the USB. It’ll be better for you to judge if you could/should be using Linux this way.

About the thousand distros, most of them don’t matter. And if you’re a newbie, stick to Mint and you’ll probably not regret it.

You can install Ubuntu (or many other Linux distros) to a bootable USB drive. Restart your computer, press F2 or whatever it says to open your boot menu, and then boot from the USB drive. This will let you run a full version of Linux, which will let you experiment around with it so you can get some experience and see if you like it or not, without having to uninstall your current OS or repartition your drives and mess around with dual-booting. It’ll run a bit slow since it’s gotta come off a USB drive for everything, but that should at least give you a good estimate on whether or not Linux is right for you.

Linux mint doesn’t require the terminal for almost anything. If it is required anywhere, there will be step-by-step instructions, but even then there is likely a better solution specifically for linux mint that doesn’t require the terminal.

Use the software manager and update manager and you’re set. Don’t install applications from the terminal, it will be easier to let the manager applications keep track of it all.

For super advanced stuff, sure, you might want the terminal, but you don’t need these things. If anything, it will be a good opportunity to learn.

Get a USB, put linux mint on it and boot from it just to try out. It can run without being installed on your computer.

Don’t over think it, Mint will be fine. Modern Linux is very user friendly, and you can do almost everything with some form of UI.

There’s nothing stopping you from making a boot key and messing with Linux or making a partition of your storage. Nothing ventured, nothing gained.

That said, as someone who is also very visually inclined, I’ve tried a couple of different distros over the years and always bounced off. I kept encountering the dumbest little issues that most people didn’t get, and it always required Terminal to fix. It’s those moments when you get to learn how obtuse and unwelcoming some of the Linux community can be.

If you do decide to do it, use an LLM. That shit will turbo charge your learning curve.

As side note, you can start learning now or later, choice is your. This is just an opinion tho

Get a live version of any distro burned into an USB.

You can give it a try this way without compromising anything.

There are thousands if not tens of thousands of distros. Wikipedia has a really cool Linux family tree.

If you think of the Linux ecosystem as a whole, a distribution or distro is just someone somewhere took various options and put them together. I want this GUI, this init system, this package manager, this set of default apps. Then someone else says well I want this GUI and this init system but I want that package manager and the other set of default apps. Often they have specific use cases in mind, some specifically target gaming, some are meant for workstation use, some like TAILS are specifically for covert communication, some like Hannah Montana Linux are entirely for fucking around.

You have a selection of GUIs to choose from, some like KDE or Cinnamon are more feature rich and the vast majority of tasks can be done through a GUI settings menu, others are more minimal because some folks prefer just directly editing config files, or so that the software is smaller, lighter and faster. The choice is yours.

I might suggest, if you want to take computer tinkering to the next level, learning a little bit of Python, or maybe playing with the Godot game engine. These work on Windows as well as Linux and turn out to be handy tools.

As for whether you should use Linux? Try it out and see.

deleted by creator

Oh don’t worry. There’s not 40 different distros…there are thousands, if not hundreds of thousands of distros!

As for terminal? Linux is terminal. There is no getting around it.

Now I’m sure SOMEONE will chime in, and say “Uhm actually, I set my 90 year old grandmother up with linux, and she’s blind. It’s not hard to use.”

And they’ll claim you don’t need terminal. But the SECOND even one little thing goes wrong? The online tutorials all start the same way.

Step 1 - Open terminal.

Maybe there is a way to do the thing without terminal. Maybe technically that’s true.

But if you don’t know how, and the tutorials all resort to terminal as step 1, then functionally speaking? Linux requires word code diarrea that is terminal.

Start w Linux Mint, one of the easiest to dip your toes into the hellscape that is Linux. One of us! One of us! 😈😇

I switched to Linux mint maybe 6 months ago and it’s been great. Just a bit of adjustment for which programs I needed to get some things done. Also turns out some stuff was WAY easier to get running such as my JavaScript twitch chat bots, I didn’t even need a tutorial and I got it running in terminal. My wife also using mint at the same time I switched and she has been liking it too. Good luck and know there’s a ton of people here that can help you out.