Microsoft Recall is MANDATORY on Windows 11

Sorry for jumping into another thread but I think I can help with some of these

Does Linux have an equivalent of Windows Powertoys Fancyzones?

Depending on what you use it for a tiling window manager might replace it, or KDE plasma has similar functionality built in I believe

Equivalent to Eartrumpet?

I think Pulse Audio Volume Control does everything Eartrumpet does, it comes default with some distributions or you can install the package pavucontrol

If I understand what fancyzones is, I think people make plugins for gnome and kde that are like Fancyzones. There's also entire window managers that are like scriptable fancyzones. I'm talking about tiling window managers like awesomeWM and i3. They're pretty technical but some people really like them.

I've dual booted for 8 years now. It's very handy for me, but it is not without its complications - The main one being Microsoft's illegal anticompetitive behaviour by making Windows regularly overwrite the boot entries, so I have to force a legacy boot to Linux so it can recreate its own entries.

The second one being that Microsoft doesn't abide by its own official NTFS specification, and will mark drives dirty when it shouldn't, forcing Linux to be careful and mark the drive as read-only unless you force it or boot back and make Microsoft re-unmark it.

If you want a Windows-y theme, I'd point to Plasma/KDE for your desktop type. Plenty of themes around too.

Honestly I've not had an issue with hardware drivers on Linux for a long time, that issue is largely historical. Except for nvidia graphics cards, which may prove a bit finicky depending on the model. Hardware which is very recent may take a while if they don't release official linux drivers.

As for software, obviously just check if your software has a Linux binary, if it does they're generally all-distro supporting these days.

A lot of games are Linux native now, but for other Games on Steam with Proton (or the more complex effort of running software in WINE), they have appDBs that list compatibility here: https://appdb.winehq.org/ and here: https://www.protondb.com/

Dual booting is less likely to cause issues if it's 2 separate drives in my experience. When Windows has to share a drive with Linux, it can cause issues.

Lots of people do it without issues, but it can sometimes lead to issues, most likely that a windows update overwrites the bootloader and you get locked out of the Linux partition. It's worth trying if you're not sure about it, but you can also just run Linux from an external drive while testing it out, which I might recommend more, although it'll be slower to start up/run programs.

Can't help you with the theme sorry, but I have seen some in the past so I guess it's possible.

The website for each distro often has comparability information, the Arch wiki has a huge amount, which more or less applies to other distributions too.

Something has gone awry if you are using git pulls to get basic wifi. I rarely rarely ever need to do that kind of thing, usually only if I'm fucking around, never for something as essential as networking. I'm curious how you ended up going down that path. Is it a very weird NIC? what distro are you going with?

I would suggest trying a different distro. Just boot it up from the USB and see if you can find one that works with your wireless and other essentials by default without any wrangling. Some computers are just more compatible with certain distros. The wizards will tell you it's not true because the linux kernel is the same... but it's the path of least resistance.

Whichever of the following you haven't tried, go for the next in the list: Mint, Fedora, Ubuntu.

You can use a utility called Ventoy to create a bootable USB with a selection of OSes/distros so you don't have to reflash all the time or have a zillion USB sticks. I have a couple dozen linuxes + Windows on my ventoy USB. It also lets you have a persistent file storage partition on the same USB which is VERY handy to keep documentation, notes about what you did, etc.

In terms of remembering, that the way you learn command line stuff is by repetition. The stuff you use, you will eventually recall. Stuff you don't use, you don't need to recall. You just look it up when you need it. Like you don't really need to remember the commands to fix your wifi because ideally you'll only do it once. (It's worthwhile to keep a note of what works in a safe place though in case of reinstallation.) And you will probably just be following a guide from online anyway. It's good to be able to read the commands so you can tell if they are OK to run but you don't need to make them up from scratch.

There is a utility called tldr it is on my top 5 things I always, always install right away on a new system. I would never have become comfortable on the command line without it. It is a very abbreviated in-terminal help system that gives a small number (5-10) of clear, useful examples for a given command. Use use it like this: tldr ls which gives you an idea of how to use the ls command. This would be the output. You can always go to man ls for comprehensive information, but you won't need to very often. Unless you end up liking the command line as I was eventually forced to.

The other way to remember stuff is also not to remember it but to make use of the shell history. That's a bit more complicated to explain and how it works by default varies by distro. On most systems you should be able to scroll with the up arrow or possibly page up at the empty prompt. You can also usually start typing and hit [tab] for auto complete. Some obtuse systems have these disabled by default. But there are very sophisticated systems/utilities for managing and navigating the shell history. By which I mean to explain that this is actually how people who live in the command line manage to "remember" things. They don't remember them... they just have a good way to access all previous commands which serve as mnemonics.

All this to say don't get down, it's a learning curve but it's doable. I'm not particularly well suited to this kind of thing. Learning it was a real struggle at times but even I manage. You feel like you aren't getting anywhere but you know more now than you did 24 hours ago.

My suggestion is to start with the KDE version of Fedora. It supports a pretty huge amount of hardware, so odds are good that your wireless NIC (and other hardware) are likely to work right out of the box. The installation flashdrive doubles as a live working system that boots off the USB stick, so you could test out your hardware to see if it all works without actually removing Windows yet.

The KDE settings GUI is good enough that you likely won't need to worry about commandline stuff for awhile. KDE has a default layout similar to Windows. By default the "start" button is in the bottom left, and like Windows that gives you the shortcuts to settings, programs, folders, etc. Tray in the bottom right. Open programs and pinned programs on the bottom between them.

The non-KDE versions of Fedora are all the same under the hood, but have very different GUIs on top. The GNOME fans may pillory me but I've found it's a lot easier to teach Windows users how to use KDE than GNOME. KDE is also extremely stable and resource-efficient.

I was trying to pull drivers for a particular cheap wireless NIC I had lying around and gave up after like six hours of trying to understand how to pull something from git.

Is it a git repo on the internet? If so, literally just type

git clone URL-HERE

e.g. to clone the Linux kernel,

git clone https://github.com/torvalds/linux.git