WINE can beat XP!

[Screenor]

There was something on G4 the other night about how Windows was the revolution because people never had to worry about difficulty playing games anymore, or something a long those lines that Dos was too complicated and hard to use.

Only reason I use Windows is because I love gaming, and wouldn't be able to not play things like WoW, and CS.

[Joe]

something a long those lines that Dos was too complicated and hard to use.

Heh, DOS isn't hard to use, it just pisses off the hunt-and-peck typers.. a lot. =p

[rabbit]

There was something on G4 the other night about how Windows was the revolution because people never had to worry about difficulty playing games anymore, or something a long those lines that Dos was too complicated and hard to use.

Only reason I use Windows is because I love gaming, and wouldn't be able to not play things like WoW, and CS.

IIRC WoW runs fine on WINE.

[Newby]

Haha. I don't think Wine cheated, considering they implemented that wmf implimentation verbatim (it was affected by the vulnerability too).

[Warrior]

I think it's been stated pretty well in this forum that those comparisons were pathetic.
Somepeople should actually *look* at the benchmark before all the Linux fanboys run up
"YES WE DID SOMETHING TO GAIN SOME SORT OF FALSE BELIEF THAT WE STAND WITH THE BIG BOYS"

[iago]

Haha. I don't think Wine cheated, considering they implemented that wmf implimentation verbatim (it was affected by the vulnerability too).

The vulnerability is in the specification, not the implementation.  The thing is, it's not exploitable without a broken image viewer, which is why it wasn't exploitable until Windows 2000 came along, with the broken image viewers. 

[iago]

Interesting but how an you actually benchmark something like this? WINE is unfinished so it goes without saying that calling a stub will be faster than calling a real function. Furthermore WINE may cheat at somethings for the speed vs functionality.

I finally got around to reading it, so I can answer the question. 

Did you look at the benchmarks?  For the most part, they where "draw a line", "allocase xxx bytes of memory", "createa  3d object with 3 light sources", etc.  You can't exactly stub that out and hope that the benchmarker doesn't notice.  Either it works, or it doesn't.