I want my terminal to just work, so all this kitty stuff is overboard for me, but good for them!

Oh I agree, I am happy with Helix and use it as my main editor already. I like that they’d rather take their time to figure out how to make plugins work well.

Uhhg, I’ve been waiting for module support for helix for forever, now. It’s a planned feature, but it’s been that way for ages now

Factorio puts game saves in ~/.factorio for some reason…

it’s pretty bad. steam for example has both
~/.steam and
~/.local/share/Steam
for some reason. I’m just happy I moved to an impermanent setup for my PC, so I don’t need to worry something I temporarily install is going to clutter my home directory with garbage

fuck you (respectfully)

No, I don’t

not really, haha

To test that SVN -> GIT works?

Oh I know it’s better, problem is I host some stuff my friend group relies on so I don’t want downtime while I figure things out. Also, it’s a bit of a pain in the ass to get NixOS set up on a VPS without native support (I’m on Hetzner and I know it’s possible, it’s just a bit of a hassle). It’s one of those projects that I’ll get to eventually, when I got time. Or so I tell myself

NixOS for most things, Debian on some servers as a docker host

of course they’re not a drop-in replacement, as the cli is getting a major redesign, but as per your source

nix shell and nix develop are still experimental, so nix-shell is sticking around despite doing the same thing

it seems like they are made to fulfill the same purpose

Interesting, didn’t know the history of the command. But that post confirms my understanding, that nix shell/develop are the new replacements for nix-shell, with nix shell for temporary package installs and nix develop for debugging and developing

Don’t copilot anything longer than a function of about 15 lines. That way you can quickly see if it made mistakes. Ensure it works, move on to the next.

And only do that for boring, repetitive work. The tough challenges and critical parts you’re (for now) better off solving yourself.

Source on the second statement? My understanding was that nix-shell is legacy for systems without flakes and nix-command enabled, and are being replaced by nix shell/run/develop

Careful, there’s three different terms in the mix here:

NixOS: an entire operating system, you don’t need this.

nix: the nix package manager. This is what you’ll need to install. look for single user install in the instructions.

home-manager: a module for nix. It’s aim is to allow declarative configuration of a users’ home configuration (and allow easier per-user install of packages on a global nix install).

If you want to go down the nix route, which I would recommend if you enjoy tinkering and having fine control over your system, you should start with installing nix. With that, you can already setup a shell that has the newest version of python available.

Going beyond that, I can link you some more resources, if you want c:

Forgejo is a free/open source code hosting site like GitHub or Gitlab. It’s a fork of Gitea, over concerns with management and commercialization. You might know it from Codeberg, which is one of the largest managed instances, but it’s really easy to host your own.

“good news honey, they heard your complaint and renamed it”

For reproducibility, nothing really beats NixOS. That’s not really what you’re asking for, as that would not involve Clonezilla.

If you’re frequently switching hardware, and want to have everything up and running, configured to your liking, in minutes, you’re gonna have fun with NixOS in the long term. But I’m not gonna sugarcoat it, it has a steep learning curve and does require you to enjoy some tinkering. Worth it, imo

Otherwise, just pick a distro that you enjoy and create a separate home partition, when it’s time to switch you do a fresh install and clone only the home partition. That’ll get you 90% of the way to have your old setup on the new device