No Stupid Questions

I have used zorin os and have not had to fiddle with it at the command prompt level any more than I have with windows installs.

You really don't need to use the terminal if you don't want to. The only reason so many people use it is because it's usually the most efficient way to get stuff done, and it's easier to show a terminal command than it is to show how to do something on each and every desktop since they all vary slightly.

When it comes to installing apps, Linux is actually not that different from how you install them on your phone. Most distros will have some kind of software center that you can use to install apps. Check here first before searching online. Most apps are NOT downloaded using your web browser.

Stick with a distro that's been around forever. Newer distros have a lot of buzz, but they lack support and you'll eventually come across a problem that you won't know how to solve.

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

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

btw, if you decide you want to use linux, build the PC for it. don't build it now and then decide the OS. a lot of people have issues because they use linux with uncommon hardware meant for other OSes.

however, maybe try a liveUSB first. you can get used to it and decide if its for you.

You won't do it.

I DO NOT want to be forced to use a terminal

I challenge you to fresh install any version of Windows and never use CMD Prompt, Powershell, or Regedit for any reason, ever.

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.

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.

and it seems like the only people that use Linux are HEAVILY experienced with those things I just listed… HOWEVER… I’m not.

Nah. Or at least, it should just work if you boot from your USB.

Just try it.

I actually don't know shit about programming, but I learned to use Linux just by reading manuals, wiki and forums for specific problems. Like everything you will have to put in effort to learn something new, and there are plenty of sources which explains the linux way for beginners. if you have the time for it, it is really fun to read wiki because most times you will discover cool things you could do with linux you didn't even knew you wanted. I did break my linux many times as i was learning to use it but everytime i broke it i learned something new so if you break your linux just take it as a learning experience.

If you have to ask randos on the web, no.

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

You haven't started your requirements. If it's only tinkering for fun and cannot handle editing text files, then best avoid the Linux world.

Based on your post, you sound like you don't want to use it but feel obligated to. You aren't obligated to use it. I purchased a Linux machine and daily drive it for everything I can. It was a little rough to start but I have picked up on it pretty quick. You will deal with weird quirks from time to time. Most issues I run into are common enough that a quick Google search will fix me up or get me pointed in the right direction. If you want to try Linux, just know that there is a learning curve and be patient with it. As far as Distros, start with a "Just Works" Distro. I recommend Linux Mint or Pop_OS. They work well out of the box while having plenty of room for tinkering. I'm by no means a programmer or Developer but Linux is still accessible without a deep arcane knowledge base of CS information to draw from. Regardless if you use Linux or not, I hope you enjoy your new PC!

Let me put it this way - I know nothing about programing and was also scared of all the terminal talk and stuff. And I can vouch for Linux Mint.

You know how you sometimes havento use command line in Windows for some issues? That's pretty much comparable to terminal usage from my layman perspective. I installed Linux Mint on a separate drive and only booted to Windows once or twice since then - it's been couple of months now

You are in your 20s so you probably won't have a referrence point but to me it felt like going back to simpler, older Windows version

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 (tm).

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.

I didn’t read the whole post.

Let me put it this way, decide if you want to fuck around for hours to get everything working as you want it (and yes, that will most probably involve the terminal or trusting random people's suggestions) or if you prefer to keep using something you know just works.