Gareth Rushgrove writes about development environments, operations, containers, Kubernetes, and Django performance.
HN gives little opinion here; the comments link his post on using virtualisation in development, and one commenter agrees with it.
I did finally see this entry. It was a great read and I agree completely with it. Note that I posted my comment on the blog directly: http://morethanseven.net/2010/11/04/Why-you-should-be-using-virtualisation.html#comment-94464917
Since clicking on that just to read my comment can be annoying, I've copied it below as well:
=========================================================
Yes! Yes Yes Yes! Virtualization for development is extremely important and I'm glad you wrote this. Also, thanks for the hat tip to Vagrant, I appreciate it. I've given a few talks on this and it always amazes me how many people are so comfortable with the status quo of developing on their own machines with apache/mysql/etc installed directly on their machines. Its a disaster waiting to happen.
I want to point out to the many people using VMWare out there: VMWare Fusion is great, yes, I won't argue. Their shared folders are better, again I agree. But Vagrant does make use of NFS which is faster than even VMWare Fusion's shared folders in order to get around VirtualBox's terrible performance.
And just because I have things to say, here are a few of my own remarks against the arguments against virtualization of development:
* Speed - Given enough RAM (which for a standard web application, shouldn't be any more than 512 MB to 1 GB for the VM instance), the speed difference is noticeable but not detrimental to your productivity. For regular web requests you won't notice any speed difference. For…
I'll give it a good few weeks, say a month, and then get the results together. It depends on how popular it is, if I'm still seeing results come in and how much time I can grab.
I'll post them to my blog (http://morethanseven.net) and I'll post the link on here too.