I think they only way in which they are similar is the way a user would add dependencies for a project. If with devbox a user populates devbox.json with package

I think they only way in which they are similar is the way a user would add dependencies for a project. If with devbox a user populates devbox.json with package names, with bob you add dependencies in list inside bob.yaml. You can find out more in a short guide[0] I wrote. But bob intends to be more than a dependency manager, it wants to be fully-fledged build system similar to Dagger, Bazel, Earthly etc with features like: * build pipelines[1]. You can define and manage your build pipelines in a familiar YAML format. You also get caching for your targets and so on. * isolated environment. We completely clear the environment for a task. I see with devbox that if I do a `printenv` or an `echo PATH` while I'm still in an active devbox shell, I see variables from my local system which can affect reproducibility. * workspaces: manage multi-repo setups in an easy manner [0] https://bob.build/docs/usage/package-management https://bob.build/docs/usage/package-management [1] https://bob.build/docs/usage/build https://bob.build/docs/usage/build