cows_are_underrated
If money can't buy happiness, why can I buy tdrugs then?
If Turkeys dont want to be eaten, why are they made out of food?
Idk, i really disliked the UI and especially the application launcher.
Another good reason for having GUIs is, that you can learn the CLI while not being dependant on it.
Havent done that (except for games ofc)
The wiki can be rough at some times, but you are guaranteed to learn a shit ton about Linux Ehen reading it. It gives you the commands you have to copy/paste most of the time, so its not to bad.
Can't speak for you, but trouble shooting, even if you dont know what you do, is at least in my experience way easier. A terminal command does the exact same thing, no matter on which system (OK, there are differences like package manager, but you get what mean) and no matter when. On Windows you get 10 screenshots of a UI that has changed 10 times since the creation of the guide and no or a completely useless error message if something does not work. As long as you are not trying to debug big ass problems that affect core components of your system (bootloader, drives, stuff with the kernel) it is in fact quite hard to fuck up your entire system (it can happen with Updates on Arch, but this is usually quite rare). As long as you are not touching anything else except your /home directory you should not be able to break your entire system. Also if you are still scared of losing date, there are ways of creating system snapshots (backups). Backing up your home directory is enough because this means, that all the files you use daily are backed up.
Since you mentioned dependencies, here's a quick answer to what this means. There are a shit ton of programming libraries. A library has the use case, that a developer does not have to reinvent the wheel every time they want to do something. You dont want to write a complete library for GUIs every time, but instead use standardised well maintained and documented libraries. Since Programms use these they depend on the user having this library (or alternatively Programms) installed. This is called a dependency. In most cases dependency errors mean, that an expected library is not installed. In this case simply copy the name, and search "install name Linux (or your Distros)" and you are almost guaranteed to find a tutorial for installing it.
My best tip is, that you take the time to learn the basics of Linux. What is a package manager and which one does my system use, how do I navigate directories, how do I create and delete files, how do I edit files. How do I copy or move files. If you know the basics of these things you know most of the stuff you need to know to understand what you are doing. If you want to read more about a specific command you can also always refer to the man page of said command. For this simply type in man "command name" (e.G. "man cd" this gives you the basic infos about the CD command (used for navigating directorys))
I’m too lazy to troubleshoot in Wine.
I've been daily driving Linux for about 3 years now and one major tip I can give is to avoid using non Linux apps as far as possible. When I started with Linux I also tried to get windows apps running on Linux, but this, at least as far as I remember, never worked the way I wanted ans always caused more troubles. Currently I'm at a point where I dont even know when I used plain wine (I am not counting proton) the last time. It has been 2 years at least. I Am using native Linux apps for everything I do. Much less trouble shooting, no need to learn wine additionally to the command line and much less prone to breaking because of an update.
I can really suggest Mint for beginners simply because it has an UI for about everything you need somewhat regularly. This means, that you can use GUIs to get familiar and aren't forced to know your way around the terminal. Its the Ideal beginner Distros (at least from my experience)
mouse
Did you ever saw a char and thought: "Damn, 1 byte for a single char is pretty darn inefficient"? No? Well I did. So what I decided to do instead is to pack 5 chars, convert each char to a 2 digit integer and then concat those 5 2 digit ints together into one big unsigned int and boom, I saved 5 chars using only 4 instead of 5 bytes. The reason this works is, because one unsigned int is a ten digit long number and so I can save one char using 2 digits. In theory you could save 32 different chars using this technique (the first two digits of an unsigned int are 42 and if you dont want to account for a possible 0 in the beginning you end up with 32 chars). If you would decide to use all 10 digits you could save exactly 3 chars. Why should anyone do that? Idk. Is it way to much work to be useful? Yes. Was it funny? Yes.
Anyone whos interested in the code: Heres how I did it in C: https://pastebin.com/hDeHijX6
Yes I know, the code is probably bad, but I do not care. It was just a funny useless idea I had.
Finally I have a valid reason to learn about memory management. It was also hella weird when encountering it.
Its definitely a bad idea writing new code that builds up on your old code, that has not been tested properly, because you quickly have to start debugging multiple layer is code at once.
Tat's the neat part about it. Scientists dont understand it either.
How computers work is also some form of witchcraft. Even tho I understand the principles behind it, it still is literally magic that we get computers to execute stuff.