Docker uses more resources, and is trying to isolate your code from the rest of thr computer. It also has a higher learning curve. Virtual environments are ju

Docker uses more resources, and is trying to isolate your code from the rest of thr computer. It also has a higher learning curve. Virtual environments are just separate copies of python with their own libraries installed. Pipenv is basically just a workflow for organizing virtual environments I can give someone a repo and tell them to type pip install pipenv && pipenv sync and they'll have everything. Assuming they already have the correct version of python installed, which is one nice thing docker handles, but it is easy to install python these days so it hasnt been an issue. My biggest problem with docker was that I ended up using a ton of storage just learning about it. I have a feeling that was mostly my own fault, maybe using too heavy of a base image. I've been trying it out once or twice a year for about 6 years now, every time my conclusion is "wow this is really cool, I wish i could justify spending more time to get it right" Though docker and virtual environments share the same problem, in that they are just a way for a developer to distribute code to other developers, and to production environments. Distributing python applications to end users is a totally different issue. I floated the idea of sending out a local data collection* app to Mac and windows users mostly because I think it would be fun to try. *data collection of troubleshooting information from users within the same company on company hardware, that are actively asking for help. I'm not trying to spy on people.