fesc

The multi-user install isn't very intrusive I think. Would definitely go this way if possible.

At work we switched from a big list in our wiki + some shell scripts + brew to a smaller list in our wiki + nix-darwin and I really like the result.

Everything which isn't in nixpkgs I prefer to install manually (such as IDEs, VirtualBox, Docker, ...) because the built-in installer/updater is more robust than brew and most of the time brew just invokes the native installer anyways.

If something is in nixpkgs though you can be pretty certain that it will work at your colleagues machine just like it does on yours which is great.

Yeah, the you would just do a quick `nix-shell -p <package>` and of you go.

Much quicker than a `brew install` for me.

At least for me the thing is I never "just" want to install a package (for myself).

If its a personal PC I probably also want the package if I ever were to reinstall the PC. => Use NixOS and add it to the configuration.

If its for work I probably want my colleagues to have the package as well => nix-shell.

Once I started using Nix just quickly installing a package felt really hacky to me, just like a dirty workaround.

I just hate when some project's README.md says: "Yeah, just do apt-get install <long list of packages> and you are good to go".

The chance that this works successfully is about 0.

EDIT: typo

Not incorrect but discouraged.

- If you want the package just for now and probably not later use `nix-shell -p`

- If you always need the package for a specific project add it to `shell.nix` (`flake.nix`) of that project.

- If you need the package globally use home-manager, nix-darwin, NixOS

> as they include their own OS

That is not required.

What kind of security problems are you talking about?

I'm using it for some internal systems at work and I feel there's nothing like it.

NixOS gives a level of reproducability that other tools like Ansible won't ever be able to give you.

This reproducability means it makes debugging problems very easy: E.g. uncomment a line in the config and see if something starts working again. You can nearly undo everything cleanly in NixOS by just doing that.

On the other hand the learning curve really is pretty steep. Took me about half a year to get to a point where I understood it enough to be able to debug most errors.

I completely agree with your second paragraph but the last sentence seems like you don't know what people mean when they say they hate NullPointerExceptions.

They don't mean that you just silently ignore the null value, they mean that they would prefer to use a language that has proper optional types.

You're missing the point.

If an Android user is travelling with an AirTag other people (e.g. a colleague) with iPhones will "send the signal to the motherships" but they won't get the alert as they most likely won't be in proximity of the AirTag long enough to trigger it.

If I tap on an issue to view its details and then go back to the results I am always at the first page and not where I left off.

Could you elaborate on that a little bit? This sounds interesting and I'm not sure where to start researching about this.