Note: This is not asking for extension recommendations.

I recently started exploring the use of Dev Containers for my next Python+NodeJS+PostgreSQL project, and am trying to understand the customizations => extensions part of .devcontainer.json. For example, after auto-generating the configuration file, this is what's in there currently:

"customizations": {
    "vscode": {
        "extensions":["ms-python.python", "njpwerner.autodocstring"]
    }
}

How do I evaluate which other extensions currently installed in the host need to be installed locally inside the container, and which don't?

I'm new to all this. I want to create a containerized environment for each language to stay organized and learn Docker/Linux. What is the difference between the Remote Containers extension and the Dev Environments feature of Docker? Are they both using the same underlying Docker features to create an environment? Are both required for my purposes? What's the best practice for an environment container I probably won't ever need to share with anyone? Thanks!

I was wondering about these today. I have been using them on and off for a few years now for personal stuff, and they work pretty well. Integration with VScode is pretty good too, as a Microsoft backed spec, but I have had some stuff break on me in VScodium.

I was wondering if they have genuine widespread adoption, especially in professional settings, or if they are somewhat relegated to obscurity. The spec has ~4000 github stars, which is a lot but not as much as I would expect for something that could be relevant to every dev, especially if you are bought into the Microsoft development stack (Azure Devops, Github. Visual Studio, etc.)

So do you guys use these? I am always going back and forth on just rolling my own containers, but some of the built in stuff to VScode are great for quickly rolling these. I would be interested to hear what other people do.