Disclosure -> Ron here, co-founder at flox and NixOS Board Member
It seems like the majority of names I recognize for their contributions from the Nix ecosystem from the past 8 or 9 years are working not just with, but on Nix/Nixpkgs in a professional capacity now, and the trend is continuing.
The list of companies with Nix people on staff has expanded well beyond just Nix consultancies, into cloud-centric SaaS providers, Enterprise software vendors, companies that make developer tools, etc., etc.
It's hard to imagine that with this new capacity for dedication in so many of the most long-standing, prolific, and passionate Nix contributors, that the Nix ecosystem is not poised to grow and mature by leaps and bounds!
Imo, the key will have to be in continuing to nurture an integral community in the face of all these companies now trying to grow Nix and build on top of it in their own, perhaps sometimes conflicting directions. It's a problem all collaborative projects face, and not one entirely new to Nix— there are just more resources in play now. If the Nix community can manage that during this phase, I think there can be no doubt that wonderful things are ahead.
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.
Please give us a try and offer any feedback, we want to make it easy to adopt for even non-Nixers and enterprise.