Presumably this is also mostly used with Linux. How do people manage Windows licenses with Vagrant?
No, it's very useful for desktop, and especially embedded development. It lets you have consistent images to test your code against.
Presumably this is also mostly used with Linux. How do people manage Windows licenses with Vagrant?
No, it's very popular on both Windows and OS-X. Virtualbox is most popular on both platforms (because it is free).
No, I think that they meant with Windows Guests (hence the license question).
I don't think that Vagrant is used much for coding Windows applications, but rather coding Linux (web) applications from Windows hosts.
I've never used it, but it looks like there is a way to use this for Windows Guests as well: http://www.thomasvjames.com/2013/09/create-a-windows-base-bo...
YMMV
With vagrant primary mode of interaction is through ssh (although it supports showing GUI on vagrant up). So I don't think it is a good fit for developing Windows or desktop applications.
As soon as you get this consistent workflow, then you can teach it to your entire organization and the whole company knows that ANY project in the company can be worked on using this workflow without any dependencies on their own machine.
And if ops decides to suddenly change the dev environment from VirtualBox to say... AWS... nothing changes! I've had large companies (200+ developers) switch from VirtualBox to VMware to AWS for their dev environments without their developers ever really noticing.
That is pretty cool.
Of course, on top of this, you get a lot of nice things: you get provisioners, you get automatic network configuration, you get the entire plugin community, you don't have to worry about stability on your own because you tap the collective stability of thousands of users, etc.
But the real power is workflow.