I see two possible reasons for your situation. One is that the company is turning to contractors to fill in gaps in their knowledge/experience, which is why everyone else has no clue how to tackle these tasks and why they get assigned the easy ones.

The other possibility is that the senior devs are gaming the metrics, letting the employees knock out easy tasks while the contractor is stuck with untangling the knots of the more intractable tasks.

Look into installing AppArmor instead of SELinux. AppArmor is easier to configure, and SELinux is not officially supported on Arch.

More specifically, it’s a lobbying group.

USB plugs are actually a great at-home demonstration of quantum mechanics. The USB plug exists in a quantum superposition of alignment - being simultaneously correctly aligned and not aligned until being inserted. Once insertion is attempted, the wave function collapses to a random alignment.

There’s no downside to writing the guards afaik, but I’m more of a c programmer. It’s been a while since I did much c++, so I’m not up on modern conventions. But dealing with legacy code adhering to older conventions often comes with the territory with c and c++, so it’s something to keep in mind.

You can generally rely on a header file doing its own check to prevent being included twice. If a header doesn’t do that, it’s either wrong or doing something fucky. It is merely a convention, but it’s so widespread that you really don’t need to worry about it.

You are mixing up some terms, so I want to help clarify. When you #include a header file, you aren’t importing a library. You are telling the compiler to insert the contents of that header file into your source where the #include line is. A library is something different. It is an already-compiled binary file. A library should also come with a header file to tell you what functions and classes are present in the library, but that header isn’t itself the library.

It may seem annoying to have to repeat yourself between headers and source, but it’s honestly something you get used to.

My spouse says that they LIKE the way I smell.

Did you know Kids in the Hall made a sketch about you?

What? Linux does use git for version control.

Reminds me of

Plus, jokingly using fash shit tends to attract people who aren’t really joking but want plausible deniability.

To be clear, dmesg -w should be run before you do anything to cause the crash. It will continuously print kernel output until you press ctrl+c or the kernel crashes.

In my experience, a crashing kernel will usually print something before going unresponsive but before it can flush the log to disk.

If you have another pc, ssh from it to the problem machine and run sudo dmesg -w. That should show kernel messages as they are generated and won’t rely on them being written to disk.

There will be things to learn and unlearn, but modern Linux distros are fairly smooth sailing for basic tasks if your hardware supports Linux well. Laptop support is a little more spotty, where there may be issues with suspend, or the Wi-Fi needing 3rd party drivers, but desktops will probably work without much fuss (and there are plenty of laptops with no issues).

Gaming has been made much easier thanks to wine and proton, particularly valve’s contributions. For steam games, many of them will just work out of the box or after ticking a checkbox. ProtonDB is invaluable for quickly seeing how well a game will run on Linux.

But as you’ll see as you read some of the reports on ProtonDB, there will likely be a more troubleshooting than you’re used to on windows. As long as you know how to Google the name of your distro + the problem you’re seeing, you’ll usually find a solution.

You don’t need to be a terminal master to use Linux nowadays. But most things are easier to explain with terminal commands than with step by step gui instructions, so many guides online will have you use the terminal to some degree.

Honestly, the best advice I can give is just try it. If you have a spare drive (internal or usb), just go ahead and install Linux to it. If you want to be extra sure you won’t do anything to your existing windows install, remove the windows drive first (or disable it in bios). Then play around with things and see how it feels.

Well, it depends on your perspective. Copyleft licenses restrict downstream developers in order to protect the rights of downstream users.

Account passwords have never had the purpose of protecting data from physical access - on Linux or any other operating system that I’m aware of. Physical access means an attacker can pull your drive and plug it into their computer, and no operating system can do anything to block access in that scenario, because the os on disk is not running.

You need disk encryption to protect your data. The trade off is that if you forget the encryption password, your data is unrecoverable by you. But that’s what password managers are for (or just writing it down and putting it in a safe).

Depending on what games you played, mac was a decent alternative for gaming. Blizzard treated mac as a first class platform for many years, indie games using multi platform engines often targeted it, and porting studios like aspyr would bring over a few big titles here and there.

Linux was in a similar boat before proton really opened things up, but with even less support than mac from game devs.

Yeah, dropping 32-bit made me start considering leaving the platform, despite being a happy Mac gamer for over a decade. The switch to arm finally made me move to back to pc. I expect Apple will drop their x86 compatibility layer after a few years like they did after the ppc to x86 transition.

Steam and lutris has made linux a great gaming platform for me.