|
|
|
|
|
by mbreese
480 days ago
|
|
It’s like the entirely of the project is completely self contained. Your host system can be running anything and you don’t need to worry about installing tools on your system to get going. You also don’t need to worry about different dev environments for different projects. Is this a Go project and you don’t have the right Go tools installed locally? Not a problem, as it’s in the container. Do you have multiple node/js projects and you don’t want modules or tools to overlap? Each project has its own container. Do you work on Mac, but want to deploy on Linux? The container makes this work too. (This one is my primary usecase). With a devcontainer, I can work on my Mac without having to install dozens of homebrew packages. Better yet, I can work with others and it doesn’t matter what computer they use, as the dev environment is standardized. If you ever used Vagrant to work in a dev VM, it’s like that… but much faster to get started. |
|