KubeRoot

Dual booting is problematic, as mentioned you’re messing with your partitions and could mess up your windows partition, but also windows can, unprompted, mess up your Linux bootloader. As long as you’re careful with partitions and know how to fix your bootloader from a live image, there’s no real issue, but it’s worth keeping in mind.

By the way, I recommend rEFInd for the bootloader when dual booting, it doesn’t require configuration and will detect bootable systems automatically.

A VM sounds like a good idea to try a few things out, but do keep in mind performance can suffer, and you might especially run into issues with things like GPU virtualization. If you want to properly verify if things work and work well enough, you’ll want to test them from a live system.

As a final note, you can give your VM access to your SSD/HDD - if you set that up properly, you can install and boot your Linux install inside a VM, and later switch to booting it natively. You still have the risk of messing up your partitions in that case, but it can be nice so you can look things up on your host system while setting up Linux in a VM.

I think the main pain would be manually aligning the frames on every line with every change, occasionally having to extend the width and updating every line of code to match it

Git exposes a lot of internals through odd commands, so I suspect you could manage synchronization by sending changes over email or something.

Bonus fun fact: there’s a git bundle command that “dumps” the repository into a single file, that can be interacted with as a remote. So if you’re ever working with a local repository and want to put it on a server over ssh or something like that, you can just create a bundle, scp it over, and clone from that on the server.

Fundamentally, the repository you have on GitHub is the same thing as the repository you have on your computer when you clone it. Pulling and pushing are shorthands for synchronizing commits between the two repositories, but you could also synchronize them directly with somebody else who cloned the repository. As somebody mentioned, you can also just host the same repository on two servers, and push to both of them.

The issue is that git doesn’t include convenient features like issues, pull requests, CI, wikis, etc., and by extensions, those aren’t included in your local repository, so if GitHub takes them down, you don’t have a copy.

An extra fun fact is that git can be considered a blockchain. It’s a distributed ledger of immutable commits, each one representing a change in state relative to the previous one. Everybody who clones a repository gets a copy of its entire history and fast forwards through the changes to calculate the current state.

Eh, I’ve previously fucked up my bootloader, all you need to do to fix it is boot up a live image, mount your root partition, arch-chroot into it, then follow normal steps to set the bootloader back up - it’s not scary if you know what you’re doing, just time-consuming

I’m tempted, though I use rEFInd not grub, but fixing any damage should be easy with a live image handy…

I might be wrong, but I think that actually wouldn’t do anything, because grub is installed by the tooling from the package, not the package itself?

I do want to clarify: it’s not Linux itself, but specific distributions (or rather their package managers). As far as I know, Arch’s pacman would do nothing to stop me 🥰

At some point, I think people will pray for nuclear war, because life will be so miserable.

Reminds me of Roll out the Fallout by The Chalkeaters

Getting a bit ahead of yourself, we’re only on 3070 so far!

Funnily enough, I’ve seen opinions that Windows has awful HDR handling and Plasma is much better, but I don’t have a proper HDR display to check. I’ve also had some success with VR, though I haven’t played much on Linux. That said, support from software for those things for Linux is still widely lacking, so it’s not much consolation.

So like telling people to ride a bike, or use public transport, with the obstacle being that the city is built with car-friendly infrastructure that’s hostile to pedestrians and bikes? Yeah, sounds like an analogy alright ;D

I imagine some instances might ban users for upvoting certain things, you know…

No, the point is… It might be obvious you’re using that specific browser, since it’d be very niche, and combined with something like your IP and maybe something like browsing patterns that might be enough to identify you.

It doesn’t matter how much fingerprinting information you hide if you replace it with new information that’s just as useful.

I don’t know from experience, but I’ve seen mentions of it taking serious work, including dealing with CP content being uploaded (federated?) to random instances…

Not a meme, but relevant https://youtu.be/-ZNoNHk8lbQ

I think it might still be dropping executables in .config, stuff like the JDK or even its own software versions

The drama where he ended up ripping into the maintainer who’s trying to block rust code from being added? :P

Context doesn’t matter because ultimately it’s directed at somebody and telling them to kill themselves. I don’t think he actually wanted that to happen, but he said it. It doesn’t make him a villain, but it’s something that shouldn’t happen.

In general, almost everything you install with pacman will update when you do pacman -Syu (and restart, in case of kernel updates). The way packages work, all the files needed for a piece of software to function are installed from a package, and when you install a newer version, it removes all the files from the old version and puts in new ones. (Caveats apply to configuration files you can modify - those don’t get replaced if you do)

So after you update some software through pacman, it should be in an entirely clean state, just like if you just installed it. The main caveats apply to things like flatpak, which manage its own packages, and software like Steam and Discord, which have an additional auto-updater for some things that’s storing files separately.