Unfortunately, most Windows users have a long history of complaining about it and then still continuing to use it.

There’s no way around it: if you keep using abusive software, you’ll stay in an abusive relationship.

It’s for window management related hotkeys. Obviously. All about windows. With a lowercase “w”.

They want a civil war, or rather a cultural war between civilians, to detract from a class war. They want the civilians to be fighting among themselves (i.e. left vs right), rather than uniting against ruthless billionaires and grifters in the government. Having a civil war would also make some of their false claims become “true”, e.g. that cities are “war zones” and that they “need” to utilize the Insurrection Act and put the military everywhere without any remaining legal obstructions. I mean they still do it partially already, which is bad enough, but when a civil war would actually exist (like they claim), then they could also claim that what they were lying about the whole time is actually “true” (just not at all the way they said it to be, but the end result would be kind of the same: war zones inside cities) and they’d be legally allowed to be even more oppressive than they are already. It would increase their power overall. It would lead to a guaranteed dictatorship. Dictators love using “emergencies” to grab full, unrestricted power. So it’s best to never aid them while they try to construct an emergency where there is none. That exposes their lies better.

In order of priority:

1. Check for a Linux-compatible alternative
2. Try installing/running it via Bottles (a veeeery easy to use Wine frontend, hiding lots of wine complexity). Wine allows running most windows programs directly on Linux, with almost zero performance overhead.
3. Try installing/running it via winboat (basically WSL in reverse - a well-integrated Windows VM or container running on Linux so you can run pesky Windows-only programs with it) (haven’t used it myself yet)
4. Use a regular full Windows VM on Linux (likely less well integrated and more resource intensive than #3, but maybe even more compatible). Set up a shared folder between host and VM for easy file transfers.
5. Dual-boot Windows from another disk. Set up a shared folder/partition for file transfers.

Ironic how being so blatantly illegal makes these neo-nazis sort of… “illegal aliens” within a democracy based on law and constitution. They are already guilty of the things they accuse others of.

• To learn Arch, install it from scratch (without archinstall), it’ll force you to read the Wiki and learn a lot of necessary commands in the process. After the installation, just keep using it. Using a Linux distro full-time as the only installed OS is the best way to keep at it and truly learn it over time. There’s no magic bullet here. Just keep using it and solving problems or issues as you go, learning more and more stuff as you go. If you need other OSses as well, run those in a VM. I don’t recommend dual-boot setups.

• Don’t blindly copy/paste commands you don’t understand. Always try to understand them first. Some commands can be very disruptive or even destroy your configuration. If you don’t understand it or are able to adapt it so that it fits to your particular configuration or system, you can EASILY damage a configuration, or even make your system unusable. Also, some people like trolling other people and deliberately share harmful commands. Generally, test potentially destructive commands or complex commandlines before actually running them.

• Document major config changes that you do. This is useful because you’ll be able to undo certain changes or even replicate your current system configuration fast when you change distros or have to reinstall in the future. For example my current Arch-based setup is fully documented in form of an almost-directly executable shell script. It does require some interactions but very little. If I ever have to reinstall this system, or upgrade my hardware, it can be done insanely fast and it’ll have the exact same configuration. This goes from basic partitioning and encryption all the way up to dotfiles and individual program configurations.

• Don’t feel the need to learn hard/advanced tools like Vim or Emacs unless you really think you’re getting an advantage from that and aren’t hesitant to put in the time and effort to learn them. Most people don’t need to use them. They’re amazing tools but you need to be prepared to lose quite a lot of time to learn them before you can become productive with them, and this might not be a tradeoff that’s useful for every single user. You can also get away with much simpler tools, like nano (as a console-based editor) or whatever programmer’s text editor you want.
• Similarly, whether a pure WM or compositor plus assorted tools compared to a full desktop environment is worth it for you or not, is up to you. There’s no wrong or right answer here. I’ve tried out pretty much everything and these days use KDE Plasma because I like the consistency and integrations and dislike having different, inconsistent stand-alone tools for panels, menus, notifications, wallpaper, file manager and so on. But again, there’s no wrong or right answer here. Just what makes more sense for you. It’s worth learning how to be able to configure and use a minimalistic setup, for sure. So trying it out doesn’t hurt and increases your knowledge overall. In general, in the Linux world it’s good to always know enough to not be screwed once some component suddenly doesn’t work anymore. For example, a competent Linux user should be able to deal with (temporarily) not having a GUI and fixing his system via commandline.

• A minimalistic, DIY distro like Arch can be amazing to learn everything, if you want to do that at least. If you just want a working desktop system with as little effort as possible, then don’t do that. But if you intend to learn every detail, then a distro like Arch is better suited for that goal than a “bloated”, fully pre-configured distro like Mint or Ubuntu is. Because Arch is much simpler on a technical level than those are. It’s much easier to understand e.g. the relatively simple package building process on Arch than it is on Debian/Ubuntu-based distros. But this “simple” explicitly refers to technical simplicity or minimalism. Most users expect something else when they hear “something is simple”. Arch is not simple as in beginner-friendly, but it is simple in terms of technical complexity, which is why many advanced users and tinkerers like it because it doesn’t stand in their way. It also means though that you HAVE to learn many things, e.g. how to configure a firewall, because it doesn’t come with any preinstalled by default. With Arch, the admin is supposed to know about everything and configure every component himself, at least on a somewhat basic level.

• If you want to go to even more details, you could also try out a source-based distro like Gentoo or Crux, which can also be a great learning experience, but it’s even more details regarding compilations of each package, dependencies, compile-time options, etc. you have to deal with than with a minimalistic binary-package-based distro like Arch, so whether that’s useful for you or not is up to you of course.
• While we’re at it: LFS (Linux from Scratch) is not a distro per se, it’s a guide on how to build your own distribution from scratch. It’s VERY time intensive and not recommended unless you truly want to learn how to build a complete distribution from scratch, or maybe start your own distro some day which isn’t based on another existing distro.