[sleey]

For me, it's reproducibility and version control.

I started from using asdf [1] for managing golang, python and node. My main language is golang but often I need to run project from other language and different version especially python with packages have different version needed from pip i.e python 3.6 and python 3.8

I found about nix and it looks a good fit for my usecase because it not messing with PATH and not spawning container like docker but when I try to use it, I feel overwhelmed by it.

I use devbox now because it's easy to use but definitely will try flox. I welcome any tools that can help reduce nix complexity.

[1] https://asdf-vm.com

[tomberek]

We think the ability to hopscotch between projects and ecosystems without fear is a key value proposition of Nix-based technologies. Our approach is to address the entire user experience from installation and docs all the way to developing, building, publishing, orchestrating, and sharing your software. It is not all ready - we can't do all of it at once; we are laying down the framework.

Please give us a try and offer any feedback, we want to make it easy to adopt for even non-Nixers and enterprise.

[pikanix]

we wrote a post which may illustrate flox vs asdf https://floxdev.com/blog/asdf-migration