I know that some developers have a need to run a large
number of local virtual machines, but I do not really
understand why, to be honest.
If you're developing a website, and you want to test on several versions of Windows and IE. Or if you're developing something that needs to work on several versions of Linux and you want to make sure it works right on several different distros. Or if you're developing something that uses Java on Mac and you want to make sure it works if the user has Java 6 from Apple, or Java 8 from Oracle, or both.Obviously, there are ways to struggle through if you don't have much RAM - for example you can run 1 VM at a time and be constantly stopping and starting them. But if testing is a PITA, and it means you do a day's work before you test properly and find there's a problem, you might have wasted that day's work :)
> I use virtual machines too, but remotely, and mostly automatically for continuous integration.
I'd love to do that, but our internet is far too crappy for that – we upgraded our offices from 2 Mbit/s to 10 MBit/s last year, and there are no faster options even if we wanted to –, hence I have to carry the VMs on my laptop (X230 with 16 GiB RAM and 2 SSDs).
I need to test load balancing configurations, transaction troubleshooting, heap dump analysis and so on. VMs are an essential part of my day-to-day activities. 8GiB let's me run Firefox and Chrome and at least 2 distinct projects.
And I'm not even talking about web development troubleshooting which is a pain in itself.
I know that some developers have a need to run a large number of local virtual machines, but I do not really understand why, to be honest. I use virtual machines too, but remotely, and mostly automatically for continuous integration.
I don't think programming is inherently particularly resource-consuming.