> You should really use docker >> I think you missed the point. Maybe I did, but I've been using Docker as version management for pretty much every technology

> You should really use docker >> I think you missed the point. Maybe I did, but I've been using Docker as version management for pretty much every technology I employ for five or six years. Prior to that I sparsely used things like rbenv and virtualenv and I actually thought it was super dangerous and unreliable. Maybe it's gotten better in recent years, and certainly people who write python and ruby every day are going to know more about this than I do. I don't install anything on my computer if I can just use Docker for it. OK, I do have go:latest, but I use docker images for various projects that might be on any version of go from 1.8 to 1.20. Your website still runs on PHP5.3? I can help you (I won't, but I could totally run it locally!). Reasons I like docker better: 1. Any scripts or configs can explicitly refer to the version number. No guessing or assuming. 2. Our whole team uses the same version. 3. Only one dependency: docker. Granted I'm more of a sysadmin than a developer and I'm sure that biases apply.