3 ms·
A VM in and of itself isn't a problem for developers, expecting them to configure it themselves is. Vagrant is a really good solution for this: it is generally
by stephenr 5y ago
A VM in and of itself isn't a problem for developers, expecting them to configure it themselves is.
Vagrant is a really good solution for this: it is generally VM based, but the same "box" (basically an image) can be build for multiple providers, so you can use Docker or LXC as your provider, I can use Parallels on a Mac, Jenny can use VMWare Desktop, Billy can use HyperV, and the casual tester can use VirtualBox.
This also doesn't preclude the use of covering different architectures for the boxes: years ago I setup the tooling for a project where one developer had a laptop without a 64bit-capable CPU, so most of us ran an amd64 box, but his was i386.