Nix falls into a category where it's incompatible enough with upstream that it requires significant packaging effort, for most libraries. This is especially so

Nix falls into a category where it's incompatible enough with upstream that it requires significant packaging effort, for most libraries. This is especially so when you have complex C or C++ libs with imperfect Cmake and Autotools build scripts or janky Makefiles. Wrapping everything for Nix becomes a significant portion of the work. Frequently it's not packaged or some version was but the upstream build system changed an you have to do it yourself. If you don't either benefit significantly from Nix's upsides (which most projects really don't), or you don't enjoy this and do it for fun, it's not a productive use for your time. If you can convince your employer to pay you to shave that yak, it's a net waste.