The instructions explain how to set up SITL (using Vagrant - the bit you point to) and how to set up DroneKit and talk to it (and real devices). If all we wanted to do was talk to SITL we could simplify the instructions and have everything (DK and SITL in that one Vagrant instance) - but we couldn't then use the same DK setup to talk to a real device. I proposed this configuration for the quickstart originally but we decided that this would be confusing for users who wanted to "quickstart" talking to a real device.
In any case, Docker is another solution to Vagrant for
hosting SITL , it is not an "all in one" solution for setting up both SITL and a separate instance of DroneKit to talk ot it.
I completely agree with your point/requirement though. I had a discussion on this a few weeks ago and there is some work going on to improve the situation. Now we can build
SITL natively on Windows Michael Oborne is working to integrate SITL as part of Mission Planner. I would hope he is also embedding DroneKit so we can run scripts to that SITL instance. At that point DK on Windows at least becomes very easy. [And as an aside, I'm hoping we'll also get some decent debugger integration too :-0]. I also asked for the Windows installation of MAVProxy to include DK:
Dronecode/MAVProxy/issues/148. If any of those deliver the instructions on Windows will be much simpler.
In theory you could also build SITL for Mac and have a similar solution. For now though, you still need vagrant for the simulation side of things.
Cheers
H