It's Nix so you just push the new generation to the device. It's probably the easiest possible way to do device management. It's also generally like two lines of extra config to wrap a block into a container if you want to hide some of the underlying OS tools completely, which I've never tried with a full desktop environment but I'd assume should basically just work if you pass a couple things like GPU?

▲

Muromec an hour ago | parent [-]

The hard part is finding enough people working for the public sector salary who know those two extra lines and where to put them, and then making sure they are not getting bored or disillusioned enough.

▲

ndriscoll an hour ago | parent [-]

You don't need someone who knows those two lines anymore. You can just ask codex to make it so that users can't do whatever. It's highly competent at just reading the nixpkgs source, or it knows how Linux works and can write its own modules.

Nix happens to also set you up with a working build environment so if a program doesn't expose the necessary options to manage it the way you want, I bet Codex would have no trouble patching it as part of your nix config.

	▲	Muromec 24 minutes ago \| parent [-]
		You still need to have somebody half competent to ask the electric shaitan to the thing and validate the result and also demonstrate this ability during the hiring process. I'm not sure it's easier than actually finding a person who can do those two lines.