Also sorta depends on what your aims are. There's no real reason to be afraid of Linux if you're just using it as a desktop. All the posts I see about how do I use Linux are like, uh...just use it? It's not 1999.
Steam's Proton is as transparent as it currently gets and generally handles anything reasonable. Maybe it won't play the absolute latest AAA bullshit at the highest resolution you can't even see anyway, but if you don't need to do that, it's fine.
In some cases the games running through wine run better than native windows. Setting up your wine prefix folders is super easy. If you want to complain about nix stuff running windows stuff, why don't you complain about WSL to make it equal?
and proton is basically just a preconfigured and tweaked wine with some changes to increase performance
Interesting to hear that running games through WINE yields better results than native Windows. I didn't expect that since the last time I've used WINE was in 2015.
>he doesn't know what I meant by calling gamers niggercattle
VMs just won't work well with games because of GPU hardware passthrough issues. You can't use your main video card as the card to play games through the VM. For basic things like games, using Wine and dxvk isn't that big of a risk. If you were going to use the same game installers on a primary windows install, I don't really see the difference in security issues. If you're installing torrented games that's a different case. Regarding WSL, I'm referring to the latest version of it. I brought it up because it's the closest corollary to Wine since you seemed to take issue with the idea of using your OS of choice to run software meant for other OSes.
With a bit of trickery you actually can. My first system I did Windows VMs for gaming with only had one graphics card. You can theoretically boot directly into a script that starts the VM while a very barebones Linux that e.g. does network filtering is running a level above, given that you tell the kernel to not initialize the GPU. You can also *sometimes* unbind an initalized GPU from the respective linux GPU drivers, hand it to the VM, and then later rebind it. If you only have one system you obviously have to script this so it happens automatically. Then you can get away with no reboots. The only problem is that GPUs are very complex beasts regarding their initialization and for some GPUs and Mainboard/Firmware combinations, this plain won't work.
Took you far too long, sataniaposter.
If you remember the commands bit not the flag, typing in man then the command name (so like "man nmap") will bring up the manual page for you and you can check the flags there.
Just use --help, or man <command>, I can't remember everything either after using for more than a decade.
This is amazing, I've been using Linux for 20 years and didn't know this, thank you.
The problem with these "user-friendly" distros, is that something will inevitably break which can only be fixed by interacting with the command line. Unfortunately, people who go for these distros are the same people who would never touch the command line. Coupled with the fact that these distros are niche, this means getting support for these issues is a miserable time for all parties involved. On a positive note, at least they describe what changes they are bringing to the table with this.
To me, Archinstall is like a coin toss, no matter the support (SSD, HDD). I always end up installing Endeavour because I'm too retarded to install Arch manually.
