Atemu

In this case you could make a very clear case that alien.top is infringing on copyright because those users only gave Reddit a worldwide irrevocable perpetual license to their postings, not anyone else.

In regular FHS distros, an upgrade to libxyz can be done without an update to its dependants a, b and c. The libxyz.so is updated in-place and newly run processes of a, b and c will use the new shared object code.

In Nix' model, changing a dependency in any way changes all of its dependants too. The package a that depends on libxyz 1.0.0 is treated as entirely different from the otherwise same package a that depends on libxyz 1.0.1 or libxyz 1.0.0 with a patch applied/new dependency/patch applied to the compiler/anything.

Nix encodes everything that could in any way influence a package's content into that package's "version". That's the hash in every Nix store path (i.e. /nix/store/5jlfqjgr34crcljr8r93kwg2rk5psj9a-bash-interactive-5.2-p15/bin/bash). The version number in the end is just there to inform humans of a path's contents; as far as Nix is concerned, it's just an arbitrary name string.

Therefore, any update to "core" dependencies requires a rebuild of all dependants. For very central core packages such as glibc, that means almost all packages in existence. Because those packages are "different" from the packages on your system without the update, you must download them all again and, because they have different hashes, they will be in separate paths in your Nix store.

This is what allows Nix to have parallel "installation" of any version of any package and roll back your entire config to a previous state because your entire system is treated as a "package" with the same semantics as described above.

Unless you have harsh data caps, extremely slow connections or are extremely tight on disk space, this isn't much of a concern though.
Additionally, you can always "garbage collect" old paths that are no longer referenced and Nix can deduplicate whole files that are 1:1 the same across the whole Nix store.

1. The right to be forgotten applies to PII. Comments can contain PII but usually don't.
2. The right to be forgotten applies to your private relationship with a company. Comments in public forums are, well, public. You can't force the public to forget what you said.

Well, unlike us, they're obviously living in a country which massively subsidises energy cost. But it seems they either haven't done the math properly or their measuring device is broken because even they shouldn't be paying pennies per month.

You can do the calculation for yearly cost yourself; it's not too hard. The two variables you need are energy pice and power.

Let's say you've got 30W idle power draw at 0.4€/kWh. That comes out to ~105€/year if you ran it 24/7.

You can plug in arbitrary values yourself: https://numbat.dev/?q=1+year++30W++%280.4%E2%82%AC%2FkWh%29%E2%8F%8E

Any distro that ships relatively recent libraries and kernels.

With the exception of Debian, RHEL, SLES and the like, pretty much everything.

Zen/liquorix kernels are packaged.

I use xanmod to get some more experimental things earlier but I don't think it does all that much.

Well, you can roll back with a switch too; no reboot required.

The VM protects you from accidental state modification however (i.e. programs enabled by some DE by default writing their config files everwhere) and its ephemeral nature makes a few things easier.

Me too lol

Unless you have specific needs for compute, I'd go with that.

You really ought to look into idle power though. At $0.1/kWh, 1W is about $1/year. You can extrapolate from there.
TDP doesn't matter here but the i3 is likely more efficient under load.

The shipping cost is quite extreme though. Not sure I'd pay that.

Post the journal after wakeup, not before.

Oh, curious. They are called "Antitranspirant" in German.

Latin words are almost always 1:1 the same in German and English (modulo suffix) and this appears to be derived from latin too, so I had assumed it'd be the same but, in this specific case, it's not.

As in, build a NixOS VM that's otherwise the exact same as your current system but with a different DE enabled. nixos-rebuild build-vm