> goes down the rabbit hole of the origin of "legacyPackages" naming

> finds no good reason (yada yada nested package attributes and nix flake show whatever) that would ever allow it to be properly addressed in #nixpkgs, the one package set most people will always have to interact with

> decides to refer to upstream #nix as legacyNix because it makes just as much sense