Linux

Yeah. I probably should have been more clear about that.

I don't understand the issue here. Does that mean I can kill my BIOS bootloader somehow? Or the display driver? And how would screwing up drivers on one SSD with Linux affect my other SSD with Windows? Sorry if these are dumb questions, I'm just trying to get my head around as much of this as I can.

A live USB would let you play around in a desktop environment for a bit to see if you like it before jumping in the deep end with it. But if you've already tried out KDE plasma and know you'll like it, then you're probably fine. I agree that you won't become familiar with a full distro without data persistence and repeated use.

Maybe at least live boot gnome if you haven't tried that one yet. Gnome and KDE are the most fully featured desktop environments, so they're natural choices for users coming from win/mac.

Yeah, you can always install another, but if you are going to do that every day or two before settling on one, maybe consider installing virtual box and trying out the distros like that first. Of course, if you're in a VM, it can be a challenge to get proper hardware acceleration if you're going to try out gaming.

At the end of the day, I think dual booting is a good idea, as long as you only use windows when it's your only option. That's what I do. It's easy enough to reboot if I need to play a game or use a windows specific app. More consistent than dealing with QEMU or something.

Oh, my misunderstanding, I thought you wanted to dual boot OpenSuse and KDE Plasma. Dual booting Windows 10 and one of those makes way more sense, especially if you have niche university software that was probably written 20 years ago for Windows XP service pack 2, is already barely compatible with Windows 10, and almost certainly never had a linux version. You definitely don’t want to gamble on abandoning Windows completely until after you graduate.

And yes, once you get comfortable installing a distro, it gets pretty easy to just install a new one.

You can indeed always install another distro. You can also run many distros in "live cd" mode, just boot from the install media and choose the live option without installing. It's actually a great way to see if a distro will play nice with your hardware and LAN and peripherals out of the box.

I keep hearing good things about both of those. They're the first two distros on my list to try out after OpenSUSE.

It’s easy to forget the steps you took to do something on your computer, especially several months later when you’re trying to upgrade. Sometimes when you try several different ways of solving a problem, it’s easy to forget which method was successful the next day!

History with Fish makes this easy

you wont be able to use ms office, so either use alternatives or the web version(or through a vm)
for most software you want to use the packages provided by your distribution maintainers, as that removes the need to deal with conflicts, often provides some sane defaults and makes it so that for the most part you only have to trust the team of maintainers rather than every software developer in the world.
also you wont be able to play valo and some other shooters, though eac and battleye are both supported and besides native and wine/proton support u can play most games on kvm passthrough vms with little performance loss

No worries, it's a lot of details to take in having never been part of it. The thing about the open source world is that there's no central authority figure to say "this is what we're doing, stop doing that other stuff". So instead, anyone can do anything without consideration for what else is out there.

So yeah, package managers are one way to install software, there are many different package managers out there, and virtually every distro ships with the one that fits their design philosophy best. Package managers tend to point to a set of repositories (servers full of packages) that are managed by your distro maintainers. Depending on the package manager, a "package" may be a pre-built binary, or it might just reference some source code and scripts to build it. Either way, the purpose is to make it easy to install packages that someone has theoretically taken a look at and given a thumbs up to, indicating that it should work on your distro, in combination with the other packages in the repo (theoretically).

But not every single binary out there has been inspected by every distro maintainer. There are often licenses that prevent them from re-hosting proprietary binaries on their servers, and even if the license is permissive, it's not uncommon for maintainers to disallow packages that aren't open source. So ex. Discord has a Linux binary you can download and use, but it's not commonly served from a package manager.

"Wine Is Not an Emulator" because it's not emulating hardware. At the end of the day, windows and Linux are both running on your x86-64 CPU. In theory you should be able to point the Program Counter at the first instruction in a binary, and the CPU won't care which OS it's running on....until it tries to make a system call, or jump to a windows-specific dll. Wine basically tries to create an environment so that when a binary tries to do something that is normally only offered by the windows runtimes, there is code loaded to do what it expects.

These days, I recommend trying out Bottles to run arbitrary windows apps. It's user-friendly, you create "containers" for specific windows apps, and it uses wine under the hood.

And then you have things like "flatpack" which are kind of like package managers where the package is a bottle/container, but the software it runs could be for any platform (Linux or windows). There are pros and cons to this (pros usually being stability, cons usually relating to the size of the containers on disk).

There are people who are adamantly for/against each thing, which is why distros exist in the first place. That's just how the open source world works. I recommend finding something that works for you and not feeling obligated to worry about the 10 other ways people have gotten it working.

Good luck!

None of the comments here explain how WINE works, so allow me to elaborate a bit.

WINE is like a translator or a compatibility layer. When a Windows program tries to perform a function that would normally require Windows, WINE steps in and translates that request into something the Linux system can understand and process.

As you may know, Windows programs work by making API calls (eg using Win32 APIs) to operate and perform basic tasks. WINE takes these API calls and translates them to their Linux equivalents (POSIX calls, to be specific, which means Wine can run on several Unix-like systems). This way, when a program asks to say, open a file, or display something on the screen, WINE converts these requests into a form that Linux can execute.

WINE's approach is about providing compatibility for user-level applications rather than replicating the internal workings of the Windows kernel. It includes various libraries and components that mimic the behavior of those in Windows. This helps in executing the Windows applications as if they are running in their native environment.

• The core of it is NTDLL. NTDLL.dll is a core Windows library that provides low-level system functions to interact with the Windows NT kernel. In WINE, ntdll.dll is adapted to work with the Linux kernel instead.

• Then you have the Win32 API libraries, providing the basic APIs that Windows applications use for functions like window management, text rendering, and system calls. Examples include user32.dll (for user-interface functions), gdi32.dll (for graphics device interface functions), and kernel32.dll (for basic system functions).

• Shell32.dll for handling Windows Shell API functions related to file operations and the user interface.

• DirectX Support, for running games and multimedia applications. WINE implements parts of DirectX, like Direct3D for 3D graphics, DirectDraw for 2D graphics, and DirectSound for sound processing. Note that WINE's implementation converse Direct3D calls to OpenGL, whereas there are community projects like DXVK and VKD3D which translates these calls to Vulkan.

• Finally there's a Registry Implementation, so that applications that need to read or write to the registry can function correctly.

Of course, there's a LOT more to it, the above is just an example of some key components. Basically Wine has reimplemented (coded from scratch) various libraries and executables that, on the outside, look like standard Windows dlls/exes, but internally they use POSIX APIs to talk to the Linux kernel and other POSIX components. This, along with the Syscall translations, bridges the gap between Windows programs and Linux.

Now naturally, this is neither a perfect, nor a complete implementation of Windows APIs; plus there are some things which Wine will never implement (such as ntoskrnl.exe), so not every program will work as expected - so check out the Wine AppDB for compatibility reports with various Windows apps.

I've been using openSUSE for a while now and haven't come across any software that was not available for it. Doesn't mean it doesn't exist, but I wouldn't worry about it. It's a pretty good OS in my opinion.

openSUSE is rather small, not everything is packaged for it. Arch is the best in terms of software availability, thanks to the AUR.

The only distro that even comes close is NixOS, but I really wouldn't recommend it for beginners. You can explore it in a VM though or maybe at some point actually try it out. It's very very different than other distros though.