3 ms·
A few years ago i used it for automated builds. The GUI bits were (and i think still are, at least last time i checked it a couple of months ago) broken, but th
by badsectoracula 8y ago
A few years ago i used it for automated builds. The GUI bits were (and i think still are, at least last time i checked it a couple of months ago) broken, but the command-line works fine and for automated builds it worked perfectly.
- acct1771 8y agoTo what benefit, could you share?
- selectodude 8y agoIt’s free
- slrz 8y agoRunning Windows builds and tests where Wine didn't work but ReactOS did? This might be motivated by Windows licensing regime. Licensing for Windows VM instances used to be super-painful, so people would try hard to avoid it. IIRC, to run a Windows VM you were required to acquire Windows Datacenter licenses for every node capable of running that VM (at least that's what we were told). If you have a fleet of hypervisor nodes running Linux workloads, the licensing cost calculated for a single Windows VM was absolutely ridiculous. I guess things are less insane today and you can just get a license for the guest OS, no matter whether it's running virtualized or bare metal?
- badsectoracula 8y agoFamiliarity, mainly. The tools i used were Windows binaries and i knew how to set them up under Windows (although it took a couple of tries under ReactOS due to GUI freezes, etc, but this was in a VM image that i'd later reuse as a sort-of blank state for each build - note BTW that this was like 6-7 years ago), whereas at the time i felt a bit skittish using Windows development tools under Wine.