it is difficult to recreate an environment similar to the production environment (e.g old versions of Windows / reliance on very finicky dependencies)
you need multiple conflicting versions of dependencies e.g software that relies on a version of glibc different from one in your system.
Your production environment runs a completely different OS compared to your laptop/dev machine
If you can recreate development environment easily without a VM, it is totally fine. In such cases, installing from a script or using Chef/Puppet/Ansible playbooks are also valid alternatives.
It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
This is basically it; using something like Vagrant, docker-compose, or minikube for your local environment just because tends to have a pretty miserable effort:reward ratio.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
VMs and Containers are useful if:
If you can recreate development environment easily without a VM, it is totally fine. In such cases, installing from a script or using Chef/Puppet/Ansible playbooks are also valid alternatives.
This is basically it; using something like Vagrant, docker-compose, or minikube for your local environment just because tends to have a pretty miserable effort:reward ratio.