Devbox vs frum

Devbox is an open-source command-line tool for creating isolated development shells from declared package lists. A project’s devbox.json can define packages, scripts, services, and environment configuration, drawing on a searchable Nix-powered catalog with over 400,000 versions of 80,000 packages. One definition can produce a local shell, a VS Code devcontainer, a Dockerfile, or a remote cloud development environment. Devbox can orchestrate project services with process-compose without Docker; Docker is needed only for container creation. The GitHub Action installs Devbox and can cache the Nix store in workflows, and documented integrations include direnv and a Visual Studio Code extension. Installation guidance lists Linux, macOS, and Windows through WSL2, and Devbox requires the Nix Package Manager. Jetify offers cloud and secrets services alongside the tool.

frum is a free Ruby version manager written in Rust. It can install and uninstall Ruby versions, list available or installed versions, and select a global or local version. It also works with .ruby-version files, so projects can specify which Ruby version frum should use. The project describes its implementation as pure Rust and says it does not use ruby-build. Installation methods listed include Homebrew or Linuxbrew, Arch Linux packages, Cargo, and release binaries. The README provides setup instructions for Bash, Zsh, and Fish and lists shell auto-completion. Ruby installation accepts configuration options such as an OpenSSL directory and jemalloc allocator selection. The README reports a benchmark in which evaluating frum init ran about six times faster than evaluating rbenv init. The project is MIT licensed and welcomes contributions, issues, and pull requests. Linux and macOS are listed as supported platforms; Windows is mentioned in the project’s goals. Its latest listed release is v0.1.2.