Show HN: Devbox – Containers for better dev environments
41–50 of 65 posts
Re: Show HN: Devbox – Containers for better dev environments
#42Why should we use yours? What does it do better or differently?
Re: Show HN: Devbox – Containers for better dev environments
#43So this reinvents devcontainers? https://containers.dev Why should we use yours? What does it do better or differently?
Re: Show HN: Devbox – Containers for better dev environments
#44So this reinvents devcontainers? https://containers.dev Why should we use yours? What does it do better or differently?
While this is true, this project seems to wrap it up in a CLI package for starting and stopping projects. Whereas starting devcontainers, at least as far as I have seen, is always done via VSCode or IDE, so while it technically could be called CLI too, would be a lot more complicated than this project.
Re: Show HN: Devbox – Containers for better dev environments
#45So this reinvents devcontainers? https://containers.dev Why should we use yours? What does it do better or differently?
While this is true, this project seems to wrap it up in a CLI package for starting and stopping projects. Whereas starting devcontainers, at least as far as I have seen, is always done via VSCode or IDE, so while it technically could be called CLI too, would be a lot more complicated than this project.
Re: Show HN: Devbox – Containers for better dev environments
#46Looks like a really fun project. You might want to reconsider the name though, since there is this other devbox from Jetify https://www.jetify.com/devbox that also received quite some attention on HN a while ago https://news.ycombinator.com/item?id=32600821
Re: Show HN: Devbox – Containers for better dev environments
#47Earlier quoted context omitted.
While this is true, this project seems to wrap it up in a CLI package for starting and stopping projects. Whereas starting devcontainers, at least as far as I have seen, is always done via VSCode or IDE, so while it technically could be called CLI too, would be a lot more complicated than this project.
The devcontainers cli has existed for a while. Definitely not as smooth as using with vscode but it has all the main points. https://github.com/devcontainers/cli
I'm not proponent of installing nodejs apps globally, npm install -g or yarn install -g
Re: Show HN: Devbox – Containers for better dev environments
#48How does this compare to toolbx? ( https://containertoolbx.org/ )
And Distrobox: https://distrobox.it One obvious one is that Toolbx and Distrobox are based on Podman, for one.
And as a result, the containers are rootless.
Re: Show HN: Devbox – Containers for better dev environments
#49Earlier quoted context omitted.
C libraries are easiest to install system wide. The situation with multiple versions of libc is tricky to work with. Not impossible, just not easy to comprehend by an average dev.
I'm kinda horrified to think there might be people writing C who don't know how to handle library versions. Somehow I don't think that is the target audience here, by I might be wrong.
You don't need to be writing C code to be affected by the dependency hell.