devbox

I have noticed that the Jetify Devbox is showing a very old index, from 10 months ago (e.g. curl -sS "https://search.devbox.sh/v2/resolve?name=curl&version=8.22.0" returns 404 since the last known version is 8.17). Since the GitHub issue (https://github.com/jetify-com/devbox/issues/3016) is not being responded to, and the Discord invitation doesn't work (another issue without feedback: https://github.com/jetify-com/devbox/issues/2999), I am asking myself if maybe the project is not actively maintained anymore?

I thought you are talking about https://github.com/jetify-com/devbox :D

FYI there's a well-starred, corporate-backed, similar functionality, Nix-based product with the same name: https://github.com/jetify-com/devbox https://www.jetify.com/devbox

I've used Devbox by Jetify for two years. Never looked back. https://github.com/jetify-com/devbox

I read the project's Readme and all I'm left with is "why?". I use Devbox[1] and get access to the entire Nix ecosystem, done. [1] https://github.com/jetify-com/devbox

There's also [devbox](https://github.com/jetify-com/devbox). Tried a lot of them, and after a while I found the nix the package manager on non NixOS requires too many workarounds. Things don't just work. For example, installing alacritty requires an OpenGL wrapper. Neovim can't find libraries to build some plugins. Basically, anything GUI had issues. In the end, `cargo install`, `go install` and download a release archive from github are simpler to script for most of the tools I use.

How does Flox compare to Devbox? https://github.com/jetpack-io/devbox

I've spent the last year managing all my packages with Devbox (https://github.com/jetpack-io/devbox). Local dev, cloud dev, CI, production – all with the same config file. Fingers crossed my talk submission for PackagingCon gets accepted. It'd be awesome to share this new way of working with a wider audience.

> Now to figure out what a "flake" is… Flake is a worthwhile addition to Nix that is worth learning. But like anything Nixian, it's not straightforward. Have you checked out any of the tools that aim to simplify Nix experience? We built Devbox (https://github.com/jetpack-io/devbox) with this in mind.

Local first, cloud optional is the only way (IMHO) we're going to get people off their local laptop development setups. We need to support local dev environments first, with the exact same config a developer can then move to the cloud. See https://github.com/jetpack-io/devbox for how this can be achieved and https://www.mikenikles.com/blog/dev-environments-in-the-clou... for my thoughts after 3 years of working in this space.

If you like the properties of Nix, but find it confusing, you should check out Devbox! It simplifies the process of creating Nix-powered dev environments: https://github.com/jetpack-io/devbox

ah, yeah, we have a cheeky workaround for this in Devbox ;-) https://github.com/jetpack-io/devbox/blob/main/internal/impl...

Nix is a great option for reproducible dev environments. However, the Nix language is pretty complex, which can make adoption and buy in tough. One solution that my company is working on is Devbox, which tries to provide the usability of tools like Yarn or Brew with the reproducibility of Nix. You can check us out at https://github.com/jetpack-io/devbox

You might be interested in Devbox (http://jetpack.io/devbox)! We built Devbox because we were frustrated with our Docker based dev environments, and our goal is to provide the power of Nix with a more accessible interface (similar to yarn or other package managers). We're open source and rapidly adding features, you can check us out on Github at https://github.com/jetpack-io/devbox