Slashdot Mirror


Wine vs Windows Benchmarks

PeterBrett writes "Tom Wickline recently posted to the Wine development list announcing that he'd done some benchmarks comparing Windows XP to Wine. They should be taken with the requisite dose of salt, but Wine has certainly come a long way."

286 comments

  1. The tests are meaningless! by creepynut · · Score: 5, Funny

    We need real benchmarks! Get some Windows worms/viruses/trojans running on WINE and then we'll have some real-world benchmarks!

    I say good day to you sir!

    1. Re:The tests are meaningless! by fleaboy · · Score: 1

      propagate, propagate, propagate!

      --
      Life is a gift. And my Karma couldn't possibly be 'Positive'
    2. Re:The tests are meaningless! by wayneo13 · · Score: 4, Interesting
    3. Re:The tests are meaningless! by Anonymous Coward · · Score: 0
      From that link:
      Out of the five Windows viruses I ran under Wine, not a single one was able to send email and propagate itself. When I went out of my way to be part of the Windows community by doing my part to propagate Windows viruses (lots of Windows users seem to think this is important, seeing as how they run random executables and use Microsoft Outlook and Internet Explorer) I discovered that it couldn't easily be done with GNU/Linux tools.

      I tip my hat to the creators of the SomeFool virus, for actually (albeit temporarily and minimally) affecting my Linux experience. However, if that's the most damage I can get by running viruses with Wine under a dummy account, then it's clear that the Wine developers have a long way to go before Wine is truly Windows compatible.

      Doing well with the apps yet resisting virii. Nice work, Wine!
    4. Re:The tests are meaningless! by Gary+Destruction · · Score: 1

      Don't forget spyware. That slows browsing up to 500%.

    5. Re:The tests are meaningless! by TheDarkener · · Score: 1

      Which brings the next question - how does AOL size up? This way you can test pop-ups, adware, spyware, viruses and spam all in one!

      It's the best Wine EVER!

      --
      It is pitch black. You are likely to be eaten by a grue.
  2. on a dev list by mrcdeckard · · Score: 5, Insightful

    while i realise that postings to a dev list shouldn't be taken as gospel, why would a dev list posting of benchmarks be assumed to be doctored? of course i would expect this from a marketing dept, but a dev list?

    chris

    --
    "Physics is like sex. Sure, it may give some practical results, but that's not why we do it." - R. Feynman
    1. Re:on a dev list by i+kan+reed · · Score: 5, Insightful

      pride. i'm a developer of software, and I don't allow myself to test my own code beyond a certain point because i'll be too proud of my accomplishments to accept mistakes or failures.

    2. Re:on a dev list by njh · · Score: 2, Insightful

      pride. i'm a developer of software, and I don't allow myself to test my own code beyond a certain point because i'll be too proud of my accomplishments to accept mistakes or failures.

      This is only half the story. Our research group tries to get our bleeding edge algorithms into existing software (e.g. text algorithms in scribus, connector routing and graph layout in inkscape). One thing we've found is that when you are developing some code it's easy to get trained into only trying certain pathways through the code. In each case we've found that once you let fools play with your foolproof algorithm, they find things you hadn't tried. If these stats are standard tests used by wine devels they will only contain well tested pathways, and if you leave those pathways things misbehave or run slowly.

    3. Re:on a dev list by hardburn · · Score: 5, Interesting

      Read the article. These aren't dev-created benchmarks, but standard benchmark suites like 3DMark and Quake 3.

      Some of the tests look really weird. For instance, in the 3DMark2000 Fill Rate test, Single Texture on Wine gets 2,402.8 MTexels/s and 11% behind Windows, but on the Multi-Texture test it soars to 6,695.1 MTexels/s and 74.5% in front of Windows. There's got to be some freaky driver code or something implemented oddly or some background process that wasn't noticed.

      I don't think these benchmarks were run rigoriously enough to say anything, except that Wine is capable of running 3DMark.

      --
      Not a typewriter
    4. Re:on a dev list by leuk_he · · Score: 4, Insightful

      Some of the tests look really weird.

      That is the key phrase(but you have to look literally). The point is that you need to test the output of the benchmarks, not just look at the frame rates. You can create a REAL FAST benchmark by not implementing some api functions. The output might look reasonable, but if you zoom into some edges you might find additional oddities. That is the main point what is mising in this benchmark.

      Rememeber driver writers made some unacceptable shortcuts in the past to increase performance.

    5. Re:on a dev list by KowShak · · Score: 1

      Programmers make mistakes, the mistakes have to be found and fixed. Burying your head in the sand doesn't help. I was once told that a successful test is one that finds a fault, a test that finds no faults serves no purpose.

      Keep him away from anything mission critical!

    6. Re:on a dev list by NutscrapeSucks · · Score: 1

      3DMark is a DirectX benchmark, I believe. It's quite possible that Wine's implementation is incomplete, where certain operations on Windows become no-ops on Wine.

      In this case, you have a "Quack3" time benchmark, where sure it runs faster, but at the expense of image quality.

      Even in the OpenGL tests, you have some pretty wild differences that probably related to the driver being used rather than Wine v Windows.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    7. Re:on a dev list by FooBarWidget · · Score: 1

      That says more about you than about developers. I am a developer too and I don't care whether I did something wrong or my dog did, I want the thing to be stable and I want it to be good.

  3. Very Impressive! by gasmonso · · Score: 5, Informative

    I've quite impressed with the performance of WINE, however these stats can be a little deceiving. These stats are based on a game that works. Getting the game to work in the first place can be quite a challenge. But for the part-time gamer that doesn't wanna be chained to Windows, this is a great alternative indeed!

    http://religiousfreaks.com/
    1. Re: Very Impressive! by Black+Parrot · · Score: 0, Troll

      > I've quite impressed with the performance of WINE

      As I understand it the essence of Wine is reverse engineering the Windows DLLs. In principle getting comparative performance shouldn't be any particular challenge. Especially if Microsoft's reputation for producing bloated slopware is accurate.

      --
      Sheesh, evil *and* a jerk. -- Jade
    2. Re:Very Impressive! by ejito · · Score: 0

      There were two small sections of two games on the bottom. Both games are very easy to install (Quake and UT).

      Most of the benchmarking is done by industrial software programs (raw operations), not videogames.

    3. Re:Very Impressive! by aarku · · Score: 0, Offtopic

      Put your sig in the signature field where it is supposed to go.

    4. Re:Very Impressive! by Anonymous Coward · · Score: 0

      The stats are also based on a version of WINE that works. As you note, getting a game to work in the first place can be difficult. The version of WINE they are testing is the last decent version they put out. That was 9 months ago. Games work *less* well with more recent versions.

    5. Re: Very Impressive! by strider44 · · Score: 3, Insightful

      As I understand it the essence of Wine is reverse engineering the Windows DLLs.

      You might understand it that way, but you'd be wrong. All Wine does is implement the published API of Windows using Linux commands. Absolutely no reverse engineering is done.

    6. Re:Very Impressive! by Psykus · · Score: 1

      Kind of pointless though, since don't both of those games have native Linux versions?

    7. Re:Very Impressive! by MichaelSmith · · Score: 2, Interesting
      These stats are based on a game that works

      My sister in law runs ubuntu and I have had a go at getting some windows games running under wine for her son. What I would like to see is a windows environment which she can use to install these things herself.

      As it is I have to mount the CD, find the installer executable and run it under wine. This is a bit difficult to explain to a non technical person.

    8. Re: Very Impressive! by diegocgteleline.es · · Score: 2, Informative

      You might understand it that way, but you'd be wrong. All Wine does is implement the published API of Windows using Linux commands. Absolutely no reverse engineering is done

      Let me doubt that - there's many "hidden functionality" in windows (ie: bugs created in windows 95 and that apps started to use and need it to work reliably and that they were kept because of compatibility reasons. Remember all those 0x0000blah numbers in Windows\system.ini? Each 0x0000blah number activates a special hack neccesary to keep the apps named before the number working. I doubt they documented that part )

    9. Re: Very Impressive! by DrXym · · Score: 2, Interesting
      You might understand it that way, but you'd be wrong. All Wine does is implement the published API of Windows using Linux commands. Absolutely no reverse engineering is done.

      Sorry, that can't be true. The Win32 documentation is fairly comprehensive, but it is absolutely horrible on the fringes. There is NO WAY you could implement an API from it and expect it to be able to run real world apps. The docs for RPC, OLE, Shell, Common Controls, Win16 are particularly atrocious. More likely you code to the API and then discover the 101 ways that apps break the APIs and the 101 ways that the APIs differ from the specs through test cases and you make your changes accordingly.

      On top of that, the header files alone are filled with macros, switches, messages, uuids, flags which aren't even mentioned in the docs, or whose underlying values are not specified.

      So perhaps there is not reverse engineering in the sense of disassembling Windows to see what is going on, but there certainly is reverse engineering of the APIs via test cases and headers by looking up the real headers.

    10. Re:Very Impressive! by harryman100 · · Score: 2, Informative

      While you'd have to pay for it - Point2Play (from Transgaming) does exactly that, it allows you to have completely seperated environments and settings for each game/application. I used to use it when I was still finishing off the windows games I had been playing when I switched to linux. Now I only buy linux games.

      --
      .sigs are for losers
    11. Re:Very Impressive! by ThePhilips · · Score: 1

      That's why it is developer test.

      It allows to compare how M$ Windows executable under Wine performs relatively to native Linux executable and to native Wind0ze executable under Wind0ze.

      --
      All hope abandon ye who enter here.
    12. Re: Very Impressive! by Black+Parrot · · Score: 1

      > > As I understand it the essence of Wine is reverse engineering the Windows DLLs.

      > You might understand it that way, but you'd be wrong. All Wine does is implement the published API of Windows using Linux commands.

      And that's exactly what reverse engineering is.

      If you have a gadget (or program) and I want to make one that does exactly the same thing, but do it by figuring it out rather than by working off your blueprint (or source code), then I'm reverse engineering it.

      --
      Sheesh, evil *and* a jerk. -- Jade
  4. Maybe a grain of salt, but it's what I'd predict by strider44 · · Score: 5, Insightful

    The results aren't exactly surprising - Wine is excelling in what Linux is generally better than Windows in doing - memory management, hard drive speed, and related matters (stressing generally there, because of course different apps give different results). This is Gentoo after all, it's built for speed. Then the heavier the load on the video drivers the more the superiority of the Windows drivers takes hold, so for the graphical stuff things don't work as fast.

    Congrats to the Wine devs!

  5. cool! by Anonymous Coward · · Score: 0

    ive been looking for an excuse to switch to linux.. i wonder if office 2003 will run under wine?

    1. Re:cool! by msh104 · · Score: 1

      try codeweavers,

      it runs word 2003, excell 2003 and powerpoint 2003

      I myself use office 2000 under codeweavers because, in my experience that one runs best, and 2003 support is pretty new.

  6. wine or driver test? by shoelace_822695 · · Score: 5, Insightful

    To me this seems to be more a test of the linux implementation of teh video card drivers.. and NOT the wine system itself.

    i think a wider suite of tests would be required.. and not just the preformance/gaming orinted stuff.

    --
    -- Shoe Lace
    1. Re:wine or driver test? by ejito · · Score: 1

      The best gains Wine had were on PC Mark 2k4 testing. If you actually looked at the benchmark, you can see Wine did poorly on the graphical part, however every other part, except HDD usage, Wine exceeded windows.

    2. Re:wine or driver test? by njh · · Score: 1

      The fact that the drivers are better is certainly interesting by itself.

    3. Re:wine or driver test? by evilviper · · Score: 1
      To me this seems to be more a test of the linux implementation of teh video card drivers.. and NOT the wine system itself.

      Well that is implying that the Nvidia drivers for Windows are much better than for Linux, which is essentially the opposite of my experience with video.

      Obviously graphics is the bottleneck, so perhaps it's a case of WINE not translating the video instructions as well as it does for other instructions.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    4. Re:wine or driver test? by Ruie · · Score: 1

      It is also a test of DirectX -> GL translation layer that Wine implements.

  7. Compatibility more important than speed! by aussersterne · · Score: 5, Interesting

    Speaking as someone who used to be a Wine-hater, Wine has definitely come a long way. My impression of Wine for years was that it a) was impossible to install and configure, b) didn't run anything other than solitaire, and c) caused major instability to desktops.

    Then I tried Codeweavers' "Crossover Office," essentially a pre-configured Wine with graphical configuration and installation tools, and everything changed. I currently use all of the following under Fedora Core 4:

    - Microsoft Office XP
    - Wordperfect 12 (word processor only)
    - Photoshop 6
    - Framemaker 7

    They all installed using the standard CD install, without my having to jump through any crazy hoops or type a single command, and they all run flawlessly and are great for serious work. They sit right in my KDE menu like all other applications and it's a real head-turner to be able to show up to work with my laptop running Linux and then pop into Word XP and Framemaker.

    Wine works incredibly well after all, it's just more "raw material" than "finished product." Get someone to write a user-friendly front end for it (ala Codeweavers' Crossover Office) and it offers a very high level of Windows compatibility to Linux users.

    --
    STOP . AMERICA . NOW
    1. Re:Compatibility more important than speed! by Kasracer · · Score: 1

      What about higher end MS applications like VisualStudio or the .Net framework? How well do they perform with Wine/Cross-Over? What about Macromedia software?

    2. Re:Compatibility more important than speed! by Theatetus · · Score: 3, Interesting
      What about higher end MS applications like VisualStudio

      Why would you run a Windows-only compiler on Linux? But, more importantly, #2:

      or the .Net framework?

      Why would you run an allegedly platform-dependent runtime on an emula^H^H^H^H compatibility layer?

      --
      All's true that is mistrusted
    3. Re:Compatibility more important than speed! by Kasracer · · Score: 2

      No real reason. Just want to know if it can be done. I do a lot of development work in both C++ and C# so if I could would with .Net and VS on Linux, I could finally move to Linux only.

    4. Re:Compatibility more important than speed! by misleb · · Score: 3, Insightful

      What about higher end MS applications like VisualStudio or the .Net framework?

      At some point you have to ask yourself why you are running Linux at all.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    5. Re:Compatibility more important than speed! by clintcan · · Score: 1

      As for Visual Basic 6.0 (I have the Standard Edition), you can install and run it as you would in windows. I've had more experience however installing Macromedia Studio MX, and practically all work as expected, except for some display refresh quirks in Fireworks and Dreamweaver (however Fireworks has more refresh quirks). I have since rarely used windows more or less at home because of this, since I run these tools already in linux. As for the wine version I used... those tools have been tested in 0.9.2, 0.9.3, 0.9.5 and 0.9.6 Interestingly, emulation programs which use opengl run as fast or faster(!) than when using windows (epsxe - a psx emulator is an example).

    6. Re:Compatibility more important than speed! by ZenShadow · · Score: 1

      A reasonable point here is that with some work Wine and the Mono folks could team up for an interesting result.

      As to VS.NET not building for other OS's, I run VS.NET-compiled binaries all the time under Mono. Works just fine. And VS is (IMO) FAR better than any currently-available Linux dev environment C# or C++.

      Hint to folks with more time on their hands than I've got: build a VS.NET clone, bring lots more people to the Linux world.

      --S

      --
      -- sigs cause cancer.
    7. Re:Compatibility more important than speed! by rvalles · · Score: 2, Informative

      Just use Mono.

    8. Re:Compatibility more important than speed! by BiDi · · Score: 1

      WineGUI for the linux platform would be an excellent idea.

      If it would be distributed with a simple to install linux distro and it would enable users to simply run WineGUI, select a windows installer file/zip with it and run it to install the win32 application on the linux box... you know where I'm going with this.

      If a distribution like this would exist the single reason people stil use winblowz would be eliminated: simplicity of installing win32 applications. On windows most applications "just work". With WineGUI they could be made to "just work" also on a linux machine.

      And the best of this would be: The only unsupported applications that wouldn't work would be spyware ridden bloatware and badly written freeware crap that all users would have to replace. Replace with what? Free and better alternatives from the WineGUI database of good quality applications.

    9. Re:Compatibility more important than speed! by Dh2000 · · Score: 1

      there's a native linux version of epsxe, so why are you running it under wine?

    10. Re:Compatibility more important than speed! by Anonymous Coward · · Score: 3, Informative

      I recently had a major problem with a legacy mission critical appliation no longer working under windows. This application was designed for windows 95. This wasn't a data error, we rolled back to older versions of the application and the database and the software just wouldnt work under windows. We tried different computers, different versions of windows, they all refused to run the application and gave varies error messages. We needed this application running and it was a major problem that it didn't work.

      As a last ditch effort we tried running it under wine. No problems. It just worked. Wine was able to run an windows application that windows couldnt.

    11. Re:Compatibility more important than speed! by Andrzej+Sawicki · · Score: 1
      Why would you run an allegedly platform-dependent runtime on an emula^H^H^H^H compatibility layer?
      What other choice do you have if you work using programs (plural -- they often work together) that require WinXP (SP2) and .NET (some use 1.1, some use 2.0)? I am specifically talking about various CAT (Computer Aided Translation) software, but I guess there are others.
    12. Re:Compatibility more important than speed! by clintcan · · Score: 1

      I do use the linux version of epsxe. However: 1. The opengl plugin doesn't run in my distro (It crashes it), so I'm forced to use the software video plugin. Epsxe is more of a programming curiousity for me. Psx plugins in linux are unfortunately more unstable than their windows counterparts in this case. Microsoft has gotten their direct3d and directx api right in this rare instance. 2. Since I'm the application maintainer of dreamweaver mx in winehq, I test other windows programs in my spare time in wine as a hobby. This includes some of the more unknown windows programs, including emulators such as epsxe.

    13. Re:Compatibility more important than speed! by Anonymous Coward · · Score: 0

      ummmm if you had bothered to do some research you would have found windows XP has the ability to run a program in a compatibility mode so that to the program it looks like it is running under windows 95. besides that I can't believe this app is mission critical if the organisation is to lazy to bother to update it or maintain it for 10 years.

    14. Re:Compatibility more important than speed! by tinkerton · · Score: 1

      I would boldly state that performance differences of a factor 2 shouldn't matter that much(just for the bleeding edge stuff).

      That said, it's not that hard to create code that is 50 times slower on WINE and poses a real problem.
      But it's just as well possible to adapt the code and work around the problem.

    15. Re:Compatibility more important than speed! by aussersterne · · Score: 1

      This is exactly what Crossover Office does, including parsing autorun.inf files.

      --
      STOP . AMERICA . NOW
    16. Re:Compatibility more important than speed! by ratboy666 · · Score: 1

      I can speak to Microsoft dev tools.

      When I do Windows dev, I generally use the Windows tools "cross" on a Linux x86 platform with Wine.

      No, I haven't tried the IDE (not my speed), but CL.EXE, LINK.EXE, etc. work just fine. And you can run them straight from the command line (after registering the EXE executable type). Which means that they can be run from GNU make and can participate in AUTOCONF.

      It just works.

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    17. Re:Compatibility more important than speed! by Grishnakh · · Score: 1

      So he can run AmaroK. By itself, it's enough of a reason to run Linux.

      Of course, immunity to viruses and worms is a big plus too.

    18. Re:Compatibility more important than speed! by Heliode · · Score: 1

      Funny thing is, I actually run and use Delphi 7 with Crossover Office (for school).

      --
      Fox can take the sky from you.
  8. Note that XP Wins the Tests that Count by Shimdaddy · · Score: 2, Insightful

    Notice, however, that the 60 some tests that Wine leads on are synthetic through and through... and when you get to actual games it's XP all the way. While Wine's performance is impressive, the requisite dose of salt may be several kg for this article.

    1. Re:Note that XP Wins the Tests that Count by ajwitte · · Score: 1

      For games, sure, but what about other apps? Linux has (speaking very generally) worse 3d graphics performace than Windows, so it's to be expected that WINE would perform worse than Windows when running games. I don't have experience running WINE on modern hardware, but I imagine the speed differential is much less (or even nonexistent) when running, say, Office or IE.

      --
      chown -R us ~you/base
    2. Re:Note that XP Wins the Tests that Count by packeteer · · Score: 2, Insightful

      Windows XP (and 2k) are better for gaming becuase of all the third part addon's and apps that only work on windows. Technically yes you can can run a game in linux but you cant run many of other programs such as Ventrilo. Ventrilo is a MUST becuase I am in a WoW raiding guild. Right now there is no Ventrilo client for linux.

      Before you go and say "well run Ventrilo under wine!" let me tell you that i have tried and it did not work. I dont know why it did not work and i dont care. Even if it was a relativly easy tweak I am not willing to do it. Its not that I can't get it to work, but why not use windows which "just works".

      Again before you guys go off about how Windows doesn't "just work" let me tell you it DOES for me on my gaming machine. My spare time these days is spent raiding instead of tweaking my computer and i prefer it that way.

      --
      unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep
    3. Re:Note that XP Wins the Tests that Count by Anonymous Coward · · Score: 0

      Ventrilo is a MUST becuase I am in a WoW raiding guild. Right now there is no Ventrilo client for linux.

      I'm Linux only, and I play a fair bit of Puzzle Pirates and Unreal Tournament. I use Skype and/or Teamspeak to talk to my flag/teammates... most everyone has at least one or the other.

      Yes, having Ventrilo for Linux would be great too (and they've been promising a client forever), but there are other options that work right now.

    4. Re:Note that XP Wins the Tests that Count by Anonymous Coward · · Score: 0

      If everyone in the raid uses Ventrilo, having TeamSpeak available IS TOTALLY AWESOME.

    5. Re:Note that XP Wins the Tests that Count by evilviper · · Score: 1
      Again before you guys go off about how Windows doesn't "just work" let me tell you it DOES for me on my gaming machine. My spare time these days is spent raiding instead of tweaking my computer and i prefer it that way.

      I'd much prefer a couple days of tweaks to get a Linux/BSD system up and working properly, rather than spending hour after hour of my life putting up with an operating system that is incredibly slow for absolutely no reason, is terribly unstable, needs to be scanned constantly for viruses and spyware, needs to be defragmented regularly, and tends to just randomly break.

      A stitch in time, my friend.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    6. Re:Note that XP Wins the Tests that Count by Anonymous Coward · · Score: 0

      Then maybe everyone should clue up and leave Ventrilo for TeamSpeak? I know the group I play with did.

    7. Re:Note that XP Wins the Tests that Count by ltbarcly · · Score: 1

      Ok, so wine isn't perfect for you, so you run windows on your computer. I'm glad I spent 8 seconds of my life reading about it. You play WoW? Very interesting. You use another program with that? That rules! What color is your car? Do you wear reading glasses? Who was your favorite English teacher? Do you prefer running or basketball shoes, and why? Could you stretch your answer out to 5 or 6 paragraphs?

      Alternate response:
      You really don't have anything better to do with your time than to collect imaginary trinkets in fantasy land? When you're 80 you'll think back on today and weep dusty old man tears over your wasted life.

    8. Re:Note that XP Wins the Tests that Count by Politburo · · Score: 1

      It's not Windows 95 anymore. Get over it.

    9. Re:Note that XP Wins the Tests that Count by Politburo · · Score: 1

      And you don't have anything better to do with your time than make fun of people on slashdot? That's gotta suck.

    10. Re:Note that XP Wins the Tests that Count by ltbarcly · · Score: 1

      This is true... sniff...

    11. Re:Note that XP Wins the Tests that Count by evilviper · · Score: 1

      Actually I was talking about the hundreds of 2000 boxes I had to administer. I doubt XP has improved the situation all that much.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    12. Re:Note that XP Wins the Tests that Count by Grishnakh · · Score: 1

      You're right, Windows 95 is long gone. I remember those days: viruses, worms, and spyware weren't nearly the problem they are now. In fact, spyware simply didn't exist back then, so we didn't need software like AdAware. Now, I just connect my WinXP laptop to the internet and I get worms automatically. Every time I connect my laptop to my corporate intranet, I have to waste time downloading security patches, applying them (unlike in Linux, you can't do it in the background), and then rebooting. It's a huge waste of time.

      Ok, maybe Windows doesn't crash quite as much as it used to, but the malware problem is far worse than ever, and is at least as much of a time-waster, whether you get hit by the malware directly or you run an AV program in the background (making your computer slower) and keep up with the neverending barrage of security patches.

    13. Re:Note that XP Wins the Tests that Count by packeteer · · Score: 1

      I doubt XP has improved the situation all that much.

      It has. Go troll somewhere else. Thats like me saying "well I tried running ventrilo under slackware 7.1 and a 4 year old copy of wine and it didn't work then so i assume it wont work today."

      --
      unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep
    14. Re:Note that XP Wins the Tests that Count by evilviper · · Score: 1
      Thats like me saying "well I tried running ventrilo under slackware 7.1 and a 4 year old copy of wine and it didn't work then so i assume it wont work today."

      No, actually it's nothing like that at all. It's much more like saying "I tried last year's model, and it had thousands of problems, and I doubt they could have fixed them all, both because of the enormity of the problem, and because they've made very little progress over the past 10 revisions."
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  9. Re:Maybe a grain of salt, but it's what I'd predic by Jeffrey+Baker · · Score: 1, Funny

    No, because you spent a week in the first place trying to get the damn thing built, then you wasted the rest of your life arguing with your "friends" about the beneficial effects of -fomit-frame-pointer during your shifts at the Dairy Queen.

  10. Re:Maybe a grain of salt, but it's what I'd predic by ScytheBlade1 · · Score: 0, Offtopic

    Yes.

    BIG yes.

    How to put this: while there may not be a default gentoo install that includes X, let's say this. Gentoo with all of the frills still boots faster and performs faster than any Fedore Core install period.

    I'm not pulling that out of my butt, either, that's from experience. Having both FC and Gentoo installed on identical hardware... gentoo will boot to X far faster than FC can get to a terminal. I have yet to find a distro that matches gentoo in speed, and I'm not saying "pmfg -O3!!three!!11!".

  11. Re:Maybe a grain of salt, but it's what I'd predic by strider44 · · Score: 1

    Look at the PC Mark tests (minus the silly graphics tests and the xp startup, app loading tests). Most of the tests are won by wine probably by only a few fractions of a second - half by less than a percentage point. Besides, they're mostly testing either memory management, which Linux generally does better, or CPU, which Wine has a huge advantage in because it's Gentoo and compiled specifically for the system.

    Gentoo really does feel faster. Compare say a Debian system (which is compiled purely for stability) to a Gentoo system (which is compiled purely for speed) and the Gentoo system will win. However I still use Debian because I kind of like my stability!

  12. Re:Maybe a grain of salt, but it's what I'd predic by gnarlin · · Score: 3, Interesting

    Enough with the gentoo bashing! These compiler optimization options would not be a part of gcc if they did nothing.
    I don't make fun of your hair do I?! So stop making fun of my favorite distro!

    --
    A bad analogy is like a leaky screwdriver.
  13. Re:Maybe a grain of salt, but it's what I'd predic by rolfwind · · Score: 1

    For my linux install, I'm using Ubuntu. I find it pretty slow for most thing (on a P4 2.6) but worse it's constantly swapping in and out of memory (512MB) even though all I do is surf and browse files in the GUI, would Gentoo provide a boost or is the benefit not worth the time invested?

  14. Re:Maybe a grain of salt, but it's what I'd predic by ScytheBlade1 · · Score: 1

    From what I know about Gentoo, as a whole, yes. I run KDE on a 2.4 with 512MB of RAM and have effectively 0 swapping happening (until I fire up a massive Java app, or do like 80 things at once). Gentoo's speed isn't the "-fmad-compile-optimize-h4x", it's just how the OS itself is built and configured by default. I'd say give it a shot. (Though, in all honesty, -O3 actually does help to an extent, but that's another topic.)

  15. Of course wine's better... by Anonymous Coward · · Score: 5, Funny

    ...it makes you feel relaxed, slightly fogged and, in sufficient quantities, happily drunk. Windows, on the other hand, just makes you feel angry and frustrated. Give me wine!

    oh, wait, you were discussing software?

    1. Re:Of course wine's better... by HaydnH · · Score: 1

      "Windows, on the other hand, just makes you feel angry and frustrated."

      Perhaps you should move to the country? =P

      --
      Time is an illusion. Lunchtime doubly so. - Douglas Adams
    2. Re:Of course wine's better... by ltbarcly · · Score: 1

      Windows are ok because it's nice to get sunlight in the morning. Wine is better after dinner with friends, and at night Windows can reduce your privacy.

  16. Strange choice of benchmarks... by Sathias · · Score: 3, Insightful

    Seems a bit strange to me to do a current comparison by using a version of 3d Mark that is 5 years old. If you were going to test out a 6800 on Windows alone you would use 2003 or 2005, the fact they didn't use that one in their Wine comparison suggests to me it couldn't run the later versions at all. The fact that 2000 ran better than under XP, but 2001 ran considerably worse suggests this as well.

    If this is the case, the results in regard to game performance are out-dated at best.

    --
    Blessed are the 1337, for they shall pwn the earth.
    1. Re:Strange choice of benchmarks... by VGPowerlord · · Score: 1

      3DMark 06 is out now, too.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    2. Re:Strange choice of benchmarks... by Anonymous Coward · · Score: 3, Informative

      What you're saying is no secret, newer DirectX versions don't work that well with Wine yet.

    3. Re:Strange choice of benchmarks... by drgonzo59 · · Score: 1
      Good point, I noticed that too. And the reason is that 3DMark05 will probably not work on Wine at all.

      But still, for an open source project to even accomplish what Wine did in the last couple of years is pretty good. I got Cedega Transgaming and it works pretty well too.

    4. Re:Strange choice of benchmarks... by labratuk · · Score: 1

      These are benchmarks done by developers for developers. They're hardly going to spend thousands of dollars going out and buying the new versions of everything just so they can run their tests.

      Also, the point of these benchmarks is they're repeated regularly to compare how wine has changed. To make those results meaningful you have to run the same software from the previous tests.

      --
      Malike Bamiyi wanted my assistance.
  17. amount of work done by Anonymous Coward · · Score: 1, Insightful

    While I assume that the results are correct, they are also substantially meaningless. First, Windows does a lot of work to handle backwards compatibility and boundary cases. WINE often breaks when it encounters really old code or boundary cases. It's easy to be faster when you are doing less work. Second, the functionality may not be exactly equivalent, just close enough. For example, when you have memory copies, one implementation may choose to optimize for very small allocations and be hitting the OS for new zero filled pages for 4k and 8k copies, while the other trades off higher memory use for faster fulfillment of these larger memory requests. Different design choices also mean that different amounts of work are done. Choosing the superior implementation involves looking at more than a small handful of benchmarks.

    1. Re:amount of work done by mmjb · · Score: 3, Insightful
      They are not altogether meaningless. For those who have never tried Wine, the article should give hope of success to those who want to give it a go - albeit more anecdotal than proof.
      It's easy to be faster when you are doing less work.

      To say that Wine developers have it easy is shamefully disrespectful to their efforts. (Unless you take the viewpoint that not having to work with MS code simplifies the work!) For Wine to work at all is commendable - to be (sometimes) faster is truly amazing, IMHO.
    2. Re:amount of work done by Bush+Pig · · Score: 1

      However, you'd have to have done some pretty nifty reverse engineering to make it totally 100% bug-for-bug compatible ...

      Just getting stuff to work at all is quite an achievement, given what you're working with.

      --
      What a long, strange trip it's been.
    3. Re:amount of work done by Anonymous Coward · · Score: 0

      You are an idiot. He wasn't talking about the WINE people, he was talking about the CODE doing less work, because it was missing things. Duh!

    4. Re:amount of work done by mmjb · · Score: 1

      I did get the suggestion was that the code (rather than the developers) was doing less work.

      Although not expressed in the most explicit terms, my feeling is that just because the code might have to do less (and therefore be targetted enough to be faster) it does not mean that the developers have it easy in any way.

  18. Only... by jd · · Score: 1

    ...if the Slashdot editors aren't adding salt to it. (Salted wine? Yuk!)

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  19. Funny statistics by cd_smith · · Score: 5, Interesting

    Anyone else notice the funny stuff going on with the statistics? All the statistics are reported as percentages of the XP value, with higher = better. That means that if wine is "+ 90%", it's performing less than twice as fast as XP. But if it's "- 90%", XP is performing ten times faster!

    So whatever this is measuring (and I concur that it seems to be mostly Linux graphics drivers), it's not reporting the results particularly well.

    1. Re:Funny statistics by typical · · Score: 2, Insightful

      That's not unusual -- choosing the incumbent as a baseline is hardly an unreasonable choice if you are trying to do performance comparisons against a challenger.

      --
      Any program relying on (nontrivial) preemptive multithreading will be buggy.
    2. Re:Funny statistics by rootEToTheIPi · · Score: 1

      I believe that that's called the logorithmic scale.

      --
      When it comes to pastry theft, I take the cake.
    3. Re:Funny statistics by camperslo · · Score: 1

      All the statistics are reported as percentages of the XP value, with higher = better. That means that if wine is "+ 90%", it's performing less than twice as fast as XP. But if it's "- 90%", XP is performing ten times faster!

      That sort of confusion occurs whenever percentages are used. The solution would be to take that same data, and compare the log of the ratios. Or if we follow what's typical in audio and electronics, take ten times the log of the ratio. That's the sort of comparison that's going on when you see the term dB (decibels). Then if you switch which is compared to which only the sign of the result will change. For example if one is twice as fast as the other, instead of it being 200% of the speed or 100% more (or the other being 50% less) you'd get +3 or -3 decibel. When one is ten times the other, the difference is + or - 10 dB (depending which you used as reference, instead of having one 1000% of the other (900% more) or being 10% of the other 90% less.

    4. Re:Funny statistics by labratuk · · Score: 1

      Well done. Have you ever done a class in number theory?

      --
      Malike Bamiyi wanted my assistance.
  20. Re:Maybe a grain of salt, but it's what I'd predic by Theatetus · · Score: 1

    Can someone explain to me why my package manager giving me the option of setting compiler optimizations for packages it builds pisses so many people off? I went Gentoo for the init scripts, anyways...

    --
    All's true that is mistrusted
  21. These tests don't really put Wine in a good light by DigitlDud · · Score: 2, Interesting

    Wine is significantly slower in nearly half of the tests. And getting faster results during memory and CPU tests don't make any sense. The OS shouldn't have anything to do with the results of these tests. Maybe the results are skewed by the Wine's timer implementations?

  22. A grain of salt?? by Anonymous Coward · · Score: 0

    I am not sure that a grain of salt is needed; These numbers are much better that wine has known in the past, but they still are not particularly impressive.

  23. Filesystem, graphics driver by phorm · · Score: 5, Interesting

    Well, my experience with Wine/Cedega has been that for the games and applications that work, the disk-access tends to be faster. Not necessarily because the actual disk is being accessed faster, but because the filesystem (in my case reiserfs) is speedier to read.

    The other wonderful thing I've found about Wine is the graphics abstraction layer. My laptop has a GeForce FX5600 (mobile) card in it. It's actually rather spiffy for most games still, but sucked ass at Battlefield 2 in windows, popping up the warning that my graphics drivers were out of date. Well, it seems that the drivers are tied to the laptop in windows to co-habitate with the power-saving etc etc... so I couldn't update from the official NVidia ones. And of course, my laptop vendor doesn't offer updates for anything over a year old it seems.

    In linux, however, the normal NVidia accelerated driver works. The game runs on that faster than in windows, and with better detail levels. I don't know if it's just that the Cedega HAL does a better emulation for the software bits, or if it's due to the more-up-to-date driver, but it's a much less painful experience in Linux.

    Lastly, my soundcard. SB Live 5.1. Abit dated, but with livedrive still a very nice functional card, except that the windows drivers will eventually/randomly freeze in most directX intensive games. Running in linux... no problemo. That's actually why I switched to Cedega/Debian almost completely (too many losses in Warcraft from lockups).

    1. Re:Filesystem, graphics driver by Anonymous Coward · · Score: 0

      Heya bud, have you tried the KX soundblaster drivers in windows. I have exactly the same sound card and since switching to this alternative driver set i have never had any issues.

      http://kxproject.lugosoft.com/index.php?skip=1

      Regards

    2. Re:Filesystem, graphics driver by strikethree · · Score: 1

      Well, it seems that the drivers are tied to the laptop in windows to co-habitate with the power-saving etc etc... so I couldn't update from the official NVidia ones. And of course, my laptop vendor doesn't offer updates for anything over a year old it seems.

      I had a similar problem with a Toshiba laptop that I owned. I merely found a more recent model of laptop with the same chipset in it and downloaded those drivers instead. Worked flawlessly.

      strike

      --
      "Someone needs to talk to the tree of liberty about its ghoulish drinking problem." by ohnocitizen
    3. Re:Filesystem, graphics driver by Tarwn · · Score: 1

      Oddly enough I get the same popup message when I start the game on my 7800GTX. I didn't get the message on my ATI 9700 Pro.
      Granted my 7800GTX drivers are out of date because I don't like running bleeding edge when I'm already getting a 90+ framerate (my ATI were up to date because 25fps was painful), but I'm willing to bet that a large part of the problem is just the fact that BF2 is a beast.
      My older windows box would consistently gain 10fps for several days after a defrag (avg of 35fps), only to fall off with time to an avg in the low 20's. A total uninstall, defrag, reinstall, defrag actually improved it by about 15-20fps from the lower average for a few days.
      HL2 looked beautiful.

      So basically what I'm saying is that BF2 may not be the best candidate for comparison. It's got a boatload of outstanding bugs, is a beast when it comes to hardware requirements, and seems to have some odd scaling issues with certain chipsets.

      --
      Whee signature.
  24. Re:Maybe a grain of salt, but it's what I'd predic by TubeSteak · · Score: 4, Funny
    I don't make fun of your hair do I?!
    Look, I know I need a haircut, but you didn't have to get personal about it.

    Sorry if I'm a bit sensitive about this, but Slashdot is the last place I expected to get a hard time about my hair.
    --
    [Fuck Beta]
    o0t!
  25. Missing the most crucial test by Chrax · · Score: 2, Interesting

    The real question on everybody's mind is: how well does it run Counter-Strike 1.5? I didn't see that test on there.

    1. Re:Missing the most crucial test by horza · · Score: 1

      The real question on everybody's mind is: how well does it run Counter-Strike 1.5? I didn't see that test on there.

      I agree. It's the only reason I have a Windows partition. Can people please post any Wine vs XP benchmarks they have, along with their machine specs! Also for CS:Source, if anyone has it working. Thanks.

      Phillip.

    2. Re:Missing the most crucial test by theArtificial · · Score: 0

      You'll need Win32 Codecs (for vent).
      Ventrilo guide using Cedega. I am not having luck with getting ventrilo working under WINE (the sound devices).
      Steam guide for CS:S & HL2.
      I've had it working on SUSE10. No luck on bsd (due to ATI drivers :|)

      --
      Man blir trött av att gå och göra ingenting.
    3. Re:Missing the most crucial test by idonthack · · Score: 1

      I played Half-Life 2 on Cedega and it worked very well. Definitely worth the $5/month fee for an update subscription. I opened up CS:Source to see if it worked but I never tried anything past the menus, although I'm sure it plays great.

      --
      Why is it that when you believe something it's an opinion, but when I believe something it's a manifesto?
  26. Re:Maybe a grain of salt, but it's what I'd predic by Bios_Hakr · · Score: 2, Informative

    The transition from Debian-based systems to Gentoo will be fairly painless. Just understand that it may be several days before you get a working system. My main computer is a dual-boot for WinXP and Gentoo. During the install, the family had to live without being able to access WinXP for almost 5 days. Of course, this was on a mid-range AthlonXP with 256MB RAM. I have (in boxes at the moment) a new dual-core Athlon. I expect it to take about 48 hours from fdisk to KDE.

    There are precompiled packages avalible to speed things up, but where's the fun in that.

    Yeah, Debian to Gentoo is quite easy. Just use "emerge" vice "apt-get".

    --
    I'd rather you do it wrong, than for me to have to do it at all.
  27. DirectLinux by MrNybbles · · Score: 2, Insightful

    The Linux Kernel has some graphics support but neither the Kernel nor the X Window System are geared for fast 3D graphics. DirectX is good at getting around using the slower Windows GDI. DirectX is one of the few things Microsoft does somewhat well. (Insert joke here about Directx 9 and taking nine trys to get DirectX right.)

    I have a feeling that unless some major changes are made to the X Window System (and maybe Linux drivers) that WINE will not catch up with WindowsXP and DirectX, but that just means I would need a faster computer.

    WINE doesn't need to be the fastest. As long as it will run my older games (which Windows 2000 does not always do well) it may be more useful to me than an actual install of Windows.
    ---
    This is just my opinion, please don't flame me just because you like Windows.

    --
    Losing faith in humanity one person at a time.
    1. Re:DirectLinux by Anonymous Coward · · Score: 0, Troll

      You know, you should probably have held off on your comment until some future date when you knew what the hell you were talking about.

    2. Re:DirectLinux by John+Betonschaar · · Score: 1

      Why is this modded 'insightful'? This might have been the case 10 years ago, but there's direct rendering in the drivers for most chipsets generally used for gaming nowadays you know... Except for the Nvidia chipsets but their closed-source drivers implement their own direct-rendering subsystem and are actually benchmarked faster than the Windows drivers... If vender support would be a little better (especially from ATI) then Linux would actually be a better 3D/gaming platform than Windows.

      Also, there's projects like DirectFB, Mesa Solo and whatnot for direct graphics without X... And wrappers around that like SDL that work seamlessly between X/non-X...

    3. Re:DirectLinux by Anonymous Coward · · Score: 0

      DirectX dont access hardware through GDI, that would be sluggish. DX access directly to hardware by a driver implemented HAL.

    4. Re:DirectLinux by octopus72 · · Score: 1

      Future of 3D in wine is grey because:
      a) linux driver for non-nvida cards mostly suck. OSS DRI drivers are good, but still lacking some pieces and lack dirty optimisations (which ati and nvidia use heavily in their proprietary drivers for last bit of performance - kids usually buy cards that win on 3dmarks). Some important OGL extensions are still unaccelerated in linux drivers - there are probably some direct3D abilities which OGL doesn't cover or appropriate extensions aren't well supported for now (e.g. FBO's), or simply not suitable for translation. Graphic card memory tests in wine are much slower, probably for something like that. Theoretically best way is to have directX reverse engineered and implemented in linux drivers, but I hope noone will spend too much time on that, maybe only add some specific new extensions to MESA if really needed for better support and speed.

      b) DirectX to OpenGL translation takes some performance away. Cedega has much more advanced D3D translation for now, and this certainly can be improved.

      c) Copy protections are BIG issue. Starforce 3 especially will be impossible to run, maybe with heavily hacked kernel, or only if you run virtualised windows kernel in parallel. But it isn't a problem as with new processors you will be able to run windows with XEN3 and play games with full performance in windows without rebooting. Yeah, you can try cracks if they exist, but starforce is practically uncrackable for now. Too bad game developers tend to go windows/D3D route so much, maybe PS3 can change that and bring us loads of OGL games, not only FPS shooters. Games using OGL have better chances of being ported to Linux. MS on the other side is trying to make OpenGL obsolete on Windows, now that they have powerful enough 3D API.

    5. Re:DirectLinux by labratuk · · Score: 1
      I have a feeling that unless some major changes are made to the X Window System (and maybe Linux drivers) that WINE will not catch up with WindowsXP and DirectX
      I have a feeling you don't know much about the subject and so you're just picking on the components that are the standard whipping boys for other people who don't know what they're talking about.

      And so we have this huge cyclical myth propogating that for instance 'X sucks'.
      --
      Malike Bamiyi wanted my assistance.
  28. Look it up in the Application DB (was Re:cool!) by Rexifer · · Score: 5, Informative

    I know this is repeat info for most people, but for the newbies...

    There's actually an online application database where people have submitted their experiences/successes in getting Windows apps to run under Wine. If you want to see how well Office 2k3 works under Wine, this'd be the first place to look. Conversely, if you have success running a given Windows app, be sure to submit your experiences. Feedback to the App DB not only helps other Wine users, but is helpful feedback for Wine developers on outstanding compatibility issues.

    The URL is: http://appdb.winehq.org/

    1. Re:Look it up in the Application DB (was Re:cool!) by archen · · Score: 1

      It's strange, but the App db always lists pretty much every version of paint shop pro as working, yet I've spent WAAY to many hours trying to get version 4 or 5 to work. I got a bit fustrated with the entire thing and just gave up. Randomly a few days later I loaded a pirated version of photoshop7 with no problems. Sucks that I can't use the software I paid for =/

  29. 3dMark 2005 by Anonymous Coward · · Score: 0

    Where are the comparissons for 3dmark2005?
    Surely 2000 isnt supported. Wouldnt it be more fair to use a dos emulator? Fits in the same gnere

  30. WINE not a Windows replacement by typical · · Score: 5, Insightful

    Okay, I *like* WINE. It's a great piece of software, and very useful. But it doesn't make Linux a drop-in Windows replacement. If you decide "Gee, I think I should use Linux as a desktop" (I do), then it's icing on the cake if WINE runs something. It's not reasonable to simply expect a given piece of software to run flawlessly under WINE, though.

    --
    Any program relying on (nontrivial) preemptive multithreading will be buggy.
    1. Re:WINE not a Windows replacement by Sterling+Christensen · · Score: 1

      Maybe not, but ReactOS is.

  31. Re:Maybe a grain of salt, but it's what I'd predic by RustyTaco · · Score: 0, Flamebait

    Here you go: http://funroll-loops.org/. In short, it's not that emerge lets you specify options, it's all the cluebats screaming about how awesomely fast -O9 is.

        - rustytaco

  32. no salt, but lies and damned stats by SuperBanana · · Score: 5, Insightful
    while i realise that postings to a dev list shouldn't be taken as gospel, why would a dev list posting of benchmarks be assumed to be doctored?

    Nobody said they were doctored; the slashdot editor said "take it with a grain of salt". I see a lot of reasons to do so:

    • there is no sample size (ie, was each benchmark on each platform run 10 times, or just once?) or variance (if it WAS run 10 times- how much did the results vary?)
    • The benchmarks all have wildly different results. Either the benchmarks are that way normally, or WINE (or Linux) is inconsistent. The data is presented such that, again, we have no clue as to the consistency of the results.
    • In a number of the benchmark categories for PC Mark 2004, Linux is less than 1% faster. Usually that kind of difference is thrown in the "statistical anomaly" bucket, but the developer happily gave it the "green" mark, when it should have received a "grey" (ie, "not clear"). If the sub-1% wins had been thrown out, Windows would have won by at least an equal margin.
    • Equal weight was given to the insignificant "wins", as was the massive failures.
    • The developer breaks down the number of Wine failures into 4 categories, but groups Wine successes into one. As a result, it appears Wine is the overall winner, when in fact Wine was slower in 63 cases, and faster in 67.

    Honestly? The results probably aren't manipulated, but the presentation is very clearly set up with a number of tricks (perhaps without him/her realizing it) to give the impression that Wine "kicked some serious ass", when for the most part, it did horribly.

    1. Re:no salt, but lies and damned stats by VGPowerlord · · Score: 4, Informative

      Not only are the marks of less than 1% thrown into the green category, so are the 0 difference marks. That's right, Wine is marked as a winner if they perform exactly the same.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    2. Re:no salt, but lies and damned stats by Anonymous Coward · · Score: 5, Insightful

      I think the main reason the 1% less is given a green is because this is targeted at developers of WINE, and seeing that wine is 1% as close as real windows means that that area is "done" being optimized. The areas where wine needs to focus are on the cases where WINE is significantly slower. WINE really only needs to be as fast as windows, not faster.

    3. Re:no salt, but lies and damned stats by Lonewolf666 · · Score: 2, Insightful

      The benchmarks all have wildly different results. Either the benchmarks are that way normally, or WINE (or Linux) is inconsistent. The data is presented such that, again, we have no clue as to the consistency of the results.
      My first guess would be that WINE is inconsistent. Especially in the areas where it falls behind. After all, it is still a beta and has not achieved 100% compatibility yet, so the developers might not care too much about optimization at this point.
      But Linux or even Windows are also possible culprits. Maybe the guys at Redmond also have a few sub-optimal routines buried in their codebase?

      --
      C - the footgun of programming languages
    4. Re:no salt, but lies and damned stats by mmjb · · Score: 1
      WINE really only needs to be as fast as windows, not faster.

      I don't altogether agree. I would prefer that the priority should be for Wine to perform best for those applications without a real Linux alternative - and if they run faster than on Windows, that would be superb.

      I don't care how slow some Windows apps run under Wine if there is a decent native Linux solution.
    5. Re:no salt, but lies and damned stats by Savantissimo · · Score: 3, Insightful

      You forgot the really important issue: in 18 of the tests, some pretty important, Wine didn't complete the test at all.

      --
      "Is life so dear, or peace so sweet, as to be purchased at the price of chains and slavery?" - Patrick Henry
    6. Re:no salt, but lies and damned stats by diegocgteleline.es · · Score: 2, Insightful

      Some of those benchmarks are not good because wine is good, but because the underlying platform is good - ej virus scanning, I guess that those are good because linux I/O subsystem is good (unless the guy who did the benchmark didn't told the antivirus to scan the same amount of files)

      Then there's basic stuff that you can't explain - why the "CPU speed" benchmark is better under wine? A CPU test will, uh, do things with the CPU, it will be CPU bound and the windows api shouldn't involved in that code path.

      Also notice that wine doesn't implement the win32 API completely. How you know that, say, "Game 2 - Adventure - Low Detail" tried to detect the card's features and since wine doesn't implement everything the game reduced the game quality to match the capabilities detected under wine? I say this because wine doesn't looks that good in the Quake, UT2004 and GL benchmarks

      Anyway, I do not care how fast wine is. I care about API compliance. This is 2006, Microsoft has rewritten half of the OS with longhorn and I continue without being able to run many windows apps created years ago. Wine is far from being a true windows replacement for windows apps today....

    7. Re:no salt, but lies and damned stats by msh104 · · Score: 1

      well, faster is always nice, but there are tons of stuff to optimize, so when something is just as fast as in windows, it might not need to get the priority of optimisation for some time since it's already doing ok.

    8. Re:no salt, but lies and damned stats by mcvos · · Score: 5, Insightful

      That's probably because this is aimed at developers. It shows in which areas they need to improve. Once Wine is equal to XP in a test, they're done, and should focus on other areas. From that point of view, it makes sense to lump all successes in one category, and distinguish between levels of failures.

      This benchmark isn't a Wine vs. XP contest, it's a test to see if Wine is at least as good as XP, and it failed in 81 categories, which means there's still some work to be done.

    9. Re:no salt, but lies and damned stats by Haeleth · · Score: 4, Funny

      Anyway, I do not care how fast wine is. I care about API compliance. This is 2006, Microsoft has rewritten half of the OS with longhorn and I continue without being able to run many windows apps created years ago. Wine is far from being a true windows replacement for windows apps today....

      I quite agree. Last time I tried Wine it didn't run any of my favourite Windows applications. I'm not talking crappy shareware utilities that I can learn to live without - I'm talking showstoppers like OpenOffice.org, Firefox, and Cygwin, all the really critical tools I use every day.

      Until Wine can adequately run programs like that, I'm sadly going to be stuck using Windows. :(

    10. Re:no salt, but lies and damned stats by stoborrobots · · Score: 2, Insightful
      You forgot the really important issue: in 18 of the tests, some pretty important, Wine didn't complete the test at all.


      If I read it right, Wine didn't finish 15 of the tests, and Windows XP didn't finish 3, leading to 18 "no-comparsion" blue results...

      But yeah - that Wine should crash out on a DivX compression or a Web Page Rendering(??!!?) test is ... strange.
    11. Re:no salt, but lies and damned stats by RalphSleigh · · Score: 1, Insightful

      Maybe you should run the linux version of firefox and openoffice?

      No? Oh well..

      --
      Come as you are, do what you must, be who you will.
    12. Re:no salt, but lies and damned stats by bhtooefr · · Score: 1

      joke

            noun 1 a statement made or short story told in order to cause amusement. 2 a trick played for fun. 3 informal a ridiculously inadequate or inappropriate thing.

    13. Re:no salt, but lies and damned stats by Anonymous Coward · · Score: 0

      *whoooosh*

    14. Re:no salt, but lies and damned stats by Crayon+Kid · · Score: 1, Redundant

      I quite agree. Last time I tried Wine it didn't run any of my favourite Windows applications. I'm not talking crappy shareware utilities that I can learn to live without - I'm talking showstoppers like OpenOffice.org, Firefox, and Cygwin, all the really critical tools I use every day.

      Why on Earth are you putting emphasys on Wine not being to run things which already have Linux native ports?

      --
      i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
    15. Re:no salt, but lies and damned stats by Anonymous Coward · · Score: 0

      Wine is marked as a winner if they perform exactly the same.

      Uh, duh? Isn't that what wine is supposed to do? The fact that it performed the same was itself an amazing feat and deserving of praise.

    16. Re:no salt, but lies and damned stats by Anonymous Coward · · Score: 0

      Whoosh.

    17. Re:no salt, but lies and damned stats by Minwee · · Score: 2, Funny

      Absolutely. Until you can use Wine to run Cooperative Linux or boot Linux on vmware then the job is only half done.

    18. Re:no salt, but lies and damned stats by rseuhs · · Score: 1
      The way I see it, it's just presented from a developer's point of view:

      Green means "good enough", red means the involved functions need work.

    19. Re:no salt, but lies and damned stats by fitten · · Score: 2, Insightful

      Actually, the wildly faster areas are sure signs that something probably needs to be done as well. How? you say. Well... a function that does nothing but "return" is a lot faster than a function that actually does some work. There are numbers of places where WINE simply does nothing when it should be doing something. Just a guess, but I'd bet that the Windows security model isn't implemented, for example, so no checking/validating (even to whatever level Windows attempts to do it) isn't done.

    20. Re:no salt, but lies and damned stats by Maradine · · Score: 1

      I'm talking showstoppers like OpenOffice.org, Firefox, and Cygwin, all the really critical tools I use every day.

      Ain't trying to be a dick here, but why would you run *any* of those in an emulated environment? OpenOffice and Firefox have excellent native builds, and all Cygwin is doing is de-emulating you back into your (presumably) native GNU environment.

      Am I missing the boat?

      --

      trustedworlds.net - gaming, security, and the gunk that lives in between

    21. Re:no salt, but lies and damned stats by Anonymous Coward · · Score: 0

      Just a guess, but I'd bet that the Windows security model isn't implemented

      That's a feature, not a bug!

    22. Re:no salt, but lies and damned stats by Lehk228 · · Score: 1

      there is little need to implement windows security. linux already has a funcitoning security model and WINE runs on top of linux. once everything else is done and VB apps with weird skins and shaped windows look right, and everything else functions adding in security within WINE may be useful, but as it is now applications running in WINE can be secured from the outside.

      --
      Snowden and Manning are heroes.
    23. Re:no salt, but lies and damned stats by Anonymous Coward · · Score: 0

      What caught my attention was that in the benchmarks WINE did consistently well, but in a 'real' world test (Q3 and UT2004) it consistently lost. I would love to see more tests with real applications, games and other multimedia software, not just benchmark suites.

    24. Re:no salt, but lies and damned stats by Anonymous Coward · · Score: 0

      That's right, Wine is marked as a winner if they perform exactly the same.

      Maybe that's because Wine *is* a winner if it performs exactly the same.

      After all, that's the whole point of running Wine, right? To run your Windows apps *the same*?

      If they had "0% slower" bars for every test (a.k.a., 100% the speed of Windows), I would call that a huge success.

      Now, if this was FOOMARK-2006 running natively on Linux and Windows, then yes, if they were the same, it would be a victory for neither side. But it isn't. For an emulator (yeah yeah, it is or it isn't), doing the same as the original *is* the goal.

    25. Re:no salt, but lies and damned stats by mole0026 · · Score: 1

      Am I missing the boat?

      Yes, yes you are.

    26. Re:no salt, but lies and damned stats by yakovlev · · Score: 1

      It looked to me like many of the tests Wine didn't finish required Windows Media Player, so it's reasonable not to expect Wine to complete those. Wine doesn't include a Windows Media Player replacement.

    27. Re:no salt, but lies and damned stats by Anonymous Coward · · Score: 0

      ... but.. but... Why? Why would you want to run OpenOffice and Firefox in Wine when they run natively? And why run Cygwin when you have the real deal?

    28. Re:no salt, but lies and damned stats by FredFnord · · Score: 1

      Cygwin in Wine! Gawd, I would love to see that. It's so... twisted.

      -fred

      --
      Sign #11 of Slashdot overdose: You see the phrase 'moderate Republican' and you wonder if that would be a +1 or a -1.
    29. Re:no salt, but lies and damned stats by Carnildo · · Score: 1

      But yeah - that Wine should crash out on a DivX compression or a Web Page Rendering(??!!?) test is ... strange.
      Actually, it's quite understandable. The web page rendering uses Internet Explorer, while DivX compression uses Windows Media Player. Those are areas where WINE hasn't done much implementation yet.

      --
      "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
    30. Re:no salt, but lies and damned stats by Anonymous Coward · · Score: 0

      My God, so many thick people here.

    31. Re:no salt, but lies and damned stats by fitten · · Score: 1

      Yes, but leaving out subsystems (or partially implementing them - just take a look at the patch required to get SubSpace Continuum running... functionality, although minor, was left out and this was required for SubSpace to run properly) may cause incorrect program behaviour. Without those systems, WINE won't be compatible with Windows (and it'd be real easy to write stuff so that WINE won't work... just throw in some security subsystem code).

    32. Re:no salt, but lies and damned stats by wolrahnaes · · Score: 1

      You win the WOOSH! award for having the joke that flew right over the most people's heads in a long time.....

      Congratulations. I haven't seen this many people totally miss a joke in years.

      --
      I used to get high on life, but I developed a tolerance. Now I need something stronger.
    33. Re:no salt, but lies and damned stats by wolrahnaes · · Score: 1

      I know one way or the other was being worked on at one time, I think it was WINE on Cygwin. The goal was to be able to run an app in WINE and Win32 side by side to make any differences obvious. I don't recall if it got anywhere, nor do I care to look.

      --
      I used to get high on life, but I developed a tolerance. Now I need something stronger.
    34. Re:no salt, but lies and damned stats by TheoMurpse · · Score: 1

      Wow, the sarcasm airplane just flew right over your head.

  33. Impressive results by Trogre · · Score: 1

    What's more impressive is that he managed to get 3DMark 2001 working at all under Wine!

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  34. Re:Maybe a grain of salt, but it's what I'd predic by hardburn · · Score: 2, Insightful

    They often do things under very specific conditions and are useless elsewhere. If you're not a compiler expert (which I definately am not), it's unlikely you'll have any apreciable performance gain. It's quite possible that you'll see a performance loss if things aren't done correctly. Even an expert may or may not get a gain.

    I love Gentoo myself, but I'm not delusional about performance gains. I do it for the customizability it offers. For instance, last I checked, you could get a Debian package that contained the Perl bindings for Vim, or the Python bindings for Vim, but not both. With Gentoo, I can easily instruct Portage to build in both.

    --
    Not a typewriter
  35. Re:These tests don't really put Wine in a good lig by Rexifer · · Score: 2, Informative

    Presumably, the memory tests deal with the various OS-level Alloc's (HeapAlloc, GlobalAlloc, LocalAlloc, VirtualAlloc, etc...), which include fault protection checking, SACL checking, and other safety features. The reason that Wine performs better is that either they have implemented a faster version of the WinXX memory management APIs, or that the underlying Linux memory management is faster and the cost of the Wine wrapping calls is negligible. Same for the CPU-related tests... Just as memory is a managed resource in the WinAPI world, so is the CPU (also having SACLs/DACLs to check, and threading/fiber management, etc...)

  36. Re:Maybe a grain of salt, but it's what I'd predic by thunrida · · Score: 2, Interesting

    Several days was when there was still stage1. Now that you must start at stage 3 (and later recompile if you like) you are done in 1 day. After you finish kernel, you just emerge x and kde and next morning you are ready to go (just after you configure x). About speed, it is faster that kubuntu (which I used), but it's the other things that made me go back to gentoo.

  37. oops...overwhelming, not overall. by SuperBanana · · Score: 1
    As a result, it appears Wine is the overall winner, when in fact Wine was slower in 63 cases, and faster in 67

    Whoops. That should read "overwhelming", not "overall".

  38. Re:Maybe a grain of salt, but it's what I'd predic by Theatetus · · Score: 4, Informative

    *shrug* same site it was two years ago. Yes, Gentoo is swarming with clueless n00bies; I was a clueless n00bie once and so was everybody else. If it gives them something to play with, keeps their interests, and gets them learning about Linux, it's worth having to deal with "why doesn't -Os -f-unroll-loops work?" when I talk to one (and I try to help them, because plenty of people helped me back in the day -- that's the whole spirit of GNU, right?).

    Seriously, what should n00bies do, then? Gentoo is a largely user-configured operating system with unbelievably simple and hand-holding documentations. Yes, #gentoo is always full of n00bs asking why they can't boot now that they disabled all block devices in their kernel. But then again, that means it's full of n00bs who have configured and compiled a kernel; other distros I've seen say "WARNING WARNING ELITE USERS ONLY" about that. Why? People point out (rightly) that you can install Gentoo and still be an ignoramus. However, if you're actually interested in learning, you can also learn from the installation procedure the commands for fdisk, the options to hdparm, how chroot works, what /etc/resolv.conf is, blah, blah, blah.

    funroll-loops is half-right. Gentoo is not simply a ricer distribution; it's a hobbyist distribution. It's the kit-car of distros. There are plenty of people who are doing the software equivalent of bolting a huge spoiler on their Civic. But there are plenty of us who are just having fun. And, anyways, the point of free software is that we're free to do what we want with it, even if that means being a moronic jackass.

    --
    All's true that is mistrusted
  39. mod parent up by Anonymous Coward · · Score: 0

    sigs outside the sig field should lead to an automatic downmod

  40. Re:Maybe a grain of salt, but it's what I'd predic by Bios_Hakr · · Score: 1

    I know what you mean about "other things". I love never having to deal with RMP hell agian.

    --
    I'd rather you do it wrong, than for me to have to do it at all.
  41. Impressed by Anonymous Coward · · Score: 0

    I've gotta say, I was exteremly impressed when I tried my first taste of real wine. Blender3D ran better in Wine then it did on Windows.

    1. Re:Impressed by Anonymous Coward · · Score: 0

      I've gotta say, I was exteremly impressed when I tried my first taste of real wine. Blender3D ran better in Wine then it did on Windows.

      You should try out the Linux version then! :)

  42. transgaming by spottedkangaroo · · Score: 2, Interesting

    As a longtime transgaming subscriber, I can tell you that wine really does work as well as pictured. However, it uses an absolutely offensive amount of ram while it does so. I don't knwo how closely related the branches are though.

    --
    Imagine if you weren't allowed to use roads because a bus company complained about your driving 3 times. --skunkpussy
    1. Re:transgaming by kwieland+in+stl · · Score: 1

      ... However, it uses an absolutely offensive amount of ram while it does so.

      Wow, they even implemented that windows feature...

  43. Example of distorted statistics by Anonymous Coward · · Score: 4, Interesting

    It does not take a second look to figure out the stats made up.

    1. Most of Wine's wins are in the 0-2% mark. Means nothing except _inconclusive_; otherwise where is the variance, num tests to justify this?
    2. Wine's perf is bad in the tests it lost
    3. Old test suites were used
    4. As some one said, If Wine is 90% faster it means it is 90% faster. If it is 90% slower it means it is 10 times slower!!!

    BUT, what is really impressive is that Wine actually managed to run all the tests. The compatibility is indeed impressive. This benchmark would have been very credible had it not played with the numbers and colors.

    Maybe a troll, but here is my argument against Wine:
    Windows is moving to WinFX. Then it makes more sense to emulate WinFX's API than Win32 API. (WinFX does use Win32 extensively underneath, but why emulate 2 API's??). In the longer term, the answer to Windows compatibility is not Wine, it is MONO.

    1. Re:Example of distorted statistics by VGPowerlord · · Score: 1
      BUT, what is really impressive is that Wine actually managed to run all the tests. The compatibility is indeed impressive. This benchmark would have been very credible had it not played with the numbers and colors.

      It didn't manage to run all the tests. FTA:

      Wine or XP aborted on 18 tests

      The breakdown for that is 3 for Windows and 15 for Wine.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    2. Re:Example of distorted statistics by n0dalus · · Score: 3, Informative

      This benchmark would have been very credible had it not played with the numbers and colors.

      This test was never intended to show up on sites like Slashdot. The page was made with Wine's developers in mind to have a place to watch performance differences between wine versions. Nobody is trying to say Wine is better than Windows. It's not supposed to be a 'credible benchmark' for the purposes some of you are using it. The main idea behind it is so that in future versions of wine we can run these tests again and see how the results changed. How we represent the numbers is not important. What's important to us is how the numbers change over time.

      To reiterate, this benchmark is really for comparing versions of wine against other versions of wine; it is not intended to be a good or thorough comparison between wine and Windows.

    3. Re:Example of distorted statistics by poot_rootbeer · · Score: 1

      Windows is moving to WinFX.

      And maybe in 10 years, it will get there. I still have some Windows software which uses Win3.1 dialogs...

      (WinFX does use Win32 extensively underneath, but why emulate 2 API's??)

      So people can run Windows software that doesn't use the WinFX API's exclusively, of course (and I expect even Office.NET to fall into this category, at least initially).

    4. Re:Example of distorted statistics by DerekLyons · · Score: 1
      To reiterate, this benchmark is really for comparing versions of wine against other versions of wine; it is not intended to be a good or thorough comparison between wine and Windows.
      Then why compare to Windows at all?
    5. Re:Example of distorted statistics by SirTalon42 · · Score: 1

      Because Windows is the base line. If Wine is as fast as Windows in a benchmark the devs know that they don't need to focus on that, if Wine is at -90% they know theres still a lot to do there. This isn't the first version of the benchmarks, I'm not sure how many revisions there have been, but I remember the benchmarks going back quite a while (I never knew they were being updated till I read about the new ones in Wine's Weekly Newsletter). It is meant to compare Wine against Windows, but only for use by the dev's.

  44. Re:Maybe a grain of salt, but it's what I'd predic by ZenShadow · · Score: 1

    In my experience, it's not the -funroll-my-toilet-paper type of options. It's more the general lack of bloat in Gentoo that makes it faster.

    I used Fedora, Debian, and others for many years, having resisted Gentoo due to time constraints (I had better things to do than compile an entire distro), but then one day I had some free time and tried it.

    The lack of RedHack's Gnome customizations was enough for me to be converted. It's *amazing* how much faster Gnome runs without all the useless RedHat garbage cluttering up memory and chewing CPU cycles here and there.

    On the other hand, you really have to know what you're doing to set up Gnome properly with everything working "as advertised."

    Now I use it on servers at work because it's actually configurable enough to handle our rather unique environment without rewriting half the init scripts.

    --S

    --
    -- sigs cause cancer.
  45. Re:These tests don't really put Wine in a good lig by Jeffrey+Baker · · Score: 1

    Or it could be that WINE have implemented HeapAlloc etc as just plain old malloc without any ACL checking at all.

  46. Re:Maybe a grain of salt, but it's what I'd predic by Al+Dimond · · Score: 1

    There are a number of reasons that might be the case, such as the way bootscripts are done and what types of services are started. My desktop machine is an Athlon XP 2100+ with a gig of RAM running Gentoo and it boots to a command prompt significantly slower than my laptop, which is a P3 700, 192MB RAM, running FreeBSD.

    Obviously the laptop has a much simpler hardware config, less services that it needs to run, and because I reboot it fairly often I actually bothered to clean out the rc files. In Gentoo at least I know that I want all those things started. With FC you might be probing parts of the hardware config that you have hard-configured into Gentoo, or starting sendmail, more hefty logging facilities, automounters or whatever. Actually, it wouldn't surprise me if FreeBSD's bootscripts are lighter-weight than Gentoo's in general.

    I'm not discounting the booting speed advantage of Gentoo over, say, FC or Ubuntu. But take that Gentoo machine and make it run everything that FC runs on startup, and I bet a lot of the advantage goes away. Boot speed won't really tell you much about how the system will perform other tasks (as you can imagine, other than booting my laptop is much, much slower than my desktop).

  47. Configuration? by darkain · · Score: 1

    what drivers where used? and what driver and OS configurations where used? and what about features? since a product has less features, it should have less to process, hence it running faster. how fast can windows 95 paint a window to the screen compared to windows xp? ya, i know, its a lame example, but its true.

  48. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  49. suckahs by Anonymous Coward · · Score: 0

    All the gamers I know play 1 game all year, which is cool and all but over the time they spend 1500 bucks on motherboard, cpu, ram, video card, power supply, and all the other stuff... get like 30 more fps over acceptable ... super pro delux internet feeds and /still/ bitch about lag. I doubt they would be very interested in Wine. OTOH, I just play to keep in touch and so I can still be involved in their conversations and get their old (bad assed) video cards and stuff.

  50. Not that bad, not that good - It's a start by Cef · · Score: 1

    The tests are ok. Sure we need more (like later versions of software, assuming that it runs of course), but at least it's a start. I look at all the green's as a "these bits work ok" and anything worse than yellow as "this needs a lot of work". Beyond that, I wouldn't read anything else into it.

    We also need to know what version of the NVidia driver was used, on XP and on Linux, as this will make a huge difference. It'd also be good to know some other stuff about each setup (eg: DirectX version and patch level under XP, kernel version under Linux), etc.

    As for these older tests not being significant: Bullcrap! So many games use bits of DirectX and the like that have been in there since well before 2000. While the tests are not the be-all and end-all, they are the building blocks that need to be completed before we jump headlong into the next level. Lets not get ahead of ourselves.

    I mailed the guy with a few criticisms and ideas, so maybe we'll see some more info shortly. Note that I did this politely - people tend to listen to polite suggestions, as compared to knee-jerk style frustrated yelling and bitching.

  51. On related news... by Anonymous Coward · · Score: 3, Informative

    The latest LugRadio show ( http://lugradio.org/episodes/43 ) features a very interesting interview of Jeremy White about Wine.

  52. Don't be silly by something_wicked_thi · · Score: 5, Insightful

    These results aren't presented to try to make Wine look better, nor is the author, consciously or unconsciously, trying to make it appear faster. These results simply were not meant to be used to say that Wine is better than Windows, and only Slashdot would try to make it appear that way. The real point of these comparisons, as is apparent if you read the Wine weekly summaries, is to give the Wine developers an idea of what areas need to be improved, and what areas are adequate. Green obviously means "at least as fast as Windows", which means that it's good. There is no point in grouping them any other way, since they don't care if they are 50% better or 1% better. Also, your criticisms of why this benchmark doesn't give a good idea of the relative speeds of Wine and Windows are quite wide of the mark (though they are valid complaints). The real reason why this benchmark cannot be used to gauge relative speeds is that it doesn't cover real world work loads. They measure a very small number of very specific things, mostly related to gaming and 3D performance. The benchmarks they ran that weren't related to that were designed to test the *hardware* speed, not the speed of the API. The Wine developers know this, and that's what the comment about taking it with a grain of salt means. It's probably adequate to give a rough idea of what parts of Wine need to be improved, but it is nowhere close to a comprehensive comparison of the speed of Windows and Wine, and was never meant as such.

    1. Re:Don't be silly by something_wicked_thi · · Score: 1
      Damn it, why can't Slashdot put in

      tags whenever I use two newlines like all other message boards? Sorry for the big blob of text.

    2. Re:Don't be silly by Anonymous Coward · · Score: 0

      Post as "Plain Old Text" and it does.

    3. Re:Don't be silly by Anonymous Coward · · Score: 0

      Damn it, why can't idiots use the "Preview" button?

  53. Flight Simulator by Cowclops · · Score: 1

    Nah, they missed the most important test.

    Does it run Flight Simulator 1.0?

    1. Re:Flight Simulator by mrchaotica · · Score: 1

      Probably not... but then again, neither does Windows XP. Flight Simulator 1.0 was a DOS program!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    2. Re:Flight Simulator by T-Ranger · · Score: 3, Informative

      You missed the subtle point of the post. MS Flight Simulator was once the de facto IBM PC standard compliance test.

    3. Re:Flight Simulator by mrchaotica · · Score: 1

      Oh, I see. I guess I'm a little too young for that, then (my first copy of Flight Simulator was version 3 or 4 (maybe last DOS version?)).

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  54. DirectX: vendor-lock-in and avoid paying to SGI by more · · Score: 1, Interesting
    DirectX was built for two purposes in the first place: vendor-lock-in and to avoid paying to SGI. Microsoft stopped OpenGL development by interfering with the OpenGL ARB, in order to catch up with their own solution, DirectX.

    Yes. Vendor-lock-in is what Microsoft generally does well.

    --

    -- Imperial units must die --

    1. Re:DirectX: vendor-lock-in and avoid paying to SGI by TheNetAvenger · · Score: 3, Informative

      SGI. Microsoft stopped OpenGL development by interfering with the OpenGL ARB, in order to catch up with their own solution, DirectX.

      Love the 'personal' theories...

      Microsoft did not even have an alternative to OpenGL in development when Microsoft pulled out of OpenGL. Microsoft pressed for OpenGL to enhance low level hardware support with intention of doing more than cad/engineering and supporting 3D rendering environment conducive to gaming and directly access video card hardware for gaming.

      OpenGL told Microsoft to go pound sand, and that OpenGL was not for games or going to support direct hardware features for gaming.

      Microsoft started stringing together a set of technologies that were called WinG, mainly a 2D form of rendering with plans for a new model that was a 3D rendering solution with direct video access on par of what the current DOS based games were used to, but in the Windows environment.

      If OpenGL would have not 'played catch-up' to DirectX, and instead took Microsoft's recommendations at the time Microsoft was a big OpenGL proponent, there would never have been a DirectX, as OpenGL would be what Microsoft would be using, and contributing to instead.

      The vendor lock in, was just a bonus in the long run, it was others involved in OpenGL that made the choice to not go for gaming.

      But you can say it was about paying to SGI or a diabolical plan to take control of the gaming industry, but the facts don't support it.

      The second part of this topic is that DirectX evolved to be more than an alternative to OpenGL, as it encapsulates everything from input devices, networking, to sound and voice.

      When DirectX first existed it was the only game in town for any standardized interface to video for accelerated graphics in gaming. Now it is more than just Video...

    2. Re:DirectX: vendor-lock-in and avoid paying to SGI by will_die · · Score: 1

      Microsoft did not even have an alternative to OpenGL in development when Microsoft pulled out of OpenGL.
      No, the only way this is true is if you consider the DirectX 10(coming maybe with vista) is the Microsoft alternative to OpenGL. Microsoft pulled out of OpenGL in March 2003 by that time DirectX 9.0 had already been released.

    3. Re:DirectX: vendor-lock-in and avoid paying to SGI by Jerry+Coffin · · Score: 1
      Love the 'personal' theories...

      I do too -- and yours are better than most.

      Microsoft did not even have an alternative to OpenGL in development when Microsoft pulled out of OpenGL.

      Microsoft was a member of the ARB until early 2003. Offhand, I don't recall whether DirectX 9 was truly "released" by then, but it had been available at least to developers for quite a while at that point.

      Microsoft pressed for OpenGL to enhance low level hardware support with intention of doing more than cad/engineering and supporting 3D rendering environment conducive to gaming and directly access video card hardware for gaming.

      What sorts of things that games needed did the ARB (supposedly) tell Microsoft they wouldn't support? I seem to remember going through situations like this Usenet thread discusses.

      If you look really carefully, you can find a few points in time at which DirectX has supported something that was slightly more difficult with OpenGL -- just for one example, rendering to a bitmap (instead of the frame buffer). None of these, however, was anything that the ARB told MS (or nVidia, ATI, et al) to pound sand on or anything like it. Quite the contrary -- OpenGL has always had a mechanism for extensions that let people integrate new capabilities into the existing framework. In addition, the ARB has moved reasonably quickly to provide (usually cleaner versions of) those capabilities in the core of newer versions as well.

      Microsoft started stringing together a set of technologies that were called WinG, mainly a 2D form of rendering with plans for a new model that was a 3D rendering solution with direct video access on par of what the current DOS based games were used to, but in the Windows environment.

      Well, you're at least partly right. WinG was certainly 2D in nature -- in fact, its basic idea was only to allow fast display of device independent bitmaps (as opposed to the device dependent bitmaps they'd primarily supported previously). It was not, however, replaced by DirectX or OpenGL or anything similar. Its real replacement was CreateDIBSection, which is still part of GDI (and takes relatively little advantage of graphics hardware).

      If you really want to look into the history of OpenGL vs. DirectX, I'd recommend going to Paul Hsieh's OpenGL Vs. DirectX page. This has blow-by-blow documentation of things that were really happening at the time, including references to other articles, Usenet threads, etc., making it pretty easy to track down things like dates, so you have an idea of when things happened in relation to each other (such as the fact that all of this happened long before MS quit the OpenGL ARB).

      When DirectX first existed it was the only game in town for any standardized interface to video for accelerated graphics in gaming. Now it is more than just Video...

      This much is true -- OpenGL has stuck to more or less the UNIX philosophy -- do one thing, and do it well. Unsurprisingly, DirectX seems to follow the Microsoft philosophy much more, attempting to integrate everything. Unfortunately, (as usual) it only does the job halfway -- on one hand, DirectX has bits and pieces of almost everything, but on the other, the pieces aren't really very well integrated together. It's branded as a single "product", but it's really separate pieces with little real integration, and even with quite a few dissimilarities between the pieces that are entirely gratuitous.

      --
      The universe is a figment of its own imagination.
    4. Re:DirectX: vendor-lock-in and avoid paying to SGI by TheNetAvenger · · Score: 1

      Microsoft was a member of the ARB until early 2003

      You base your entire point around this; however, my point was not Microsoft's ARB membership, but OpenGL support.

      Microsoft was a strong proponent of OpenGL and even added OpenGL to NT natively in the early 90s.

      When Microsoft realized OpenGL had no intention of supporting new hardware and gaming concepts, Microsoft jumped ship with DirectX to provide these features.

      You can wrestle your argument on the point of Microsoft's official ARB membership, but the fact is OpenGL would NOT BE providing what it is doing today if Microsoft hadn't jumped and created DirectX demonstrating the need for gaming and upcoming popularity on the PC.

      Just as Microsoft has with the WPF, no one else was writing high level language 3D interfaces, this has left a big world open once again for Microsoft.

      I.E. Windows developers can write a 6 lines of XML and get the benefits of hardware 3D acceleration and offer a new level of productivity and features for even common business or consumer level applications.

      As for the link you provide, this is a very old story of ID and their adoption of OpenGL instead of DirectX, years ago, with veiled references to 'intel's disdain' of the way DirectX worked, which was nothing more than speculation even then.

      The point that the link you provide misses about OpenGL and DirectX is partially based on the timeline this article is written around. And at that time do you even realize the limited functionality that was hardware support in GPUs? Do you realize how important CPU was with games even with the most advanced GPUs at the time?

      Today the GPU is more the result of the limitations of CPU based pushing and rendering, and instead of trying to even 'work with' the CPU, they are designed to replace 98% of the visual functionality. Where back then it wasn't even 50% of the rendered scene.

      You can also find people at both NVidia and ATI that very much credit Microsoft's work in both the hardware specifications and DirectX implemention for moving the whole 3D and gaming world forware, even WHAT OPENGL has been FORCED to bring to the table to remain a non-windows competitor.

    5. Re:DirectX: vendor-lock-in and avoid paying to SGI by Jerry+Coffin · · Score: 1

      You base your entire point around this; however, my point was not Microsoft's ARB membership, but OpenGL support.

      Microsoft was a strong proponent of OpenGL and even added OpenGL to NT natively in the early 90s.

      When Microsoft realized OpenGL had no intention of supporting new hardware and gaming concepts, Microsoft jumped ship with DirectX to provide these features.

      So when exactly do you propose that this took place? The previous post claimed that it was what led to WinG, which came out in 1994. Microsoft, by contrast, at least claimed (and provided reasonable backing for the claim) that they were serious about supporting OpenGL substantially later than that -- e.g. in a rather long Usenet thread years after that, Stephen Wright talked about Microsoft's wonderful new OpenGL 1.1 implementation.

      You can wrestle your argument on the point of Microsoft's official ARB membership, but the fact is OpenGL would NOT BE providing what it is doing today if Microsoft hadn't jumped and created DirectX demonstrating the need for gaming and upcoming popularity on the PC.

      Any claim that the world would have been different if X had not happened is obviously speculation, not fact. If you want to make such speculative claims, the very least you need to do is provide some information about the things you think Microsoft originated, that were then adopted by OpenGL. Right now, your claims are not only speculatively, but seem to be entirely unsupported as well.

      If you actually want some facts, try reading through this Usenet thread. The posts from Stephen Wright and Mark Kilgard are particularly interesting WRT the Direct3D vs. OpenGL question.

      Just as Microsoft has with the WPF, no one else was writing high level language 3D interfaces, this has left a big world open once again for Microsoft.

      What's supposed to be so innovative about WPF again? I seem to have missed whatever it is. Specifying graphical objects to be rendered is certainly nothing new -- that goes at least as far back as Renderman. Remote rendering isn't new either; that's been around since VRML. Doing it in XML isn't new either -- Adobe's SVG has done that for a while too. What are we left with? I don't see a lot beyond support from Microsoft, ensuring that it'll be widely used.

      And at that time do you even realize the limited functionality that was hardware support in GPUs? Do you realize how important CPU was with games even with the most advanced GPUs at the time?

      If you bother to read the thread cited above, you'll note that I've not only read it now, but clearly read it at the time (having posted to it).

      One of the links I previously provided talked about the fact that at the time, Direct3D didn't support hardware acceleration of T&L -- even though cards that supported it were available. As for knowing what was done in software, consider my post from a few years later discussing exactly that.

      The bottom line is pretty simple: for your argument to make sense, DirectX would have to have consistently supported 3D capabilities of popular hardware well before OpenGL did so. That's simply not the case. In a few cases, it's been ahead, but in other cases it's been behind. OpenGL has been revised far fewer times than DirectX (seven vs. about a dozen) but in most cases, the larger number of revisions has not really reflected adding new capabilities more quickly -- it has primarily reflected features being defined at en

      --
      The universe is a figment of its own imagination.
    6. Re:DirectX: vendor-lock-in and avoid paying to SGI by TheNetAvenger · · Score: 1

      What's supposed to be so innovative about WPF again? I seem to have missed whatever it is.....I don't see a lot beyond support from Microsoft, ensuring that it'll be widely used.

      Wow, good luck with that. Now I understand where your keen understanding and insight comes from.

      You couldn't take two minutes to actually look at the technology other than the 'news' blurbs or your attitude wouldn't be so eager to downplay its relevance. Even the Sept PDC information would be a jaw dropper to you if this is your insight into WPF.

      It is people like this that one day realize the world changed and go, wow, I didn't see that coming.

      Anyway, good luck and hope the world doesn't continue to pass you by.

    7. Re:DirectX: vendor-lock-in and avoid paying to SGI by Jerry+Coffin · · Score: 1
      It is people like this that one day realize the world changed and go, wow, I didn't see that coming.

      ROFL. It's far more common for me to see the latest and greatest fad die an ignominious death, and say "Wow, I didn't see that going." Unfortunately, that hint of sarcasm in my voice as I'm saying it usually ruins the effect.

      --
      The universe is a figment of its own imagination.
    8. Re:DirectX: vendor-lock-in and avoid paying to SGI by TheNetAvenger · · Score: 1

      ROFL. It's far more common for me to see the latest and greatest fad die an ignominious death, and say "Wow, I didn't see that going."

      Oh, so you are a JAVA developer then... *wink*

      Just funning.

      Take Care,
      TheNetAvenger

  55. almost classic by dchallender · · Score: 2, Insightful

    Looking at the results - "Grammer Check"
    Shame it was not "Spelling Check" but on still quite amusing.

    In all seriousness, interesting and makes me want to revist Wine as it looks a lot better than when I last tried it (given I run pretty low spec hardware, performance is key rather than stability).

    Though I do think "Wine or XP aborted on 18 tests" was a bit cheeky as it was 3 XP aborts, 15 Wine aborts...

  56. Re:Maybe a grain of salt, but it's what I'd predic by macshit · · Score: 4, Interesting

    From what I know about Gentoo, as a whole, yes. I run KDE on a 2.4 with 512MB of RAM and have effectively 0 swapping happening (until I fire up a massive Java app, or do like 80 things at once). Gentoo's speed isn't the "-fmad-compile-optimize-h4x", it's just how the OS itself is built and configured by default

    Um, the question was whether he'd see a marked improvement changing from debian/ubuntu -- and given that Debian uses the same kernel as gentoo, and the same apps, it's very unlikely that there will be any difference in performance unless it comes from the "-fmad-compile" options. [In my experience, the -fmad-compile won't make any difference in practice either unless you're talking about very specialized balls-to-the-wall code like scientific computing or whatever.]

    The "0 swapping happening" is an attribute of the linux kernel, not the distro; I notice the same thing under debian (in fact I generally see no disk i/o at all unless I'm writing files, because of linux's excellent disk caching). If the OP is having problems with swapping it means that he doesn't have enough memory for the apps he's using; a distro change is unlikely to help with that.

    --
    We live, as we dream -- alone....
  57. beige boxes by jaavaaguru · · Score: 1

    Is there any way to make Windows apps run on PPC or SPARC hardware, possibly using Wine in conjuction with something else? I like the idea of Wine, but I have no x86 stuff in my room. Not even sure if I'd have a use for it, but it would be fun to play with.

    1. Re:beige boxes by Anonymous Coward · · Score: 0

      Use qemu to run wine and emulate x86.
      See http://fabrice.bellard.free.fr/qemu/qemu-doc.html# SEC49 for more information on running the qemu userspace emulator with wine.

    2. Re:beige boxes by jaavaaguru · · Score: 1

      Exactly what I was looking for, thanks :-)

  58. Re:Maybe a grain of salt, but it's what I'd predic by Anonymous Coward · · Score: 0

    Well, I don't understand why people here are talking about direct x, 3dmark or games. Yeah, I agree that games are fun (and maybe easier to get figures like fps or something), but for me (and I think many others and especially companies) they are not the reason to delay my transition from windows to linux. I think different productivity and office programs are the real reason that someone might not do the transition. If they work well, then people start concidering switch. And most of them are starting to work really well, even install very easily (with latest wine versions).

    I have dual boot machine, linux and windows. I play around with linux and have it as testing environment for my web server, but everything else I do in Windows. When my Adobe CS2 starts working in Wine as well as in Windows (also my wacom pen tablet, last time I tried pressure and tilt didn't work), then I don't have any reason to work in Windows anymore. My computer would still be dual boot for the few games I play, but I wouldn't need to boot to Windows to work.

    And I think it is similar situation for many companies too. There's some program or some feature of a program that doesn't work in linux (and maybe in wine) too well. Transitioning from program to something else might be a real pain (for example starting to learn gimp, I would have to do that on my own time, my employer wouldn't pay me to learn it, sacraficing my own free time is not an option... even if gimp would do everything I want it to do) for many reasons including those I told.

    I hope some day linux with wine is viable option for me to do transition from windows to linux. It's not now, but maybe in few years.

  59. I thought salt was for tequila by sayanchak · · Score: 1

    Well, now we have salt with wine too.

  60. What do you think reverse engineering is ? by sjf · · Score: 1
    If I rephrase your statement then it's clear that, of course, this is reverse engineering:

    WINE implements the FUNCTIONALITY of the Windows API. It merely provides the same API.

    The implementation is by no means 'published' and therein lies the reverse engineering.

    Reverse engineering does not necessarily mean disassembly or anything remotely dark-hattish.

    1. Re:What do you think reverse engineering is ? by CheeseyDJ · · Score: 1

      Reverse engineering in terms of software involves studying source code to see how it works, typically before producing your own implementation based on what you have learned.

      If the relevant source code was available, there would be nothing dark-hattish about reverse engineering Windows DLLs, but the source code is not availible. So, to reverse engineer any of the Windows code you would first need to decompile the binaries, which is an activity I'm sure most people would consider 'dark-hattish'.

      The WINE developers are producing a new, Linux based implentation for the Windows API, without studying Windows source code -- there is no reverse-engineering involved. They are simply implementing the Windows API.

    2. Re:What do you think reverse engineering is ? by Jon+Pryor · · Score: 5, Informative

      Wine is most certainly a reverse engineering effort. The problem is that you don't fully understand what reverse engineering includes.

      Reverse engineering also includes the following process:

      1. Write test (e.g. figure out some undocumented detail for CreateProcess)
      2. Run test, get results (CreateProcess doesn't format your hard drive)
      3. Write your own code to duplicate the results of the test written in (1)
      4. Repeat 1..3 until complete.

      This is black box reverse engineering. You treat some piece of software as a block box, write tests for it, figure out what the "box" is doing, and recreate that behavior. No decompilation required, no source code required, just lots of tests and ingenuity. This has the benefit that no copyright violations are required (since you never decompile the original program). This process is also used in clean room design, except step 3 is replaced with a documentation step -- instead of code being the result of the process a specification is the result. Compaq did this to reverse-engineer the IBM PC BIOS.

      Wine is most certainly doing this, as it's the only way to determine undocumented connections between various APIs. Mono certainly does this ("what's this member supposed to do, and is Mono's version following that behavior properly?"). Another way to think of this is for bugs -- does this Mono code do what the .NET equivalent code does? If not, we'll get a bugzilla entry for it, and (eventually) fix it. This bug-report/fix cycle can also be considered as black box reverse engineering, since the bug-report is itself a test, through which we can determine what the actual functionality should be.

      Decompilation is generally not legal, since it can lead to copyright violations. Black box reverse engineering is legal, and any attempt to limit black box reverse engineering would kill the interoperability market, since no compatible hardware/software could ever be created unless the original manufacturer permitted it.

    3. Re:What do you think reverse engineering is ? by BostonPilot · · Score: 5, Insightful
      With 30 years as a software engineer, it's only very recently that I've ever seen "reverse engineering" used in the context of reading source code. In the past we called that.... um... "reading the source code". I can understand this interpretation, and it fits in with the general idea of "deduce design by observing details" but I think this particular interpretation trivializes the term a bit. Can you imagine someone saying they "reverse engineered a book" because they read it and understood what the author intended?

      Throughout most of my career, I've understood reverse engineering to be what you do when you DON'T have the source code. I think the wikipedia entry mentions that this is the most common interpretation. It can be extremely difficult and time consuming. I've done it on major projects a few times in my career. It is neither easy nor efficient, but sometimes the only choice you have.

      It's also common to talk about reverse engineering hardware, where the innards of a chip may be deduced by observing its inputs and outputs. I worked on a project at a startup where we had to do that, because the original hardware developers were long gone, and no VHDL could be discovered, yet we had to write drivers for their (buggy) chips in order to make a deadline. At the same company we had to reverse engineer the workings of a (buggy) Fiber Channel PCI card, because the manufacturer would not give us the support we needed to make our deadlines. They were rather surprised when we talked to them about the details of their (proprietary, embedded in an ASIC) DMA engine that we deduced via logic analyzers and oscilloscopes.

      Those projects were SO difficult compared to reading (even obscure) code, that I really think that using the one phrase for both activities is confusing and sometimes even deceptive.

    4. Re:What do you think reverse engineering is ? by sjf · · Score: 2, Interesting

      Well, I don't agree with all of the Wikipedia entry, nor do I agree with your comment implying the necessity of decompilation.

      However, if we're going to take Wikipedia to be gospel, then let's read all of it, including:

      The Samba software, which allows systems that are not running Microsoft Windows systems to share files with systems that are, is a classic example of software reverse engineering, since the Samba project had to reverse-engineer unpublished information about how Windows file sharing worked, so that non-Windows computers could emulate it. The WINE project does the same thing for the Windows API, and OpenOffice.org is one party doing this for the Microsoft Office file formats. [emphasis mine]

      I have no idea if the WINE engineers have disassembled (or as you say decompiled) Windows binaries or not. My point remains that this is not the determining factor in deciding if it is reverse engineering or not: meaning that disassembly is not necessarily a feature of reverse engineering.

    5. Re:What do you think reverse engineering is ? by sjf · · Score: 1

      in lieu of mod points: "Well said sir!"

    6. Re: What do you think reverse engineering is ? by Black+Parrot · · Score: 1

      > Reverse engineering in terms of software involves studying source code to see how it works

      That is simply wrong.

      > The WINE developers are producing a new, Linux based implentation for the Windows API, without studying Windows source code -- there is no reverse-engineering involved. They are simply implementing the Windows API.

      I.e., they are reverse engineering the DLLs.

      --
      Sheesh, evil *and* a jerk. -- Jade
    7. Re: What do you think reverse engineering is ? by CheeseyDJ · · Score: 1

      That is simply wrong.

      Whatever.

      > The WINE developers are producing a new, Linux based implentation for the Windows API, without studying Windows source code -- there is no reverse-engineering involved. They are simply implementing the Windows API.

      I.e., they are reverse engineering the DLLs.


      I completely disagree with this. Simply implementing an API does not constitute, or necessarily involve, reverse engineering.

      Consider JVMs. All JVMs need to implement the same API - compatibility is tested via the Java Compatibility Kit. If your implementation passes the JCK tests, it can be certified as Java compatible.

      At no stage do you need to reverse engineer Sun's reference JVM to produce a new implementation. You just need to produce an implementation which behaves correctly with reference to the published API, and test it using the JCK.

      If the Windows API is published, and I believe it is, there is no requirement for reverse engineering in order to construct a compatible implementation. You just jump several stages in the development cycle - you skip the design stages and move straight to code construction and unit testing, because you already have an API which has been designed and defined by Microsoft.

      Of course, you do not have access to the design documents, so implementation will be non-trivial. Reverse engineering is one way to make progress, but it is not essential - you could create the implementation solely via testing your implementation to check whether it behaves the way the API states it should. That is not reverse engineering. That is testing.

    8. Re:What do you think reverse engineering is ? by MikeBabcock · · Score: 1

      Thank-you for such an intelligent response to the issue.

      --
      - Michael T. Babcock (Yes, I blog)
    9. Re:What do you think reverse engineering is ? by spitzak · · Score: 1

      Just want to back up the other responders. I also have never heard "reverse engineering" as being decompilation like you claim. "reverse engineering" is testing the original, inventing new tests to determine things the original tests did not, and producing a copy that outputs the same results as the tests.

      Decompilation is genearlly called "cloning" if done legally, maybe cracking/hacking if done illegally. I think legally doing it requires walled-off development groups, such as was done for the BIOS. Decompilation is quite impractical for something the size of Windows, and as you mentioned the MS documentation and many programmers familiar with the platform give a huge head start and make reverse-engineering the far-preferred method.

    10. Re: What do you think reverse engineering is ? by Anonymous Coward · · Score: 0

      "you could create the implementation solely via testing your implementation to check whether it behaves the way the API states it should."

      Errr... to some degree this is true. But a couple things. Just to make this clear (I think you understand this as well, but just to make sure) - api's don't equal the source. Some times it's just simple the function, arguments, and what it returns (I might call this reverse engineering - since who know the specifics of the args/return vars). In some cases it may go into a lot of detail, and thus make implementing the api (which I may not call reverse engineering - it gets a little gray, but you still don't have the source, so...).

      BUT, if you go to the wine website they state quite plainly that they don't have api documents for all dll's, and apparently some are misleading.

      So the entire wine project probably encompasses all this stuff (and other cases I'm missing - remember it's a big project). And it certainly does some reverse engineering.

    11. Re: What do you think reverse engineering is ? by OOGG_THE_CAVEMAN · · Score: 1

      "Reverse engineering" is, get this, "engineering" in "reverse."

      Engineers start with a design, more or less formally specified, and end up delivering a product, which may or may not be delivered with complete documentation, or conform to a publically available standard.

      Reverse engineers start with the product, which may or may not have complete documentation, or conform to a public standard, and come up with a design.

      Get it?

      Your metioning that reverse engineers "might not have access to the design documents", and your earlier discussion that involved "reading the source" shows that you have a fuzzy notion about what reverse engineering is.

    12. Re:What do you think reverse engineering is ? by Hard_Code · · Score: 1

      "Decompilation is generally not legal"

      I don't know if can cite any specific law to back that up, but reverse engineering (of which "decompiling" is certainly a strategy) is still, and should always be, legal. Now, BECAUSE of this, most software has nasty decompilation clauses in their EULAs, so you have to agree to them to license the software (although I think it is a open question as to whether you can just NOT accept the license and proceed with the decompilation - as long as you don't ever actually "use" the product).

      --

      It's 10 PM. Do you know if you're un-American?
    13. Re:What do you think reverse engineering is ? by Grishnakh · · Score: 1

      I worked on a project at a startup where we had to do that, because the original hardware developers were long gone, and no VHDL could be discovered, yet we had to write drivers for their (buggy) chips in order to make a deadline.

      I hope they were paying you well. If it were me, I'd be looking for a new job, because that sounds like a company that won't be around for long.

    14. Re:What do you think reverse engineering is ? by BostonPilot · · Score: 1
      It wasn't around for long :-(

      Amazingly, we got the hardware and software to work. And, the customers loved the product. The company simply ran out of money before they could become profitable.

    15. Re:What do you think reverse engineering is ? by Grishnakh · · Score: 1

      Well I imagine so: it can't be cheap paying your engineers to reverse-engineer everything. Unless you're going to charge your customers a bundle to pay for this highly inefficient type of work, it's simply not a workable business model.

    16. Re:What do you think reverse engineering is ? by BostonPilot · · Score: 1
      The company was an unfortunate combination of bleeding edge and inadequate funding. At the time, 100BT Ethernet had just come out, and people were getting 5-6MB/sec over it. We were using Fiber Channel to get gigabit ethernet speeds over the network. There was only one card at the time, from Emulex, and I don't think they considered us worth their effort at first. When we started demonstrating what we could do, they got much more helpful. Certainly had we not reverse engineered their DMA engine, they never would have given us the time of day.

      The other half of the project was the actual server hardware. It was a project another company did, and when it was cancelled they sold the assets for cheap. I think this looked like a good deal to the president and CTO of our company. In retrospect, it was probably a bum deal. We could have done better by starting with PC hardware running an RTOS, and then later done our own boards. At the time, it looked like a cool piece of hardware. Problem was that the CTO didn't perform due diligence.

      I've certainly learned over the years that you almost NEVER want to do bleeding edge, or if you do it needs to be ONE THING, with everything else conservative, and you better have a backup plan too!

      All that said, there are certainly times it's cheaper or faster to reverse engineer someone else's work, rather than try to reinvent it from start.

    17. Re:What do you think reverse engineering is ? by Anonymous Coward · · Score: 0

      This is what people mean when they say "reverse engineering" source code. Frankly, it might be easier to figure out the logic of some of those... constructs... by observation than by reading them.

      If you've never seen such horrors, praise God for it--they don't often seem to be low on submissions over there :(

    18. Re:What do you think reverse engineering is ? by Anonymous Coward · · Score: 0

      Since it can lead to copyright violations (seeing the code means you might use it either conciously or sub-conciously,) is there any point to doing that?

      Although I suppose, maybe you could document what it does and leave it to someone else to do the programming.

    19. Re:What do you think reverse engineering is ? by Anonymous Coward · · Score: 0

      Can you imagine someone saying they "reverse engineered a book" because they read it and understood what the author intended?

      Woiuldn't they also have to rewrite the book aswell before they could say that?

  61. Re:The benchmarks all have wildly different result by Anonymous Coward · · Score: 0

    It doesn't seem to me the benchmarks give wildly different results - it seems that exactly the benchmarks requiring lots of memory where running slower. I would expect wine to consistently do well if one were to run it on a machine with twice the RAM of a similar windows machine.

    What I find missing in the benchmarks are "boring" benchmarks for other tasks but graphics.

  62. Re:Maybe a grain of salt, but it's what I'd predic by jrockway · · Score: 1

    LACK OF BLOAT IN GENTOO!?!?!?!?!?!?!?!1?1111

    Nearly all of the software that ships with gentoo is bloated. For example, gentoo's interpretation of cp includes an option to draw a progress bar while the file copies! That's not in the GNU codebase, that's something gentoo added. Bloat that gentoo added.

    --
    My other car is first.
  63. "Grammer Check" by CockMonster · · Score: 0

    Pinch of salt indeed

  64. Re:Coral Link... site's a little slow by JNighthawk · · Score: 0, Offtopic

    Coral Link... site's a little slow (Score:-1, Redundant)

    Well, at least now you don't have to worry about being a karma whore.

    --
    Wheel in the sky keeps on turnin'.
  65. Reverse engineering is... by Savage-Rabbit · · Score: 4, Interesting

    ... the detailed reproduction of another manufacturers product following detailed study of it's function and composition.

    That sentence came from the Oxford American Dictionary. To me that sounds as if reverse engineering has more to do with cloning products than just coming up with an alternative implementation which is what Wine is. All that Wine does is create a blackbox that works like the Windows API from the point of view of a Windows application but using totally different internals. Reverse engineering would be if they had recreated the internals more or less exactly using components replicated as far as possible from the originals in which case they would have to recreate the Windows source code from binaries somehow. You could also point to the AMD processors that implement the x86 instruction set, internally they are radically different from the Intel originals but to Windows they function the same. If that was reverse engineering I somehow suspect AMD would have gotten it's pants sued of by now. Instead Intel has now adopted the AMD64 instruction set that AMD came up with which is basically just x86 extended to 64 bit. The 'Mono' implementation of the Microsoft .NET architecture would be another example of somebody coming up with an alternative implementation without it being reverse engineering. The components of Mono may actually work more efficiently or also much less efficiently than their .NET counterparts but they behave the same and have an identical interface but very different internals.

    You did raise an interesting point about limited reverse engineering which is probably true. In order to clear up inconsistencies and undocumented features in the Windows API the Wine team probably did some analysis of Windows. Surprisingly enough I recenty found out that this is actually permissable under copyright laws, at least in my own country, if the manufacturer is reluctant to issue full and comprehensive documentation and it is vital to the success of your project and you are not attempting to replicate the internals of the undocumented product just determine how it works to fill in patchy documentation which is the case with Microsoft and the Wine team in this case, they are not making a bolt for bolt replica of Windows. From what I can tell Wine is not doing anything illegal or unethical if they were producing line for line copies of Windows system binaries by reverse engineering Windows source code that would be another matter.

    --
    Only to idiots, are orders laws.
    -- Henning von Tresckow
    1. Re:Reverse engineering is... by sjf · · Score: 2, Informative

      NOT ILLEGAL ! (per se)

      That's why Intel has tried to sue the pants off AMD and has failed. Clean room reverse engineering is a technique that DOES permit invasive inspection of decompiled binaries and has been upheld as legal and legitimate, in possibly the most famous example of reverse engineering in moderm computing: the IBM/Compaq BIOS case.

    2. Re: Reverse engineering is... by Black+Parrot · · Score: 2, Insightful

      > To me that sounds as if reverse engineering has more to do with cloning products than just coming up with an alternative implementation which is what Wine is.

      Reverse engineering is in fact almost always used for cloning. However, that's exactly what Wine is: a clone of various Windows components.

      > All that Wine does is create a blackbox that works like the Windows API from the point of view of a Windows application but using totally different internals.

      Reverse engineering isn't concerned with the internals, it's concerned with the effect.

      > Reverse engineering would be if they had recreated the internals more or less exactly using components replicated as far as possible from the originals in which case they would have to recreate the Windows source code from binaries somehow.

      No, that's not what reverse engineering means. Reverse engineering means "I'm want to make a thingy that works just like your thingy, but I don't have your blueprints, so I'm going to poke and prod your thingy as a black box, and mimic whatever behavior I observe."

      > You could also point to the AMD processors that implement the x86 instruction set, internally they are radically different from the Intel originals but to Windows they function the same. If that was reverse engineering I somehow suspect AMD would have gotten it's pants sued of by now.

      Intel did in fact sue whoever first cloned their x86 chips, but lost because the reverse-engineered chips did not violate any patents or copyrights.

      One of the dangers of keeping trade secrets rather than patenting them is that someone can reverse engineer your goodies and market them without paying you anything.

      --
      Sheesh, evil *and* a jerk. -- Jade
    3. Re: Reverse engineering is... by strider44 · · Score: 1

      You did read his definition didn't you? It said "function and composition ". What you said is just duplicating function, but not composition. It's most definitely concerned with internals - reverse engineering means taking apart the product and trying to duplicate it exactly - clone it. Which is most certainly not what wine is. Do you really think that if you compared the Wine source code and the Windows source code they'd be exactly the same? Wine is not a clone, it is an implementation.

      (On the same thread AMD didn't reverse engineer Intels chip either for the same reasons)

    4. Re: Reverse engineering is... by Black+Parrot · · Score: 1

      > You did read his definition didn't you? It said "function and composition". What you said is just duplicating function, but not composition.

      The composition of software products is a pattern of bits in some kind of media. The choice of media almost never matters when reverse engineering software. If I were trying to reverse engineer a car battery the choice of materials would be critical, but that's not what Wine is doing.

      > It's most definitely concerned with internals - reverse engineering means taking apart the product and trying to duplicate it exactly - clone it.

      No, it doesn't. It means creating a product that you can use in place of the one you looked at to create yours.

      It doesn't even have to look the same on the outside, unless the look is important to its function.

      > Do you really think that if you compared the Wine source code and the Windows source code they'd be exactly the same?

      Of course not. Get over your misconception of what reverse engineering means, and you'll quit expecting me to believe things that I don't.

      --
      Sheesh, evil *and* a jerk. -- Jade
  66. Re:Maybe a grain of salt, but it's what I'd predic by tuxeater123 · · Score: 1

    the only thing that windows does better than linux is compatibility (and that's even debateable) is user-friendliness. For instance Unix will let you modify a core file that will make your computer reboot as soon as it starts up. So wine still has far to go, but it has come very far.

  67. Re:Maybe a grain of salt, but it's what I'd predic by xenoterracide · · Score: 1

    5 Days!!! don't do a stage 1. absolutely nothing to gain from it. especially since gcc-3.4 is stable now. but it's not on the livecd's yet. you'll probably end up recompiling the entire system anyway. it may also be a good idea to do a grp install. just to get a faster working system. you can alway's re-emerge them later. I have an athlon-xp 2200+ and although it might take 4 days to get the system to where it is now. It take less than 8 hour's for an install and a functional system. infact I think I get to reboot in 2-3 hours.

  68. Re:Maybe a grain of salt, but it's what I'd predic by ZenShadow · · Score: 1

    cp is a lightweight utility to begin with. Those kinds of features don't detract significantly from performance.

    On the larger components such as Gnome, things suffer from considerably less featuritis than in any other distribution I've laid eyes on.

    BTW, if you don't want the progress bar, you can always disable the Gentoo-specific patches... I don't recall exactly how to enable it offhand, but there *is* a "build from original, unpatches sources" option.

    --S

    --
    -- sigs cause cancer.
  69. Re:Maybe a grain of salt, but it's what I'd predic by WilliamSChips · · Score: 1

    The only single package I've had take more than 24 hours(on a 900MHz Duron system--we're not talking 486s here) was OpenOffice.org. And it provides a bin package for that reason--and it's still quite slow, packages for OpenOffice take a long time to install no matter what type they are. And the thing I like about Gentoo is that, for example, I don't need to have that annoying gtkspell thing emerged if I'm not going to use it with Gaim. A friend of mine commented on #linuxattack that a Gentoo system often takes less time to install and get going than a SuSE system because the Gentoo system doesn't have to install near as many packages, even though each individual package takes longer.

    --
    Please, for the good of Humanity, vote Obama.
  70. Big prblemo by Anonymous Coward · · Score: 1, Informative

    is that there IS NO complete API for win32. There are bugs, undocumented features and outright porkie-pies.

  71. Re:Maybe a grain of salt, but it's what I'd predic by Anonymous Coward · · Score: 0

    Damn those grubby users for not keeping their fingers off of my /etc/inittab and constantly fiddling with the default runlevel entry!

    On an urelated note, could you pass me a toke of whatever you are smoking?

  72. Re:These tests don't really put Wine in a good lig by Rexifer · · Score: 1

    That could be true, too. I suppose it would make implementing a number of the WinAPIs easier, not to mention faster. :)

    I haven't looked at the Wine source (and probably can't), and didn't mean to imply one way or another the correctness of the Wine implementation of the mentioned APIs... I have some familiarity with Win32 underpinnings, and had only intended on commenting on the validity of the tests (memory/CPU) themselves as having a quantifiable performance component, as there is actually measurable work being done in Windows for those related APIs.

  73. Pure Nonsense by DirtyFly · · Score: 1

    These kind of tests only breing discredit to the 'linux' community and should be ignored, I believe enough was already said about the statistical nonsense this test is . but i had to express my anger here. WARNING : The amount of salt needed in this analisys will make your blood pressure raise to the 100's

  74. Re:Maybe a grain of salt, but it's what I'd predic by B2382F29 · · Score: 1

    If the OP is having problems with swapping it means that he doesn't have enough memory for the apps he's using; a distro change is unlikely to help with that.

    Not necessarily, the big plus of gentoo is the small number of extra services which get installed. Also you can control which features a program will use. OpenOffice for example will probably be compiled with Gnome and KDE support for distros like ubuntu. If you don't use KDE you can just drop KDE support with gentoo. => smaller binaries, less unneeded libs, more ram left, less swapping.

    --
    Move Sig. For great justice.
  75. Tell me when by TheDoctorWho · · Score: 0

    Tell me when I can play more than Quake 3 on a flavor of Linux.

  76. Re:Maybe a grain of salt, but it's what I'd predic by Spacejock · · Score: 3, Insightful

    I agree with you. When I was a kid we had 8 bit computers and you learned by doing. In those days you of fritzing your hardware by moving it too suddenly, causing a machine lockup with crappy code was the least of your problems.

    Gentoo evokes that era for me, and you can't have a go at people for breaking something when they're busy learning. So what if they over-optimise compiler flags and break things? When they fix them up they're learning a valuable lesson, and that lesson isn't 'next time use a binary distro'

    Anyway, today's school-age gentoo n00bs are tomorrow's crop of system admins.

  77. how about this benchmark by frankcow · · Score: 1

    How many applications actually work??? I'm going to hazzard a guess that Windows will run around the 100% mark, wine a paltry 25%

  78. Call me a novice....! by mattshadbolt · · Score: 1

    Call me a novice but the title of this thread made me wonder what benchmark could be associated between Windows and my favourite Cab Sav! - Matt Out

  79. WINE vs Windows or vice-a-versa by Nichole_knc · · Score: 1

    Being a long time Slackware user and only have a way ever-so-often need to run something on Windors "I ask why use WINE?" I have a Windors box that is a slave to my Slackbox with Synergy. It asnswers the telephone until I need something. I guess I look at it like this. If you go to the trouble to install Linux or a Unix flavor only to install WINE and run Windors apps on it "Why even bother?" Just run Windors... I started running Slackware to get away from the trouble not add to it. IMO

    1. Re:WINE vs Windows or vice-a-versa by SirTalon42 · · Score: 1

      Because not everyone has a second box next to them to use for Windows, because not everyone has an extra hard drive (or enough free space) to install Windows. What actually works in WINE generally works better than on Windows, I couldn't even install Call of Duty on Windows (it kept claiming my CD was in the drive, yes I did have the real CD in the drive), but it installed and worked great on WINE! Also lots of games act really bad with Alt+Tab in Windows, but everything works with switching between VTs on Linux (xinit `which PROGRAM` -- :1 is great).

      Not everything works with WINE (especially newer stuff), but what does seems to work great.

    2. Re:WINE vs Windows or vice-a-versa by Nichole_knc · · Score: 1

      Ok... But I am not a "gamer" least not on a Desktop. I will leave games to gameing consoles, thats me... Yes Windors has a bad rap with games and desktop switching... Not mentioning the rest... But I have read where lots of people have loaded Linux and WINE and then try to run everything on a windows partition only to be frustrated when it fails. Then they get frustrated with Linux because they just cannot 'point-n-click' everything. Me thinks they could not tweak a windors machine either. IMO The 3 "major" OSs Unix, Linux and windors have their place. Somebody somewhere can and will argue the points for each system. And that too is why I have all 3 (FreeBSD, Linux(Slackware, FC2 and Knoppix) and windors(xp home, xp pro, win98) and my Amigas(1.3, 2.1, 3.0) I once ran BeOS. Yes I have a thing for computers. I have no use for WINE or any other emulator. I have considered VM ware for my next build which will be bootable to at least 4 different OSs. BTW need a box, I keep 3 spares in a closest in case one fails. 16 total, at least 5 running all the time. A girl has got to have her servers.

  80. Re:Maybe a grain of salt, but it's what I'd predic by pjbgravely · · Score: 1

    Strange that you have these problems. I run Ubuntu 5.10 on a 800MHz PIII with 512 MB RAM with FireFox, Thunderbird, Azureus, Gaim, Abiword, 2 nautilus windows, and some terminals open and my memory usage is 293 MB RAM and 12 MB swap. The speed of the desktop is comparable to an XP box in the 2+ GHz range. It sounds like you have a memory leakage problem. You shouldn't swap much unless you are editing huge files or running very large programs.

    --
    Star Trek, there maybe hope.
  81. Wine Is Not an Emulator by The+MAZZTer · · Score: 1

    So no... Wine was only made for x86 machines.

    1. Re:Wine Is Not an Emulator by jaavaaguru · · Score: 1

      Wine in conjuction with something else

      I was thinking of something to do the x86 emulation...

    2. Re:Wine Is Not an Emulator by Slithe · · Score: 1

      You should be able to use Bochs to run an x86 Linux distribution that can run Wine. I hope you have powerful hardware; otherwise, it will CRAWL!

      --
      ---- "XML is like violence. If it doesn't fix the problem, you aren't using enough."
  82. Slower But Functionally Comlplete by deKernel · · Score: 1

    Personally, I would sacrifice performance for functionality any day. More times than not, I am not running the Windows app in any manor that requires critical performance (and if you are, you really need your head examined!).

  83. Re:Maybe a grain of salt, but it's what I'd predic by hazah · · Score: 1

    yay! i have a future!

  84. My xp by Apreche · · Score: 1

    It's always been my experience when using wine that wine performs better than Windows. Except of course for when wine doesn't work. So when it works, it works better, but it doesn't work nearly often enough. Notepad works though. Once you use notepad in wine you'll never go back.

    --
    The GeekNights podcast is going strong. Listen!
  85. Re:Maybe a grain of salt, but it's what I'd predic by Bazzalisk · · Score: 1
    CenterICQ for some inexplicable reason seems to take twice as long as Gnome.

    On a reasonably modern system Gentoo takes 1, maybe 2 days at most to set up, and that's stage 1. Stage 3 takes an afternoon at most and is every bit as good unless you have some very odd requirements.

    --
    James P. Barrett
  86. thats nice.. by nurb432 · · Score: 1

    But when it doesnt run the application you need, does speed matter? The application database is much more useful first.

    ( not faulting the WINE guys here, its is a huge task they have undertaken and are doing well )

    --
    ---- Booth was a patriot ----
    1. Re:thats nice.. by Austin+Milbarge · · Score: 1

      Yea, I agree. Just run my app first. Unless the app runs so slow it's not worth using.

  87. Microsoft Management Console by Gary+Destruction · · Score: 1

    Manage windows boxes from Linux through Wine.

  88. Late-Breaking news by teklob · · Score: 1

    This just in: Both OpenOffice.org and Mozilla Firefox are now available for Linux
    In other news, I'm not a troll but parent's point is 2/3rds incorrect.

    1. Re:Late-Breaking news by teklob · · Score: 1

      okay, okay, mod me flamebait i haven't had my coffee yet my apologies to the comedian

    2. Re:Late-Breaking news by woah · · Score: 1

      Yeah that and both apps have been developed for Unix/Linux first.

  89. Re:Maybe a grain of salt, but it's what I'd predic by oringo · · Score: 1

    I'm a gentoo user and I disagree. Gentoo does in general take longer to set up be in a working state than most OS. It's not supposed to be easy-installing like ubuntu. But I switched back from ubuntu because of the advantages that portage have over apt-get. Now my KDE runs faster and I don't have to keep two types of package on my system: 386 and 686.

  90. You are awesome by idonthack · · Score: 1

    I wish I had a "+1 LOL Gotcha!" mod for everyone else who replied to you.

    --
    Why is it that when you believe something it's an opinion, but when I believe something it's a manifesto?
  91. Re:Maybe a grain of salt, but it's what I'd predic by idonthack · · Score: 1
    For instance Unix will let you modify a core file that will make your computer reboot as soon as it starts up.
    Likewise, Windows lets you modify core files and cause the computer to crash as soon as it starts up, no matter what you do. At least with Linux you can pass it a boot option to go into runlevel 2 instead, and then quickly fix it or at least get your stuff off the drive.
    --
    Why is it that when you believe something it's an opinion, but when I believe something it's a manifesto?
  92. Spare us the cliche by Enrique1218 · · Score: 1

    the requisite dose of salt

    Enough with the cliches, especially that one. Try an analogy. Let's see. "Be as skeptical as reading G.W. Bush's interpretation of Superstring Theory" Doesn't quite roll off the tongue but you get the point.

    --
    You don't have to be smart to use a Mac, you just have to be smart enough to buy one
  93. Re:Maybe a grain of salt, but it's what I'd predic by Lehk228 · · Score: 1

    less unneeded libs

    Rush Limbaugh uses Gentoo?

    --
    Snowden and Manning are heroes.
  94. Re:Maybe a grain of salt, but it's what I'd predic by Darren+Winsper · · Score: 1

    If the KDE support is never used, it will never get paged into RAM. Thus, RAM usage will be largely the same.

  95. Macbook Pro: by Upaut · · Score: 1

    Has anyone tried to get WINE to work on a new intel Macbook or Imac? Now that a processor emulation is no longer needed, will it be a simple recompile, or are there other hurdles to jump before I can run windows software on my mac?

    ... I just have a bunch of educational software my course gives me that I would like to run, but it does not have a mac version... That and the ocassional game would be nice (I know macs have games, but I have a seriouse backlog of classics I loved from my windows/DOS days)

    --
    3 degrees of separation from Vladimir Putin
  96. Re:Maybe a grain of salt, but it's what I'd predic by outZider · · Score: 1

    No, but I'll bash your hair if it's necessary. I asked a serious question -- does it matter?

    "Gentoo is my favorite distro, I like it." is valid. I like Ubuntu. That's why we have choice.

    "Gentoo is built for speed." is not valid, as I haven't seen a benchmark yet that warrants five days to get a usable system.

    --
    - oZ
    // i am here.
  97. Re:Maybe a grain of salt, but it's what I'd predic by mattyrobinson69 · · Score: 1

    in 2.6 kernel's there's a setting somewhere in /proc (cant remember the exact path, i'm on a window box at the mo) called swappyness.

    Its possible that debian has their swappyness set higher than the other distro (gentoo i think, i didn't rta)

  98. WINE IS a Windows replacement by Kludge · · Score: 1

    Because the only thing that Linux can't do that Windows can is run my son's kiddie video games. Wine has become very stable and adept at that in the last year. Yeah! Soon I will blow away that infested piece of crap. Windows, you're fired!

  99. Re:Maybe a grain of salt, but it's what I'd predic by rolfwind · · Score: 1

    Nah, I play mostly with my Plan9 system for doing stuff.

    But I use Linux to browse the web with at least 10 tabs open at a time (probably more), using the filebrowser to look stuff up (Nautilus is a resource hog), and perhaps a FTP client to upload files. That's it of programs of note (the others are accesory programs like calculator or Sasuga (?), japanese spelling program - things that aren't processor/resource intensive).

    Sometimes I fire up emacs. But the swapping always happens when I'm only browsing the web or my files. Then I sit there for a minute waiting for it to subside.

    I like Ubuntu overall (it has great detection and I was impressed how easy it's to burn CDs right out of the box, so to speak) but I always run into strange problems. Since using Automatix, I get repository errors when trying to upgrade my programs - these errors happened eventually on every release I tried. Perhaps my computer is just jinxed:)

    Anyway, Gentoo was one distro I haven't tried yet. I tried Linux From Scratch years ago, but I'm too busy for that now.

  100. Re:Maybe a grain of salt, but it's what I'd predic by Bios_Hakr · · Score: 1

    If you are going to do a stage 3 or a GRP, you might as well use Debian. Deb has packages for GCC and the kernel compiled for virtually every acrhetecture out there.

    --
    I'd rather you do it wrong, than for me to have to do it at all.
  101. Re:Maybe a grain of salt, but it's what I'd predic by WWWWolf · · Score: 1
    Not necessarily, the big plus of gentoo is the small number of extra services which get installed

    Debian, last time I checked, installs a ton of redundant stuff, which is why God invented dpkg -r... Just because extra services get installed doesn't mean they need to stay =)

    OpenOffice for example will probably be compiled with Gnome and KDE support for distros like ubuntu.

    A bit bad example. At least in Debian, GNOME support is in a separate packages (openoffice.org-gnome, ooqstart-gnome, openoffice.org-evolution). I don't think OpenOffice.org even has KDE support, apart of the generic freedesktop standards support, which we hold self-evident these days.

  102. Re:These tests don't really put Wine in a good lig by DigitlDud · · Score: 1

    The tests I'm referring to are the read/write memory tests. They're over small amounts of memory within a page so the memory manager would have nothing to do with it. Not only that, if allocations are included in the test time, well, that's one inefficent test since it's ment to test hardware not OS overhead.

  103. DirectLinuX Revisited by MrNybbles · · Score: 1

    When I see comments like "And so we have this huge cyclical myth propogating that for instance 'X sucks'." I wonder if some of you ever even read my origonal post.

    The X Window system does not "suck" nor did I say it does. I however did say that WINE does NOT need to be the fastest. The X Window System works well for almost anything you can throw at it and can even be set up so that the actual program you are running is on a different computer and the one you are using just dislays what is going on. It was designed to be very useful, but not to be the best gaming engine on the face of the earth.

    Many of you seem to be missing the point which is The X Window system is fast enough and the effort to make it faster isn't worth it.

    And what is with that Anonymous Coward commment "DirectX dont access hardware through GDI, that would be sluggish. DX access directly to hardware by a driver implemented HAL."

    I said "DirectX is good at getting around [MEANING NOT USING] using the slower Windows GDI." Are enough of you dumb enough to actually be confused by the phrase "getting around?" Yes, I now realize that was a poorly constructed sentence with two meanings and that is my fault, but that is no excuse. By the context you really should have figured out what I ment or at least asked what I ment but instead a bunch of you (but not all of you) acted like dumbasses and jumped to the wrong conclusion.

    Yes, DirectX can use HAL (hardware abstraction layer) and if a spicific feature is not available it can sometimes use HEL (hardware emulation layer.) (And there is also the Reference Rasterizer. Unlike HEL, the reference rasterizer supports every Direct3D feature according to the DirectX 7.0 Programmer's Reference.)

    Microsoft put a lot of time and effort into optimizing DirectX for speed. If you want to squeeze some more performance out of WINE you will most likely need to have the people working on the Kernel driver, the X Window System, and WINE working tward the goal of optimizing for speed. But why would they do that? As I said before "WINE doesn't need to be the fastest."

    Please don't be upset by anything I have said. We are all dumbasses sometimes I forgive you.
    ---
    Summary 1: WINE does not need to have the best benchmarks( be the fastest.)

    Summary 2: I know that many of you deal with dumbasses on Slashdot way too often and are fed up with it, but please realize that sometimes you are the dumbass.

    Summary 3: The phrase "getting around" can be taken two ways. My bad! Sorry!

    Summary 4: Because we are all dumbasses sometimes, I forgive you.
    ---
    This is just my opinion, please don't flame me just because you didn't take the time to not be a dumbass.

    --
    Losing faith in humanity one person at a time.