This whole article is weird to me.

I don't really understand the point of a "dev box" that's hosted in a DC and shared, at all - at least not the way they're painting it here.

Hardware capabilities for even consumer level laptops and desktops have progressed much faster than average network connections.

Having testing/preview/branch named environments in a DC? Sure. But this line:

> They should be able to run any software they want inside their own workspaces without impacting each other.

What does that even mean?

Is this about someone working on a feature branch that uses some new dependency that needs to be installed?

That's 100% the sort of thing your local development environment is for, until you're ready to push it to your hosted test/whatever environment.

> But when it's running in a VM, the VM gobbles up as much memory as it can and, by itself, shows no inclination to give it back.

Someone, anyone, tell me which hypervisor doesn't enforce a memory limit on VMs?