rutrum

If you really hate linux, I think the transition will be extra difficult and you might not end up switching away.

If you use conda, I suggest using pixi as a project manager. It has lock files which will fix dependencies, and it can activate your enviroments with scripts and variables defined in your pyproject.toml. It has been so much better than using conda directly: https://pixi.sh/

Theres three things at play here: nix, nixpkgs, and NixOS.

Nix is a programming language. Its designed as its primary purpose to configure, build, and install software.

Nixpkgs is a collections of mamy bundles of premade nix code called derivations. These derivations include the build instructions for applications and the configuration options for those applications. This part is most equivalent to a package repository, but it does not contain prebuilt packages. It only contains the instructions for building it.

Nix has a wide variety of tools for managing these derivations. This includes downloading derivations from nixpkgs and building them locally on your machine (or finding prebuilt packages from a cache). Nix shell is one of those tools that downloads a package temporarily, and makes it available in your shell. You wouldnt use nix shell for installing things permanently.

The OS built with nix as the primary package manager is NixOS. It allows you to define your entire system state as a derivation: your systemd units, installed packages, user configuration, graphical environment, etc.

The best part of NixOS is that it takes the OS and represents the state of the computer as a single repository of code. If you look up someones nixos configuration on GitHub, you'll see a single collection of files (filled with derivations!) that completely and totally define the state of the system.

Lollypop looks awesome. Thanks for recommending. Welcome back to NixOS

Looking forward to TYPE_CHECKING without import typing.

I use borg backup. It, and another tool called restic, are meant for creating encrypted backups. Further, it can create backups regularly and only backup differences. This means you could take a daily backup without making new copies of your entire library. They also allow you to, as part of compressing and encrypting, make a backup to a remote machine over ssh. I think you should start with either of those.

One provider thats built for being a cloud backup is borgbase. It can be a location you backup a borg (or restic I think) repository. There are others that are made to be easily accessed with these backup tools.

Lastly, I'll mention that borg handles making a backup, but doesn't handle the scheduling. Borgmatic is another tool that, given a yml configuration file, will perform the borgbackup commands on a schedule with the defined arguments. You could also use something like systemd/cron to run a schedule.

Personally, I use borgbackup configured in NixOS (which makes the systemd units for making daily backups) and I back up to a different computer in my house and to borgbase. I have 3 copies, 1 cloud and 2 in my home.

There are many devices for making single or double cups of coffee. I think the aeropress and v60 are great options.

Deep cut

Does anyone here use kellnr? Sounds really awesome to have, but I dont write any closed source rust, and just publish to crates.io.

Only a web dev could be fooled into being a gopher

I like butter+jelly and butter+peanut butter on my biscuits, but never both. I also like making sausage gravy with cream cheese instead of flour most of the time. Looks yummy anyway, even the eggs right on top ;)

I enjoy beyond all reason, which is the only flatpak I have in my config XD