The provocative claim that developers are “deleting” local environments really describes a shift in trust. More teams are avoiding hand-configured machines because local differences create bugs that are difficult to reproduce.
Modern alternatives include virtual environments, lockfiles, containers, remote development workspaces, and CI systems that build from a clean image. These approaches make dependencies and system requirements explicit. They also make onboarding easier: a new contributor can start from a documented setup rather than a long list of personal fixes.
Containers are not a cure for every problem. They add image maintenance, file-sharing considerations, and operational complexity. A lightweight virtual environment is often the right choice for a small Python script. A container becomes more useful when the project needs system packages, multiple services, or parity with deployment.
The best setup is disposable but understandable. Pin dependencies, document the runtime version, provide one command to create the environment, and run tests in clean CI. Keep local tooling fast so developers are not punished for using the reproducible path.
The goal is not to remove the laptop. It is to stop treating one laptop as the only source of truth.