Many blizzard games work almost perfectly under wine including warcraft 3, starcraft and world of warcraft. Last time I tried starcraft anthology (digital download) I did not have any problems.
>I haven't noticed much of a difference. Even if there is, there's the matter of the Mac price tag.
and the utter agony of using a Mac if you're used to Windows.
>If you lack the budget for a Mac but you want to do graphic design, Windows is the logical choice.
That comment got flagged (wasn't mine), and this one probably will be too. Holy fuck the apple worship on this site is strong sometimes.
Fair enough but the parent comment claimed that Adobe (and Blizzard) were keeping Windows alive. How can that be if it runs better or at least just as good on Mac?
Wine has long been sufficiently compatible with Windows to run malware. I added a bit about this to the Wine FAQ in 2009 I think ;-) IIRC the ZeroWine malware analyser would run malware in Wine in Debian in a QEMU virtual machine.
The question here is not whether it runs, but whether it can infect.
No, the more pressing question is whether it can run, specifically whether it can run without intervention, and I'm willing to bet a lot of money/bitcoins that it can't, purely because it couldn't gain access to the machine unless those ports were open.
I use a separate user session with a separate X server to run games, which is about 100% of my use of Wine. Granted, that's not out of paranoia, but because video mode switching makes my windows resize and go all over the place and sometimes the window manager crashes, so simply running a barebones OpenBox session specifically for games results in less pain than letting them run on my main desktop.
Isn't the entier fs exposed as Z: or so in wine? I know there's some way to get to the user's home directory which is probably good enough to cause essentially the same amount of pain.
By default only. You can easily disable that. It always made me worried that anything in wine got access to my system, even though I normally wanted something closer to an isolated instance, so I always disabled that.
There may also be links to your home directory as "Desktop", "My Documents", etc. See winecfg for these. And note that your registry files may refer to Z: (mostly for fonts, it seems), or even directly to files outside your Wine directory.
If the software is Wine-aware, it doesn't matter. The \\unix\ filesystem namespace allows programs running under Wine to access the host filesystem whether it's mapped as a drive or not. And, of course, since Wine Is Not an Emulator, it could also use POSIX APIs or Linux kernel syscalls directly if it wanted to.
Wine is not an isolation layer. You can disable the Z: drive but the applications running in Wine still have about the same access a normal application has.
Most interesting. However, you have to butcher your system a bit in order to make that happen... That doesn't say there aren't setups like that, but they are really one out of million.
