Linked by Thom Holwerda on Sat 7th Apr 2007 20:58 UTC, submitted by rx182
Thread beginning with comment 228625
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2006-01-21
Sorry to nitpick, but there indeed are shorter paths, that connect two points in general settings, where "general" means that you don't happen do have a purely euclidean metric / topology ==> your two points are not sitting on a flat (hyper)plane.
http://en.wikipedia.org/wiki/Geodesic
is a quite accessible introduction to an important mathematical concept.
So with that in mind, it is entirely possible to achieve better performance with an comp ability layer like WINE than with the native stuff (once the compability layer works, which starts to become increasingly true for WINE, judging from my limited exposure), if the compability layer and the OS that hides beneath manage to be more efficient than the "original" OS.
I'm not implying that this is the case here, as I have not done measurements myself, but judging from posts like the Grandparent post of this and this [1]
[..SNIP..]
Also, and that's what people are usually interested in, the combination Wine+Unix may be more efficient that Windows. Just as before it's just how good/bad their respective algorithms are. Now to be frank, performance is not yet a Wine priority. Getting more applications to actually work in Wine is much more important right now. For instance most benchmarks do not work yet in Wine and getting them to work at all should obviously have a higher priority than getting them to perform well.
, it is - repeating myself - not entirely unlikely.
Remember: WINE is not an Emulator
[1]:http://www.winehq.com/site/myths
EDIT: Pressed Submit to early ...
Edited 2007-04-08 07:42