It’s one week until Bluefin goes beta and we’ve been putting a bunch of effort into the developer workflow. Please feel free to participate, even if you don’t use Bluefin!
We basically have four piles:
- devcontainers with vscode with or without devpod
- Distrobox/Toolbox
- Homebrew
- Devbox/Fleek for nix
We just had a discussion on chat about what tools people prefer to use, so I’d thought I’d start a quick poll with a little template so we can all document our preferred workflow. Then we can just add them to the docs as a little collection of ideas for people to start from.
Because I am now firmly convinced that the default “use toolbox for development” isn’t working for people, and each combination of the things we’re talking about offer so much more, especially considering you can always use toolbox/distrobox. Let’s have some fun!!! 
(Copy and paste my format so we can all match)
Mission: I were to convince a user to try bluefin-dx I would recommend:
Tools in order of preference (why and/or why not):
Devcontainers for Development
Open spec, multiple IDE support, great tooling. Devpod supports it which gives us great multicloud support with awesome local dev too. This is declarative, is in productions at a huge scale and every distro people care about have well maintained containers.
homebrew
CLI and random tools. htop, every neofetch clone, all the stuff people want but aren’t easy to do if they come from other linuxes. And it’s nice to have a seperation from your terminal tools and your work requirements, which are already specced out in devcontainers. Every cool new tool you read about is already in there because so many MacOS desktop users that are linux admins, this really takes advantage of that.
distrobox/toolbox
You’ll still use this a ton, I’m still convinced we need a new terminal to really unlock this workflow but it’s still awesome.
Devbox/Fleek
For the nix nerds, not my thing. I’m a fan of Determinate Systems and jetpack.io and they’re all awesome people.