[stephenr]

It's always interesting to see new approaches but I don't see this replacing Vagrant for my projects any time soon:

- Vagrant already supports VM or Container environments, and has a well defined system for building and distributing "base" boxes;

- Vagrant uses a Ruby file to define the environment, so it's much more powerful than a Yet Another Migraine Looming file.

[ojacques]

Devcontainers bring notions such as configuring plugins for your IDE, getting « features » from other repos / registries, managing environment variables that you pass from host to devcontainer, and finally either code locally or in the context of a remote environment with more resources or just simply in the context of the rest of your application (very handy for complex network or security setups).

[stephenr]

IDEA/IntelliJ based IDEs already support having their native config committed to a project repo and support a `.editorconfig` file; I'm not sure I need a third way to do so.

Like I said, a `Vagrantfile` is ruby, so besides having all the power of Vagrant and its plugins, you can also just do straight up ruby stuff, or even shell out to do other stuff.