There are several tools in this space now- nix is maturing and people are realizing how useful nix can be for dev envs.
* [devenv](devenv.sh) - I am using it and loving it, but worried that the development is not moving forward
* [devbox](https://www.jetpack.io/devbox)
* [daytona](https://www.daytona.io/docs/usage/workspaces/)
* [devshell](https://github.com/numtide/devshell)
* [bob.build](bob.build) more focused on the build
I am glad that flox is pushing its development forward. Does flox have a way to run services? With `devenv` I run my database with `devenv up`.
Nix allows you to have a single lock file for all your dependencies. This is very useful for development environments. When you share a lock file via Git, then you know your colleagues will be running the same versions.
Devbox can also run services too. Both products use an awesome process runner called process-compose (https://github.com/f1bonacc1/process-compose/) which is worth checking out (it's even built with nix!)
I think the ability to run services is really what separates Devbox from other related Nix-based dev-env solutions.
Essentially taking what you get from the NixOS-specific configuration.nix options (like for example `services.mediawiki.enable = true`) and letting that be per-project, per-directory, is super useful.
+1 to devenv.
I used to use Nix natively, then switched to devbox and then devenv.
devenv is the most intuitive to use. I just wish that I could just run a command using devenv (similar to nix run) instead of having to declare it in the devenv.nix first.
I have used devbox and have been keeping an eye on other options. Haven't tried devenv yet. Any thoughts on devenv vs flox given what we're seeing here?
