I use wine for running test in configure scripts when cross-compiling my software for windows. That way I can provide window binaries without running any proprietary software. This is great.
Virtualization would still require me to have a window license, and would be much more painful to set up.
Posted Nov 6, 2010 18:12 UTC (Sat) by dlang (✭ supporter ✭, #313)
[Link]
not to mention that if you run a virtual machine, you thenhave to worry about patching windows, anti-virus, and all the other problems that windows administration brings.
<rant>
people seem to consider virtualiation to be a solution to administration problems, they tend to ignore the fact that every virtual guest that you create is another (logical) box that has to be administered.
I've seen management reject good network architecture designs because they 'add to much complexity' because it adds a couple more pieces of hardware, but this same management doesn't blink at the thought of adding a few dozen virtual machines.
there is less hardware to manage, but the software management is the majority of the effort.
</rant>
Wine gets better, but not perfect, with age
Posted Nov 10, 2010 12:11 UTC (Wed) by nelzas (subscriber, #4427)
[Link]
I agree. Just two weeks ago, as a student I've been asked to deliver exercises as windows executables. I installed mingw cross-compiler to do that, and then Wine to check that those executables run ok. I didn't need to do anything to configure Wine. Although I would like to play with virtualization, I don't have enough time to deal with it currently, but then only to try other Linux distros, not to have to deal with Windows...