Add comparison chart to documentation covering similar projects

[alerque]

I don't know if I've only started noticing or if the tooling in this space has started to proliferate, but it isn't clear to me which tool to reach for an which project. Recently I've run across nixpacks, riff, devbox, and devshell — all of which seem to try and simplify building and-or using projects by abstracting some combination of nix and docker features. There are likely others I'm unaware of too. Of course this is in addition to lower level tooling like docker and nix shell and nix develop which can be used directly as well.

I think it would be useful for at least one of these projects to maintain a comparison chart that helps flesh out which projects cover which ground and what the respective pros and cons of each approach is to help people make informed choices about tooling.

c.f. same issue on nixpacks, riff, and devshell.

[hugosenari]

same issue on devenv

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will be closed in 5 days.

[alerque]

Not stale.

And attention project maintainers: this issue bot is super obnoxious and a huge turn off to contributors and users. Please shut it off. An issue would only be stale if a maintainer had responded and asked for more info and it was never given. This bot not only doesn't detect an unanswered question but doesn't check maintainer involvement. Seeing this bot pop up basically just means the project is dead because no maintainers are actually triaging issues and they want them to go away before they are triaged.

[Lagoja]

Hey @alerque, thanks for the feedback.

I've disabled the stale bot. Our intention was not to disregard issues, but to help us better triage issues that have been left un addressed for too long. I think the bot needs some more fine tuning to accomplish that goal (your suggestion to check maintainer involvement is a good one).

For this issue -- we think a comparison chart is a good idea, and we have it in our backlog for our documentation or for a future blog post.