What's more annoying is doing port mapping through VirtualBox's XML configuration files, but this is a one-off task and not too complex. I'm seriously considering purchasing Mac OS X Server edition and using that in a VM as well but I can't figure out if this actually works. Does anyone know?
However, then I read this ServerFault thread and realised the bridge is a _new interface_, and hence you must either bind directly to it or bind to all interfaces in order to get your VM to become externally accesible!
http://serverfault.com/questions/206498/virtualbox-bridge-ne...
Fantastic!
And yeah, the reason something like AppEngine or Django wouldn't work is that they, by default, bind only to loopback/127.0.0.1, and are only accessible from the host on which they're running, as a security precaution.
Running two systems on your laptop is a perfectly viable strategy for dev machines, and if you're most at home in Windows, I recommend it. If you're Linux or OS X, though, I think it's probably worth the effort to keep your dev environment cross-platform instead of working on it in a VM.