Yeah as great nix is… documentation is hard. But after a year or two you start knowing enough to know where stuff is declared.
But in that case it seems more like they copied without reading the config, and they are just not organized in their configs
… which is fair enough, as I don’t have a layout I like either… it’s always time to refactor. Even my latest machine needs a refactor, and it’s not even been a month…
Yeah, I mean, my colleague pretty much just used this other person’s config like a distro. It comes with programs you didn’t install and defaults you didn’t choose, but if it works, then no need to change it, I guess.
That’s hilarious. I know some people use other people’s config as a starting point or template, or just a reference; I can only imagine how wild it would be to learn a bunch of people used my config like a distro
Yeah as great nix is… documentation is hard. But after a year or two you start knowing enough to know where stuff is declared.
But in that case it seems more like they copied without reading the config, and they are just not organized in their configs
… which is fair enough, as I don’t have a layout I like either… it’s always time to refactor. Even my latest machine needs a refactor, and it’s not even been a month…
Yeah, I mean, my colleague pretty much just used this other person’s config like a distro. It comes with programs you didn’t install and defaults you didn’t choose, but if it works, then no need to change it, I guess.
That’s hilarious. I know some people use other people’s config as a starting point or template, or just a reference; I can only imagine how wild it would be to learn a bunch of people used my config like a distro
Technically every nix config is a distro. Pull and run*!
*put the correct hardware configuration, system state, cpu type and remove the encrypted secrets before uses