Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> ... why it isn't ready for prime time yet ...

I think for a professional / team setting, its learning curve is sufficiently steep enough that it'd be risky to adopt with only one or two team members familiar with Nix.

Writing Nix code for your own packages varies in difficulty from 'trivial' to 'demands you know a lot about Nix, the compiler, Linux, and your software package'.

> What is a real world use case where Nix isn't overkill? ...

I'd rephrase this as "nix is 2nd best at everything".

So, yeah.. to setup tools you could use asdf; provision a system you could use ansible; to build an image you could use packer; etc. -- But, if you've already paid the (steep) learning curve for nix, it's going to be a better choice when doing anything that involves packages.

I'd put emphasis on "declarative" more than I'd emphasise "reproducible", though.

> It feels like the Kubernetes of package management/build if you will complexity wise.

This is an apt comparison.

However, there Kubernetes alternatives are often simpler with 80% of the power.

With Nix, there's nothing that's simpler that handles as many use cases.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: