We’ll have to start worrying about malware soon, exciting haha

You can use Steam’s proton even on non Steam games. It might work better than wine.

I’ve switched a few months ago mostly for gaming, and here are few tips and issues I ran into, in case you run into them too.

Not sure what distro you are using, but I’ve run mostly into issues when trying to get NVIDIA and Proton working on Fedora. Just getting the drivers to work took a few tries, and I never managed to get stuff like cutscenes to work properly.

However, I then switched to Nobara (I suppose PopOS may also work), and the experience was wastly better, with everything working out of the box (I did switch to KDE Plasma on X11, since Wayland kept freezing on me).

I’m not sure what of the many changes Nobara does helped solve my issues, but I guess it may be related to it including Proton GE by default, which I recommend getting, and a slightly streamlined installation of NVIDIA drivers.

I also recommend checking out Lutris, instead of using Wine directly. However, I never really managed to get it working, aside from WoW, so your mileage may wary. But I have most of my games on Steam, where everything is working out of the box, so it wasn’t that much of na issue. I only sometimes have to switch Proton version (by right clicking the game - properties - Force a specific version of compatibility tool).

Managing Wine directly is pretty tideous job. Use Heroic for Epic/GOG games, Bottles for everything else. Lutris is also worth trying

Copilot being back on the taskbar after removalafter taking my show desktop button (also removed) was it for me as well. Already enjoying it. Some quirks, but I think I’m going to spend way less time configuring than I am trying to unfuck windows once a week.

They are in linux forums spruiking chatgpt/copilot as well. Mods deleted my comment the last time I told them to get lost. The rampant commercialism is so frustrating. The FOSS community has done so much to empower users/developers and give everyone the tools to learn, grow and customise their systems with amazing documentation and access to source code. And it is going to be Disneyfied within a generation with the fruits of our labor locked up behind billionaire controlled subscription services in flagrant disregard of our copyright and licences. Our kids won’t know how to tie their shoelaces without paying Nadella, Altman and their shareholders for instructions.

Microsoft GitHub injects Copilot ads in their source views. It’s another Microsoft service worth abandoning.

What distro is gnome?

Ads in Windows 10 back in like 2017 were major contributing factors for me to switch back then. But then when I mentioned I got ads in Windows 10, people looked at me like I had two heads. Perhaps there was some kind of A/B testing going on, and I was the unlucky one. This followed a forced update from Windows 8 Professional to Windows 10 Home, so I lost some control over my PC in that transition, as they took Pro features away from me.

They are not seeking feedback between “I like it” and “I hate it”, they want feedback between “I tolerate it because I still feel locked in” and “that’s it I’m moving to a competitor”.

They’re not looking to see if people enjoy ads, per se – they want to see if people will tolerate them. They want to see what they can get away with. If no one complains, it becomes the standard.

It’s likely they’re looking for feedback from their shareholders, and their advertising partners rather than the users themselves. They know they’ve got a good portion of the market cornered and if it looks profitable to them; why wouldn’t they do it?

small brain move: install windows on a seperate disk to linux and then let your BIOS decide what it wants to boot, instead of relying on a unified boot loader

Small brain move: install Windows as a guest on a Linux host. Rip out so much of it’s guts it can’t show any ads and barely works at all. Declare victory over the desecrated husk of Microsoft Windows.

deleted by creator

8 had advisement tiles when they did the whole metro ui

Gonna opt-out of Windows 11.

“Works fine for me”

If you find yourself running the same set of commands over and over, throw 'em in a shell script and keybind it! It may be obvious, but good to keep in mind.

One fun one is to pipe clipboard to qrencode — it’s a simple and (nearly) universally supported way of getting a URL, etc., from a laptop/desktop to a phone.

Another great one is to take a screenshot, upload to your server, and put the URL in the paste buffer. Bonus points to put the URL in the middle click buffer and the image itself in the ctrl-v buffer.

Go slow, pick an easy distro like pop OS and take it easy.

If its for gaming, even https://nobaraproject.org/ is great as it has a lot of gaming optimisations.

Remember, Linux with a GUI is not more complicated than windows with a GUI, you have just spent your whole life learning the windows one.

Yes.

1. Back up your files.

2. When building the computer, go for generic middle of the road normal hardware. Fairly easy to do with off the shelf ATX PC hardware. Inside the case, this usually means look out for weird graphics cards or motherboards. I’ll warn you that Asrock RGB lighting doesn’t like to play with open source control software. Outside the case, pick a keyboard and mouse that don’t require (much) in the way of configuration because Razer and Corsair don’t publish their bullshitware for Linux yet.

3. Back up your files.

4. I recommend spending some time with whatever current hardware you have trying out a few distros in a virtual machine. Don’t just look around and go “ah that’s nice. ah that’s weird.” Actually use it to do your work. Even though you’re running Linux IN Windows, try to use Linux to do actual stuff.

5. Back up your files.

6. Choosing a distro. Isn’t really all that important, at least at first. Most of the meaningful differences are going to be in the Desktop Environment anyway. There’s about 18 different GUIs you can use, from weird tiling window managers the hardcore nerds tend to like, to more Windows like experiences in KDE and Cinnamon, to more Apple like experiences with Gnome and Pantheon. Try a few out in virtualbox.

7. Back up your files.

8. Learn a little bit about the terminal. A lot of people hate and fear that suggestion, but it can honestly be fun. Wait till you see what the command fortune | cowsay | lolcatdoes. Learn how to edit files, run commands, install software via the terminal, even if you don’t plan on doing it that way routinely. Mainly, so that if you ask the community for help, you’re not completely in the dark when given a terminal command to run. Which is often the case; because “click here then here then there then tell us what it says” is harder to convey than “copy paste this command into the terminal, and then copy-paste what it says.” There’s a lot of cool stuff hidden in there.

9. Back up your files.

10. Have fun!

For windows you dont need to buy it, you can activate it using microsofts own tools, its on github (dont remember its name right now.)

As for linux, i would recommend openSUSE Tumbleweed, it is fresh, and the best part about it is that whenever you update the system, it creates a snapshot, so if the update had some kind of undesired sideeffects, you can just startup the old version. (These snapshots only effect the system’s packages, your apps will keep their state iirc. My brother uses tumbleweed and he is very content with it.)

A very important one besides backing up your files is that you should more or less stop searching the web for applications to download and install. You should first try to use your package manager (read the wiki of your distribution to know which one it is and how to search for and install software with it). If you miss some applications from Windows, you could have a good chance to look for alternatives at sites like https://www.opensourcealternative.to/

Do not fear the terminal too much. I know, Windows tried to make it as dreadful as possible to use, but if you do not run sudo rm -rf / (deletes your whole filesystem), there is not much that can go awfully wrong. And you should only execute commands you understand. If something does go wrong however, it is a good thing to have a backup ready (I would recommend Pika Backup or Vorta, both based on the great CLI application borg)

For things that are not explained in the wiki of your distro, you have a pretty good chance to find a good explanation and even troubleshooting tips at the Arch Wiki (e.g. I use Void Linux and still search for most things at the Arch Wiki). It is also good to read some parts of the manual pages if you did not find enough information at the Arch Wiki (the command man is your friend) and the software’s wiki page if it exists.

If you ever find yourself in the editor vi or vim, type :q and press enter to quit until you feel the need to potentially invest a lot of time in learning vim movements to increase your editing speed and you never want to go back. Use nano, micro or a graphical app at first instead and keep using it if you are not someone who edits text a lot.

Arch is going to be the new mint. Just wait.

why?