Two Views on Containerized Dev Environments
Andrew Welch makes the case for running local development environments in Docker containers. His argument, in brief:
- Each application gets exactly the environment it needs, down to specific versions of supporting services such as PHP, MySQL or Postgres.
- Onboarding becomes a matter of installing Docker and running
docker-compose up. - The environment is disposable — when something breaks, delete it and start a fresh one.
- Because the host machine is kept separate from the dev environment, moving between computers is easy, and conflicting versions of DevOps services don't strand you.
- Trying a different service version is cheap: change a number in a
.yamlfile and bring the stack up again.
The Counterpoint: Cost and Mac Performance
A counterpoint circulated anonymously from a group Slack takes the opposite position. The author describes losing roughly a full day to Docker troubleshooting, at a cost to the client of "literally thousands of dollars" in work not delivered. The setup itself came from the dev team — the complaint is not about its authors but about what the writer calls the brittle, unstable nature of the tooling.
The specific grievance is performance: the writer states that Docker is "horribly slow on the Mac," and has been for several years, yet remains in use. The post closes by asking whether Docker-based development on a Mac can be made not to suck.
Same tool, same platform, two irreconcilable experiences.



