Slashdot Mirror


No WINE Before Its Time

Joe Barr writes "Stephen Feller has a story about WINE on NewsForge this morning ahead of next week's expected Beta release. The WINE project is 12 years old, so it's just about time." From the article: "'Wine has historically had a very frustrating history because it has been alpha software,' White said. 'This is really hard work. We're replicating the work of a billion-dollar company. The reason we're saying it's alpha is because we believe we still have fundamental changes to make on the way the internals work.' Noting that it has not always been easy to install software with Wine's alpha releases over the last decade, White said that once you got something working it has never meant it would continue to do so, or do so properly. There may have been display glitches or things not functioning properly, if a program even worked with Wine at all." OSTG is the parent company of both Slashdot and NewsForge.

145 of 192 comments (clear)

  1. More info.. by jkind · · Score: 5, Informative

    LWN.NET has a good rundown of new features, including Direct X 9 support and a new RichEdit control :)
    http://lwn.net/Articles/154451/

    --
    ~jennifer.k~
    1. Re:More info.. by tonsofpcs · · Score: 2, Interesting
      But from bugzilla, it seems that 24 and 32bit direct draw (DIB/GDI issues) has yet to be fixed :(
  2. Great Wine Quote by xactuary · · Score: 5, Funny
    The post reminded me of an old wine quote which I've used quite often... Just take a sip and say, "A naive domestic with little breeding, but I'm amused by its presumption."

    Cheers.

    --
    Say hello to my little sig.
    1. Re:Great Wine Quote by jcupitt65 · · Score: 1
      Heh, actually a caption to a 1940s James Thurber drawing. A host offers a glass to a guest: "It's a naive domestic Burgundy without any breeding, but I think you'll be amused by its presumption."

      I don't seem to be able to find a scan of the actual cartoon online anywhere, oh well.

  3. Yes but.. by Anonymous Coward · · Score: 4, Funny

    Does it run linux?

    1. Re:Yes but.. by rincebrain · · Score: 1

      It's funny because it's absurd, thus the funny mod.

      Also, I wonder how well WINE runs Cygwin. :)

      --
      It's only an insult if it's not true.
    2. Re:Yes but.. by kill-1 · · Score: 1

      It's funny, because it's joking about one of the standard Slashdot comment. Just like "Imagine a beowulf cluster".

      And I wonder how well Cygwin runs WINE...

    3. Re:Yes but.. by CaraCalla · · Score: 1

      cygwin on wine on linux is underway. See http://www.winehq.org/?page=fun_projects (about halfway down the page, under "Virtualisation Projects")

    4. Re:Yes but.. by FST777 · · Score: 1

      No, but there have been reports of the beginnings of a NetBSD ports...

      Seriously though, when wine is 100% compatible with Windows, it should be able to run coLinux AFAICS... (then use X-Cygwin as X11-server, and compile QT and KDE for coLinux... w00t!)

      --
      Free beer is never free as in speech. Free speech is always free as in beer.
  4. VisualStudio Plugin by Anonymous Coward · · Score: 5, Interesting

    I think it would be incredible to have a VisualStudio plugin that would allow developers to target the Wine API and at least indicate if a particular API will not be supported under it. That way it makes the API less of a moving target in that it establishes WINE as the authoritative API for development of Windows applications that will work across platforms. Once people recognize that Windows is not the way forward they will appreciate having their options open.

    1. Re:VisualStudio Plugin by Anonymous Coward · · Score: 2, Informative
  5. Moonbase Alpha by fm6 · · Score: 4, Funny
    The reason we're saying it's alpha is because we believe we still have fundamental changes to make on the way the internals work.
    Microsoft seems to have the same problem.
    1. Re:Moonbase Alpha by jZnat · · Score: 1

      In that case, what would that make the alpha and beta builds of Vista, IE7, etc., all be considered?

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    2. Re:Moonbase Alpha by fm6 · · Score: 1

      Well, Microsoft obviously has different definitions of "alpha," and "beta" than, say, Google.

  6. Obligatory Microsoft joke by Anonymous Coward · · Score: 1, Funny

    Noting that it has not always been easy to install software with Wine's alpha releases over the last decade, White said that once you got something working it has never meant it would continue to do so, or do so properly.

    Sounds like it represents the Windows API pretty well then.

    1. Re:Obligatory Microsoft joke by Sephiriz · · Score: 1

      This is to the people who modded this as informative: Who ARE you people?

  7. vista by CDPatten · · Score: 5, Interesting

    How will Vista affect this beta release?

    1. Re:vista by smittyoneeach · · Score: 4, Funny

      Category 5 hurricane

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    2. Re:vista by ln+-sf+head+ass · · Score: 1

      Props for your sig!

    3. Re:vista by gvc · · Score: 2, Insightful

      Vista? Wine has yet to make it to the NT era. All its dll-s are win98 compatible, not winXP.

    4. Re:vista by joeljkp · · Score: 1

      Not quite sure what you're getting at, but WINE has support modes all the way up to Server 2003.

      --
      WeRelate.org - wiki-based genealogy
    5. Re:vista by MasterOfCeremonies · · Score: 1

      Hurricanes are so two months ago.

    6. Re:vista by ln+-sf+head+ass · · Score: 1

      Heh :).

  8. Welld duh its written in C by Billly+Gates · · Score: 1, Insightful

    Unless they rewritten wine in c++ its going to have problems emulating c++ features like objects really really bad. I am not bashing C, but rather pointing out that rewriting the language to mimick an operating system heavily built on C++ is a mistake.

    Gnome 1.x learned this lesson by emulating c++ in C because the unix C purists thought it would be less bloated and more cool. It was fine until object oriented programing became a factor.

    Most of it is due ot the fact that windows is complex and very proprietary with information hidden on the inner details. There are thousands of lines of code in windows based programs that simple workaround bugs. You have to actually duplicate the bug so the code works properly. Its a mess.

    1. Re:Welld duh its written in C by blazzy · · Score: 1

      What? WinAPI is pretty much entirely implemented in C. I'm guessing your only exposure to windows programming is something along the lines MFC? That's just a big C++ wrapper around WinAPI functions.

    2. Re:Welld duh its written in C by AgentJJ · · Score: 1

      Unless they rewritten wine in c++ its going to have problems emulating c++ features like objects really really bad. I am not bashing C, but rather pointing out that rewriting the language to mimick an operating system heavily built on C++ is a mistake.

      Huh? The Windows API is written almost entirely in C (it dates back to the mid 80's). New Windows features are still exposed through C (though I think some of the Vista features are only going to be exposed through .NET). Things like MFC and .NET Forms are built on top of the Windows API. The only "core" Windows API that I know of uses C++ is GDI+ which was written as a newer and better version of the GDI (which may or may not be built on top of GDI and some undocumented C functions).

    3. Re:Welld duh its written in C by man_of_mr_e · · Score: 4, Interesting

      The core API is definately C, but most of the ancillary libraries are C++. Pretty much anything COM based is C++ (DirectX, OLE, GDI+, etc...).

      Not that I agree with the original poster, you can certainly emulate C++ in C.

    4. Re:Welld duh its written in C by Waffle+Iron · · Score: 1
      The core API is definately C, but most of the ancillary libraries are C++. Pretty much anything COM based is C++ (DirectX, OLE, GDI+, etc...).

      Any COM interface can be called directly from C code. It's just a matter of typing an even more redundant and finicky syntax than the C++ version. In theory, COM was supposed to be a language-independent standard.

    5. Re:Welld duh its written in C by HermanAB · · Score: 1

      Oh man, Windoze always has been C. MFC is just a schtoopiddttt wrapper to make it more obscure. Real programmers don't use MFC...

      --
      Oh well, what the hell...
    6. Re:Welld duh its written in C by Anonymous Coward · · Score: 3, Informative

      How old are you, twelve? Because you're obviously not a C programmer, nor have you any idea how any of this stuff works. This much is clear from your post.

      Quit making shit up. Seriously.

      Gtk+ and by extension Gnome is object oriented and always have been. So are parts of Win32. Both use C, not C++. It is very possible to do object orientation in C. The earliest C++ compilers took C++ code and turned it into C, then passed it into a C compiler. It would still be possible to do a modern C++ compiler this way, because C++ doesn't do anything fancy that can't be expressed in C.

      Templates? Use #define or possibly some other trick. Namespaces? Put extra namespace_ crap in your symbols. Classes? Use structs. Virtual methods? Put function pointers in the structs. Inheritance? Cast structs to other structs, or store different structs in object wrappers. These are just a few ideas. What you end up with may not have as nice syntax, but it still does everything that C++ can. It is done by Microsoft. It is done by Gnome. It's really no big deal.

      I really hate it when people assume that object-oriented design depends 100% on the presence of a "class" keyword. To say that is narrow minded and shallow.

    7. Re:Welld duh its written in C by xquark · · Score: 2, Informative

      Wasn't one of the first iterations of GCC's C++ to just simply convert the C++ syntax into C and then compile + link ?

      Arash

      --
      Arash Partow's Philosophy: Be a person who knows what they don't know, and not a person who doesn't know.
    8. Re:Welld duh its written in C by blazzy · · Score: 1

      My mistake. When I think of Windows API i think of things like the basic UI elements, winsock, GDI, and whatnot. I suppose that speaks of my own limited exposure to windows development. Until, today I hadn't considered or appreciated the the enormous scope of what the wine project is tackling.

    9. Re:Welld duh its written in C by ClosedSource · · Score: 2, Informative

      "Gtk+ and by extension Gnome is object oriented and always have been. So are parts of Win32."

      I don't know about Gtk+ and Gnome, but I believe Win32 is only object-oriented it the sense that your application can create display objects at run-time that are subclassed from standard Windows display objects. That's not the same as saying that the Win32 source code is C written in an object-oriented manner.

      "It is very possible to do object orientation in C."

      Yes, you can write object-oriented code in C or even assembly language, but the set of problems that are best solved using that approach are very small. The vast majority of C-only programs are not object-oriented and are probably better off that way.

      "The earliest C++ compilers took C++ code and turned it into C, then passed it into a C compiler."

      Yes, early C++ programs were compiled this way. The reason they went to all that trouble was because they believed that C was inadequate for solving large complex problems, not because they didn't believe an OO approach was possible in C.

    10. Re:Welld duh its written in C by man_of_mr_e · · Score: 1

      That's what I said, you can emulate C++ in C.

    11. Re:Welld duh its written in C by Anonymous Coward · · Score: 1, Informative
      Win32 is object oriented in that you pass abstract handles and pointers to various data structures into its various functions which will act slightly differently depending on the underlying implementation. This description is kind of vague, but what I'm trying to say is these methods are used all over the place in various pieces of Win32. It's not clean and it has a lot of cruft. But it's a form of OO in terms of how it gets implemented. Think about the Win32 HANDLE, even. Yes, it's a key to a kernel resident data structure but if you think about it, those data structures are also objects. A HANDLE can have any number of methods, some underlying implementations behind handles have different methods and inherit from others. That's all a form of OO; just not the kind of OO that everybody thinks of when they hear OO.
      Yes, early C++ programs were compiled this way. The reason they went to all that trouble was because they believed that C was inadequate for solving large complex problems,
      What? That's gibberish. What "large complex problems" are you talking about exactly? C expresses everything that C++ does, minus the clean syntax. It's still conceivable to write a C++-to-C converter. I would think that the reason the compilers moved away is that there's no point in implementing these features in an "intermediate language" when you can just go straight to the assembly level. If you think about turning C++ into C and then compiling that, that's obviously notthe most elegant way to do it.
    12. Re:Welld duh its written in C by atomm1024 · · Score: 1, Funny
      How old are you, twelve?

      Well, duh. His account's listed URL is a LiveJournal. :)

      --
      Signature.
    13. Re:Welld duh its written in C by Urusai · · Score: 2, Informative

      Anything that can be done can be done in any Turing-complete language. So what? Putting objects in C is like emulating structured programming in Assembly--certainly doable, but what kind of idiot would you be? If you want modern paradigms, use languages that have them built in. This sort of excludes the hack that is C++, I admit...

    14. Re:Welld duh its written in C by cobras2 · · Score: 1

      >Not that I agree with the original poster, you can certainly emulate C++ in C.

      Somebody should already have said this, but, for that matter, you can *WRITE* C++ in C... Bjarne did :)

      ( http://www.research.att.com/~bs/bs_faq.html#bootst rapping )

      --
      Early bird may get the worm.. but the second mouse gets the cheese.
    15. Re:Welld duh its written in C by 51mon · · Score: 1

      'What? That's gibberish. What "large complex problems" are you talking about exactly?'

      Stroustroup says "event driven simulations for which Simula67 would have been ideal..." (but for the performance), but heck, what does he know.

      You can of course compile C++ into any Turing complete language, that doesn't necessarily mean it is a good idea, or that the other language is equivalent in terms of expressive power.

    16. Re:Welld duh its written in C by ClosedSource · · Score: 1

      "A HANDLE can have any number of methods, some underlying implementations behind handles have different methods and inherit from others. That's all a form of OO; just not the kind of OO that everybody thinks of when they hear OO."

      A handle is really just a pointer. I don't see anything OO about it. In any case, the issue at hand is the value of writing OO style source code using C instead of C++. Surely one can implement a run-time environment that has object-oriented features in C using only K&R style code, but that says nothing about the value of writing C code in an object-oriented style.

  9. Wine for OSX by Dr.+Spork · · Score: 5, Interesting

    You know, starting about next year, WINE will suddenly find a new big customer base, provided they can abstract the design enough to run on OSX-x86. I'm not sure how much work that would take but it certainly seems worth doing. I imagine that the people on OSX with an urge to run Windows apps will outnumber users of Linux with the same urge. Hell, if I were Codeweavers, I'd be working really hard on CrossoverOSX. There might even be good money in it!

    1. Re:Wine for OSX by FidelCatsro · · Score: 2, Interesting

      I expect a large influx of funding from Apple(perhaps already has occurred and they wanted it kept quiet) , Darwine has been underway for a while already http://darwine.opendarwin.org/ so they already have begun to tie it to the kernel .

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    2. Re:Wine for OSX by fm6 · · Score: 4, Insightful
      No matter how quiet they did it, it would get back to Microsoft — and the repercussions would be extreme. The Mac still relies heavily on Microsoft's goodwill.

      The idea of running Wine on Intel Macs probably occurred to every WINE enthusiast roughly 300 milliseconds after Apple announced they were abandoning POWER. No doubt many people are working on it, including Codweavers. But forget about financial support from Apple.

    3. Re:Wine for OSX by timeOday · · Score: 4, Funny
      I'm not sure it's such a good fit:

      Mac: It Just Works.

      Wine: Whoah, something almost worked!

    4. Re:Wine for OSX by FidelCatsro · · Score: 1
      Darwine is a project on the OpenDarwin site ,OpenDarwin was started by Apple and ISC to develop the kernel .
      to quote
      Many OpenDarwin members are either Apple employees or committers to Apple's CVS repository, who have an active interest in merging technologies from OpenDarwin.org into Darwin and Mac OS X releases..
      Pure speculation of course
      Some apple employs in their spare time working on the Darwine project , getting extra bonuses at Christmas and long holidays .

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    5. Re:Wine for OSX by pwagland · · Score: 3, Informative
      Hell, if I were Codeweavers, I'd be working really hard on CrossoverOSX. There might even be good money in it!
      http://www.codeweavers.com/about/general/press/?id =20050622

      It would appear that you are not alone...

    6. Re:Wine for OSX by fm6 · · Score: 1

      None of which comes even close to funding Wine for Mac development.

    7. Re:Wine for OSX by 11223 · · Score: 1

      The OpenDarwin site hosts the Darwine project. No Apple employee that I'm aware of works on Darwine, however.

    8. Re:Wine for OSX by FidelCatsro · · Score: 1

      Depends how many employes and how much of a bonus . Money can be funnelled through a few different channels rather easily , normally done to legally avoid a few taxes .

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    9. Re:Wine for OSX by subsolar2 · · Score: 1

      I imagine that the people on OSX with an urge to run Windows apps will outnumber users of Linux with the same urge. Hell, if I were Codeweavers, I'd be working really hard on CrossoverOSX. There might even be good money in it!


      IIRC I heard that they were on the wine list.
    10. Re:Wine for OSX by niteice · · Score: 1

      But if you add code to the kernel to recognize that a binary file is a Win32 PE, you know to give it to Darwine. Apparently, Mac OS X/x86 uses a similar method to determine that a file is a ppc application and pass it to Rosetta.

      --
      ROMANES EUNT DOMUS
    11. Re:Wine for OSX by ultranova · · Score: 2, Informative

      Wine: Whoah, something almost worked!

      Wine used to work somewhat, back when all configuration was done with a config file, because then you could just copy-paste it from the Net. However, then some nincompoop decided to remove support for the text config in favor of graphical configuratio tool, which not only makes it harder to config things (since you can't just copy-paste config file from Net anymore), but apparently doesn't properly save little details like "is this drive the CD-ROM or hard drive", even if it lets you choose between them in the graphical interface.

      Personally, I've pretty much given up on Wine. Nothing installs under it, nothing works properly, and when by some miracle you finally get something to both install and work, someone rips the functional parts of Wine code out because they happen to offend his sense of How Things Should Be.

      And yes, I did use wineinstall, so the config should be set to a working default. Now if something, anything, would actually work with those default settings :(...

      Do yourself a favor and stay away from Wine - as it is, it's just a waste of good diskspace.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    12. Re:Wine for OSX by Burz · · Score: 2, Funny

      Wow, It Nearly Executed!

    13. Re:Wine for OSX by esarjeant · · Score: 2, Interesting

      Agreed -- while the Wine project is a valiant attempt to simulate the Windows API calls, it simply doesn't provide the transparent support necessary to enable all of your Windows apps. While it comes very close, and there are at least a few cases where you will be pleasantly surprised, you will be much happier discovering the open source alternatives for your favorite Windows app.

      The only place where this falls apart is when you want to play a game on your PC. The fact is, developers support the Windows platform and without something like Wine you simply cannot play these games on other operating systems.

      Maybe one day the game publishers will see the light, and will instead develop to a portable platform (eg: Qt libs or somesuch) and everyone can then enjoy these games on any platform.

      --

      Eric Sarjeant
      eric[@]sarjeant.com

    14. Re:Wine for OSX by cerberusss · · Score: 1
      Do yourself a favor and stay away from Wine - as it is, it's just a waste of good diskspace.

      While I agree that Wine is sometimes barely useful, the people from CodeWeavers make a really useful release every now and then. It's really stable, if you use the supported applications (check their website, mainly MS Office). The download version is $40.

      No hidden agenda, just a satisfied customer.

      --
      8 of 13 people found this answer helpful. Did you?
  10. Obsolete model? by Slashdiddly · · Score: 5, Interesting

    Could it be that the hardware improvements made over the last 12 years may have made library-level emulation unnecessary? Device-level (eg, vmware) and architecture-level (eg, virtual pc) are both simpler and more robust.

    1. Re:Obsolete model? by Darkon · · Score: 1

      Could it be that the hardware improvements made over the last 12 years may have made library-level emulation unnecessary? Device-level (eg, vmware) and architecture-level (eg, virtual pc) are both simpler and more robust.

      Sure you can run Windows on a virtual machine, but you need a legal copy of Windows first. WINE allows you to run Windows applications without having to pay Microsoft any $$$.

      Also applications running in a VM are captive within the VM's window. I like the ability to move/resize/manage Windows applications anywhere on my desktop.

    2. Re:Obsolete model? by October_30th · · Score: 1
      WINE allows you to run Windows applications without having to pay Microsoft any $$$.

      Yeah, sure. If you want to run a notepad, minesweeper or solitaire. I've never been able to WINE more complex windows applications than that.

      --
      The owls are not what they seem
    3. Re:Obsolete model? by Anonymous Coward · · Score: 1

      but vmware and virtual pc don't run windows apps, wine does.

    4. Re:Obsolete model? by Darkon · · Score: 1


      Yeah, sure. If you want to run a notepad, minesweeper or solitaire.

      Good point. I really meant to say "In theory WINE allows you to run Windows applications without having to pay Microsoft any $$$"

    5. Re:Obsolete model? by AlbertEin · · Score: 1

      You didn't mentioned mIRC :P

    6. Re:Obsolete model? by AlbertEin · · Score: 1

      I only own a 386, you insensitive clod!

    7. Re:Obsolete model? by Slashdiddly · · Score: 1

      or d) People moved on to other platforms - which, as mind-boggling as it may seem - is still more likely to happen than either a), b) or c) in my opinion. In fact I think it is virtually guaranteed to happen within 15 years or so.

    8. Re:Obsolete model? by onemorechip · · Score: 1

      Either you haven't seriously tried Wine in the last five years, in which case your comment is utterly pointless, or you have, in which case it is pure BS.

      I've been running Quicken under Wine for years, upgrading every three to six months. Some versions of Wine have not worked as well than others (as the article points out, stuff gets fixed and broken all over again) but the last CVS version I got (20050725) was pretty smooth. I'm looking forward to the beta.

      I can't comment on any other large Windows-based apps because that's the only one I still run anymore (thanks to Gimp, OpenOffice, etc.). One smaller app that I run with Wine occasionally is SkyMap, and it works well also.

      --
      But, I wanted socialized health insurance!
    9. Re:Obsolete model? by imroy · · Score: 1

      I've used Wine for quite a few years to play StarCraft, Total Annihiliation, and Diablo II. The only problems are that emulating 8-bit paletted graphics on a 24-bit true-colour display eats up quite a few CPU cycles. And that I can't easily minimize or switch between the full-screen games. Oh well. So I just close down Firefox to free up memory and CPU, and my Jabber client so people know not to disturb me. Then I play for a few hours. Works pretty well too. Now what were you saying about notepad and minesweeper?

    10. Re:Obsolete model? by makomk · · Score: 1

      Even once most people have moved to other platforms, there'll still be businesses with legacy Windows applications they need to run. Hell, quite a few banks are still using OS/2 for some/most of their computer systems...

    11. Re:Obsolete model? by October_30th · · Score: 1

      Ok. And how much time did you spend tweaking WINE? I expect it to work out-of-box for major killer applications like MS Office before I say it's working, so I guess that's the reason I've been disappointed every time I've tried using it. Couldn't care less about games, though.

      --
      The owls are not what they seem
    12. Re:Obsolete model? by Albinofrenchy · · Score: 1

      WINE will become obselete, as it becomes possible for computer to intelligently port code. And make no mistake -- when that day comes, it would be easier to go from binary to binary rather than from source to source. I can easily imagine factoring the human element out of this process, which it would then be possible to follow new MS releases almost step by step.

      --
      "A man is but the product of his thoughts what he thinks, he becomes." -Mahatma Gandhi
    13. Re:Obsolete model? by CaraCalla · · Score: 2, Informative
      You certainly have a point there.

      But:

      • Try running a graphic intensive application (eg. a game) inside VMWare.
      • More generally, there will always be applications which require the latest and fastest hardware. In that case you do care about emulation overhead.
      • You still need a Microsoft License.
      • While in VMWare's case integration between native and emulated apps is pretty good (filesystem, clipboard), its not even close to being on par with Crossover Office and wine.
      • Wine is not an emulator :-)

      --
      sig: no sig

    14. Re:Obsolete model? by Ash-Fox · · Score: 1

      Try crossover office.

      --
      Change is certain; progress is not obligatory.
    15. Re:Obsolete model? by ultranova · · Score: 1

      Try running a graphic intensive application (eg. a game) inside VMWare.

      It would propably work better than in Wine, since it won't work at all in Wine. Or at least I haven't gotten a single game to even install, much less work with Wine... With the sole exception of Fallout 2.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    16. Re:Obsolete model? by Lucractius · · Score: 1

      I pity a bank running OS/2 instead of something more serious like AIX, zOS or OpenVMS

      --
      XML - A clever joke would be here if /. didn't mangle tag brackets.
    17. Re:Obsolete model? by pnewhook · · Score: 1
      Could it be that the hardware improvements made over the last 12 years may have made library-level emulation unnecessary? Device-level (eg, vmware) and architecture-level (eg, virtual pc) are both simpler and more robust.

      Of course Wine is obsolete. It was designed over 10 years ago and obviously technology has improved since then. Who cares that they've made incremental improvements.

      Oh wait. That's the argument for getting rid of Hubble. Never mind.

      --
      Tesla was a genius. Edison however was a overrated hack who liked to torture puppies.
    18. Re:Obsolete model? by Knuckles · · Score: 1

      If you want to run a notepad, minesweeper or solitaire. I've never been able to WINE more complex windows applications than that.

      Other people did

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    19. Re:Obsolete model? by Knuckles · · Score: 1

      With the sole exception of Fallout 2

      Try the right tool

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
  11. Darwine by catmistake · · Score: 1

    anyone know if this project is affected by this? Is it moving along? Have they made it to alpha yet?
    [opendarwin.org]

  12. Windows Standard Base by shumacher · · Score: 3, Interesting

    In the hardware-side x86 world, at least for the last fifteen years or so, you could buy a complete system, and no single company could be guaranteed a cut. AMD might get money, Intel might get money, but nobody had it locked down. Over time, the x86 has become something of a standard hardware platform. With WINE, I'd love to see a Windows Standard Base created. A single software environment that would be very commonplace, widely supported, shipped on almost all hardware, but not tied to a single company. In a sense, push Microsoft in software where IBM went with hardware. Eventually, you'll see vendors start creating secure versions, embedded versions, silly hacks to the PSP, and the money could go anywhere. Microsoft's Windows division could use some more direct competition.

    Wouldn't that be great, or am I wrong?

    1. Re:Windows Standard Base by hitmark · · Score: 1

      problem is that its like trying to base a open document format on something that have its basis in the ms office files.

      yes it can be done, but you still have one company that controls the basis. therefor there is no need for embrace, just extend, and watch all the rest chase their tails...

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    2. Re:Windows Standard Base by shumacher · · Score: 1

      That's the thing. IBM tried to force the market to Microchannel, and instead of the x86 world following, IBM found themselves on a incompatible, and largely unsupported fork. Microsoft could find themselves in the same boat if they try steering Windows just to break the base.

    3. Re:Windows Standard Base by Weedlekin · · Score: 1

      Why would they want to break the base? Surely, being able to say "look, our stuff is so great that even people running Linux and OS X want to emulate us" is great for them, especially if the emulation is eight years behind their release wave-front and even less reliable than the notably crash-prone Win9X series that they've now completely abandoned.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    4. Re:Windows Standard Base by Lehk228 · · Score: 1

      WINE isn't unstable. cewrtain apps will fail to work at all or be unstable in certain situations. however WINE iteself is rock solid and with apps that are unstable under windows i have found better in crash recovery. in particular EQIM an instant message program for connecting to everquest chat servers when it crashes in windows you have to wait N time where N can be a large amount sometimes but not always before a final error box to pop up before it can be successfully restarted. under WINE EQIM looked like hell but was no less stable than under windows. but could be relaunched instantly when it did crash and seemed to eat it's configuration files less often under WINE

      --
      Snowden and Manning are heroes.
  13. Not as hard as quote suggests by AHumbleOpinion · · Score: 4, Insightful

    This is really hard work. We're replicating the work of a billion-dollar company.

    Yes and no. It is a little simpler than this quote suggests. Wine does not need to implement every API that Microsoft produces. It needs to implement every API that desired Windows applications use. In some ways it is a quality of service problem, the marginal cost between supporting 90% of apps and 100% of apps may be too expensive. Maybe 80% to 90% is too expensive. I don't pretend to know what the optimal percentage is but it is surely not 100% or even mid to high 90%s.

    In any case this is a monumental task and the Wine developers deserve an awful lot of credit and thanks.

    1. Re:Not as hard as quote suggests by Kjella · · Score: 1

      Wine does not need to implement every API that Microsoft produces. It needs to implement every API that desired Windows applications use.

      Except users come in all flavors, and the list of desired apps is probably as long as the API list. And sometimes building the system is just as much work as building the API, if you want to do the "desired" parts of the API the rest just naturally fits in. In the end, they're still trying to recreate most of what Microsoft has made.

      --
      Live today, because you never know what tomorrow brings
    2. Re:Not as hard as quote suggests by IamTheRealMike · · Score: 5, Informative
      It's not quite that simple I'm afraid.

      Take the recent DCOM work we did. This is what I'm going to talk about because it's what I know - myself (CW) and Rob Shearman (CW), along with some help from Marcus Meissner (Novell) and Huw Davies (CW) reimplemented large parts of DCOM mostly for one application. The work took many months - starting from a pre-existing codebase written by Marcus years earlier, we were "finished" ~135 patches later.

      What was that one application which was so important?

      InstallShield.

      Now perhaps you see the problem - sure, not every API is used by every app. But there are hundreds of thousands of APIs, many extremely complex, and many millions of applications. All it takes is ONE popular application to use a single API that was not yet reimplemented and you have months of work ahead of you.

      This is especially true of something like DCOM where the supporting infrastructure for 4 or 5 functions can run to 10,000+ lines of code.

    3. Re:Not as hard as quote suggests by xerxesdaphat · · Score: 1
      OK. First of all, who says it took MS 100.000 lines of code? It took the WINE guys that, who are working under very different circumstances and may have had to write large workarounds for all kinds of reasons


      Secondly, how is it the fault of InstallShield that their code requires such an expensive API? All they have is, they come to the problem to write an installer, and the API is there, already implemented. How do they know how expensive it is? Why should they care? It's already there, they might as well use it.

      --
      The Shoes of the Fisherman's Wife Are Some Jive Ass Slippers
    4. Re:Not as hard as quote suggests by Jarlsberg · · Score: 1

      But Installshield does so much more! That's why it's so darn expensive, running at up to over $3000 for the full, premier version. You can't deliver a 100K app at that price ;)

    5. Re:Not as hard as quote suggests by adrianmonk · · Score: 1
      It needs to implement every API that desired Windows applications use. In some ways it is a quality of service problem, the marginal cost between supporting 90% of apps and 100% of apps may be too expensive. Maybe 80% to 90% is too expensive. I don't pretend to know what the optimal percentage is but it is surely not 100% or even mid to high 90%s.

      I disagree. There are lots of people who need Windows for some purpose, but in order to accomplish that purpose, they need more than one app.

      For instance, I develop for a platform where I can do most of the work on the Macintosh (which is what I do), but a certain amount of it must be done on Windows. Now, what is the stuff I have to do on Windows? Well, I need an IDE to run, and I need a couple of separate GUI editors to run, and I need several different variations of the same hardware simulator to run. And there may be one or two other tools I need as well.

      So, just to take some numbers at random, let's assume I need 10 apps to work in order not to need to have a Windows machine. And let's assume that 90% of apps work under WINE. What are the odds that all 10 apps that I need are going to be available? Well, it's (90%)^10, which is about 35%. Or what if only 85% of apps work and I only need 5 apps? Then the chances that all 5 apps will work are (85%)^5, or about 44%.

      Plus, it's not necessarily even as good as a 35% or 44% chance that it's workable. The apps I use over time may change. New versions come out, and new tools become available that I may need to use. (In my case, one of the two GUI editors I mentioned didn't exist a few years ago and is now becoming the standard, plus a new compiler is also slowly becoming the de facto standard.) Let's say that I have 2 new required apps in a year, and there's a 90% chance each will work. Well, then, there's an 81% that this hypothetical 90%-of-apps version of Wine will continue to be good enough, and there's a 19% chance that in a year, I'll have to abandon Wine and get a Windows box going instead.

      If all that is the case, then why would I want to go with Wine? According to those odds, there's a better than 50% chance that after I research it, I'll find that it can't do what I need now, and then there's a 20% chance that even if it does what I need now, it won't do what I need in a year. It's much easier just to go with Windows if Wine can only do 90% of the apps.

      Naturally, Wine isn't probably going to hit 100%. (Even Windows XP doesn't hit 100% of apps that ran under, say, Windows 98.) But for my money, the closer it can get to 100%, the better. 99% is considerably better than 98%. At 98%, the chances it will run any 10 randomly-chosen apps are only 82%, but at 99%, those changes go up to over 90%.

    6. Re:Not as hard as quote suggests by AHumbleOpinion · · Score: 3, Interesting

      Please don't misunderstand. I am not suggesting that targetting a subset of MS APIs is fast or easy. I've been down that road in a product far more limitted in scope than Wine, it was painful for us too. I just wanted to clarify that a successful project does not need to be a perfect, or even near perfect, Windows clone (API perspective). I suspected that some readers would focus on the entirety of MS APIs and I wanted them to reconsider doing so.

      Your point is well taken but it really seems to address how to pick which APIs go into that xx% that gives you optimal coverage. Optimal coverage is also not something that is fixed. Naturally as new or updated apps come out there will be more work (and pain) for the Wine developers. I guess another way to describe the point that I was trying to get at is that there is a lag between Microsoft introducing APIs and applications beginning to use those APIs, and that it would seem the latter is more important than the former. Adopting a new API can be tricky for a developer because that API may not be supported on older versions of Windows. I'm guessing here but I would expect apps with broader appeal, and more importance to the average Wine user, would be more resistant to requiring newer APIs with little backwards compatibility. I would expect that apps that immediately jump on new APIs and ignore backwards compatibility would tend to be more specialized and more niche oriented and less likely to be needed by Wine users. Again, just guessing.

      Maybe this leads us to a way to estimate what xx is. Take the top 10 most commonly used apps, what APIs are used? Now the top 50, then top 250. Plot the % of API coverage required, maybe we'll have a useful curve.

    7. Re:Not as hard as quote suggests by AHumbleOpinion · · Score: 1

      So, just to take some numbers at random, let's assume I need 10 apps to work in order not to need to have a Windows machine. And let's assume that 90% of apps work under WINE. What are the odds that all 10 apps that I need are going to be available? Well, it's (90%)^10, which is about 35%.

      I disagree with your analysis. Your first flaw is that you ignore the requirements of your formula. The 90% of all apps working under Wine are not chosen at random, they do not have equal "weight", they are chosen by popularity. The odds that a random person's 10 important app are in that 90% are far above 35%. Your second flaw is arguing that one individual's particular case is important. In general it is too expensive to support everyone, more practically developer time is very scarce and supporting niche products in the 10% remaining is an exceptionally poor use of time. There will always be new/updated programs with greater popularity that are better recipients of that time.

      Now the above represents the theoretical perspect of the Wine devs. The population of some niche community using an unsupported program may find it economical to spend *their* time adding support to Wine. When they are done they can contribute their changes. Ain't open source wonderful? Dev's can ignore the minority that is not worth their time and yet the minority can get serviced.

  14. Already announced by rincebrain · · Score: 1

    Codeweavers already announced that they were working on that codebase.

    I can't find the announcement, but have a line from the last WINE CVS drop changelog:

    * Some fixes for MacOS/x86.

    --
    It's only an insult if it's not true.
  15. Good clone by Baramin · · Score: 5, Funny
    White said that once you got something working it has never meant it would continue to do so, or do so properly. There may have been display glitches or things not functioning properly, if a program even worked with Wine at all.


    That's what I get from WinXP on a regular basis, so I guess I could stand using Wine.
    --
    There's no place like 127.0.0.1
    MyBlog
    1. Re:Good clone by FST777 · · Score: 1

      yeah, it struck me that they did reach 100% compatibility with the feel of the OS long before there were talks about beta-releases...

      --
      Free beer is never free as in speech. Free speech is always free as in beer.
  16. ABRs of OSS by Doc+Ruby · · Score: 4, Interesting

    "Alpha" is not a subjective measure of the quality or maturity of code. Alpha means the code has never been modified by feedback from testers who are not part of the development team. "Beta" means code that has been or is being modified after receiving beta test results from people without the expectations, therefore the blind spots and other biases, of the developers themselves. Alpha tests are important, but beta tests are much more important to determine whether the code will be acceptable by its users, especially when those users aren't the developers. The "release" test is a more subjective delineation, especially since Netscape got everyone to accept that we'd use "beta" software the same way we'd use a general release.

    So WINE might have good reasons (eg. moving Microsoft target) for remaining relatively "immature", incomplete, or buggy. But once they revised it on feedback from people outside the WINE development team, it is beta, regardless of what they call it.

    This is not a semantic argument. It's a very important point about how development/testing patterns affect code quality. Incorporating the "social" aspects of development, and their constructive/destructive effects on projects, makes development more productive. This is especially true of OSS, as projects often lack the discipline that comes with keeping the code hidden from "outsiders". Without the proprietary discipline, the alpha/beta/release discipline lets OSS projects have more flexibility, and therefore more productivity when used right. Without even the alpha/beta/release discipline, OSS projects need another to produce quality, or fail to do so.

    --

    --
    make install -not war

    1. Re:ABRs of OSS by AlbertEin · · Score: 2, Informative

      From http://en.wikipedia.org/wiki/Development_stage

      Alpha: The alpha version of a product still awaits full debugging or full implementation of all its functionality, but satisfies a majority of the requirements. It often lacks features promised in the final release, but demonstrates the feasibility and basic structure of the software

      Beta: A beta version or beta release usually represents the first feature complete version of a computer program or other product, likely to be unstable but useful for internal demonstrations and previews to select customers. Some developers refer to this stage as a preview, as a technical preview (TP) or as an early access. Often this stage begins when the developers announce a feature freeze on the product, indicating that no more features will be added to this version of the product and only software issues, or bugs, will be removed. Beta versions stand at an intermediate step in the full development cycle. Developers release them to a group of beta testers (sometimes the general public) for a user test. The testers report any bugs that they found and sometimes minor features they would like to see in the final version.

      Alpha does mean lack of quality and features, it does mean that it could change a lot.

      Beta doesn't mean that some code or binaries are released, that could apply to non open source software, but in OSS it's out of place. The beta stuff is about make something stabler, frozing the features, like a snapshot of the final release.

    2. Re:ABRs of OSS by chgros · · Score: 1

      Netscape got everyone to accept that we'd use "beta" software the same way we'd use a general release.
      I thought that was Google?

    3. Re:ABRs of OSS by Doc+Ruby · · Score: 2, Interesting

      Moderation -2
          50% Troll
          50% Offtopic

      TrollMods: that's a Flame, not a "Troll". Look it up before you mod.

      --

      --
      make install -not war

    4. Re:ABRs of OSS by Doc+Ruby · · Score: 1

      I agree. OSS does intrinsically blur distinctions of who's "in" the development team, and who's just working "with" it. Another reason why the alpha/beta/release discipline is so important. It doesn't impede development, but does offer useful structure to replace that lost with the proprietary straitjacket.

      --

      --
      make install -not war

    5. Re:ABRs of OSS by Doc+Ruby · · Score: 1

      As I detailed, and as another post in this thread concurs, alpha/beta/release definitions are not at all fuzzy when used properly. Sure there are plenty of releases that abuse the terms - marketspeak is like that. But marketspeak is abuse of the terms. That's why I'm going to the trouble to clarify the use of the terms, and the underlying process that works. Those are the facts. I can argue with your facts, because they're wrong. You might not be certain about what marks a project's progress to release, but I am certain, regardless of what mistakes are made by others in describing them.

      --

      --
      make install -not war

    6. Re:ABRs of OSS by Doc+Ruby · · Score: 1

      We'd already accepted that, courtesy of Netscape, years before Google appeared.

      --

      --
      make install -not war

    7. Re:ABRs of OSS by huiac · · Score: 1

      Well we're all entitled to our own opinions and interpretations, but in the last place I did development feature freeze always preceded or coincided with the transition from alpha to beta: adding new features implies adding untried code, which (however clean it looked to the developer) would be classified as alpha quality by the standard of those who set the rules.

      We also never (well, *almost* never) provided beta software to anyone outside our organization - beta was always about debugging, and preparing to pass formal testing. Important customers or those with urgent needs might occasionally see release candidates (which were considered 'post-beta').

      In the olden days there was also a gamma stage, but you rarely hear about that nowadays.

      OSS changes the rules and blurs the lines between beta and RC, but any significant new code is always alpha in my book.

      John.

    8. Re:ABRs of OSS by Doc+Ruby · · Score: 1

      You learned about alpha/beta/release terminology at a shop which didn't use the process right. They used the names associated with code maturity, which came from specific changes in the development cycle, to refer to the relative maturity rather than the phase changes. This is generally the reason that the terms are so widely misunderstood. But that doesn't mean that the terms do mean that, though they might to some - or many. More importantly, it doesn't mean that the process is properly run that way. The process, properly run, is much more manageable and productive. Consider that, rather than what you might have learned at a shop that didn't use the process properly. As I've said, my post isn't a semantic argument. I'm pointing out the difference in the process; the names merely reflect that.

      --

      --
      make install -not war

    9. Re:ABRs of OSS by huiac · · Score: 1

      I hadn't noticed what source you're citing as your authority, but our development process reflected (among other things) the requirements of our strategic partners which included firms like Intel, which went over the place and the development process with a fine-tooth comb just before I started.

      You've referred several times to maintaining objective distinctions between alpha, beta and rc, but those of your posts that I've read seem not to demonstrate that, and appear to blur the line in a way that makes it hard for me (at least) to see what you believe those distinctions are; but then, you've posted so many responses to this article I may simply have missed it. Care to provide a URL to the post where you set out those objective distinctions, or cite the authority you rely on?

      John.

    10. Re:ABRs of OSS by Doc+Ruby · · Score: 1

      The alpha/beta system I originally described is objective. Alpha software has never been revised in light of feedback from people outside the development team. Beta has. The release point is subjective as I described it, but (to expand more on a complex subject) is properly defined as when the product meets all of the acceptance criteria specified during its design, and when those criteria have not been changed.

      As for my "authority", the answer is "it works". Which I have found in the best-run projects during the nearly 30 years I've been programming. Including at Apple, and at my own consultancy, where dozens of us produced top-quality code at top speed for big clients on big projects (and small ones). Those are the authorities - practical success. Not brand names. Even your experience at Intel is only a name-brand authority - their project management has now produced at least the P4 and now the Xeon, to name just the most prominent examples, of "releasing a wine before its time". Maybe they are using qualitative definitions of alpha/beta, or maybe they're designing the wrong acceptance criteria, or maybe they're releasing prematurely because their R&D isn't producing properly. But Intel is no citable authority on either the meaning of alpha/beta points, or the utility of another definition. The authority, as I've cited, is success.

      --

      --
      make install -not war

  17. Is it just me? by zappepcs · · Score: 1

    Or do others feel that multibillion dollar companies get away with selling alpha software? As far as I can remember, most companies put out alpha and beta software to let users test it in production environments. I could name a few here, but we have all probably dealt with this issue.

    One thing that is nice to see, the group developing Wine have no illusions, and freely admit that you might have problems using the software. Despite that, I know many people who use Wine so they don't need MS operating systems. Since my adventure began to rip MS products out of my home and business networks, I have found a couple of programs that just are not available for *nix and so far, have limped along on an old Win98SE box. Wine is my next step.

    Along with others here I say, "so its alpha?", THANK YOU VERY MUCH.

    --
    Yes, if it works for me, I contribute dollars.

    1. Re:Is it just me? by RoffleTheWaffle · · Score: 2, Insightful

      "Or do others feel that multibillion dollar companies get away with selling alpha software? As far as I can remember, most companies put out alpha and beta software to let users test it in production environments. I could name a few here, but we have all probably dealt with this issue."

      One word: marketing. That's how you get away with selling alpha software. You market an alpha-qaulity product to look like something that works as good as it should, and if your marketing campaign successfully ropes in enough interested parties that can't analyze your codebase to see what shit your product really is, it will sell anyway due to the fact that you have convinced them to have faith in your product by other means. (Usually graphics, sound, and long lists of features.) It should also be noted that in the world of computing, marginal functionality in many cases is still enough to get work plenty of work done, but there is always room for improvement, especially in the case of the piece of alpha software I suspect you are speaking of. (Windows.)

      WINE is a brilliant project. I'd like to see it move faster than it is, but one can't rush perfection. Now that WINE is bearing some real fruit - an actual beta release - perhaps support for the project will further build. I certainly hope so.

    2. Re:Is it just me? by ebuck · · Score: 2, Funny

      Just imagine, and Digital kept pushing their Alpha CPUs on everyone. The didn't even make it to Beta, and it's no wonder that HP scrapped thier remains.

      Or, you could perhaps look at the software to see if it meets your needs, and not get so excited about the release name / revision. Considering that there are not a lot of ways to make Windows executables run on Linux, even a pre-that-thing-before-alpha sounds better than nothing at all.

      And no, virtual machines running windows isn't the same thing as running a windows exe on Linux, but those who's needs are met by such workarounds are not those who drive the Wine project anyway.

  18. Enough is enough... Call the FTC by Baldrson · · Score: 2, Insightful
    The FTC should have been requiring M$ to publish its API from the first day IBM shipped MSDOS with the 4.77MHz 8088 PC.

    It should require M$ to publish all of its APIs now and verify that all M$ applications are written to those published APIs. Moreover, it should require that all communications between the application development portion of M$ and the operating system portion of M$ are public domain.

    1. Re:Enough is enough... Call the FTC by DigitlDud · · Score: 1

      Uhh...Windows is Microsoft's private property, it's not public domain. They're not obligated to do any of those things. You know, property is supposed to be protected in this country not regulated by the government.

  19. ReactOS and WINE by Anonymous Coward · · Score: 5, Interesting

    In case anyone doesn't know. The ReactOS project works closely with WINE. They are implementing the API from WINE on a replica of the Windows 2000 kernel.

    This means that both Windows drivers and applications will work natively without any changes. They seem to have come on leaps and bounds in the past year with many applications working straight away (OpenOffice, Abiword, mIRC, Unreal Tournament, InfranView, PuTTY as some). Once they start implementing some of the security features then there will be another viable alternative.

    In the future I can imagine ReactOS coming on a CD with OpenOffice, Apache etc, much like Linux distributions do, which creates an easy migration path:

    Windows + Apps -> Windows + OSS Apps -> ReactOS + OSS Apps then then off to a Linux or *BSD varient if you want.

    1. Re:ReactOS and WINE by TwoTailedFox · · Score: 4, Informative

      Replica? Almost. ReactOS is designed to be compatible, first-off, with Windows NT 4.0.

      Networking is the next big leap for the 0.3.0 ReactOS Release. Some parts work quite well already.

      --
      ~The TwoTailedFox posts again....
    2. Re:ReactOS and WINE by walterbyrd · · Score: 1

      My experience with reactos 2.7 is that it doesn't work at all. It won't even install on my very standard PC. Even people who love reactos admit it isn't stable enough for ordinary use. And, react is tryin go catch up with an OS that came out ten years ago.

      I hate to post it, but I'm afraid that by the time reactos is anywhere close to NT4, it will be much too late to be of any practicle value. Like freedos or zeta, it will just be a curiosity.

    3. Re:ReactOS and WINE by TwoTailedFox · · Score: 2, Informative

      Small Correction: It's 0.2.7, not 2.7.

      ReactOS is still Alpha Software, and as such, is incorporating elements from later Windows NT iterations. Some Winsock 2 API's have already been implemented, that came in Windows XP. Even some Windows 2003 Functionality, like Guarded Mutex, is present.

      0.2.7 shipped with a 2 major bugs that have been largely fixed (touch wood)... 0.2.8 is due out in a few weeks, with 0.2.8 RC1 already out on their Sourceforge Page (http://sourceforge.net/projects/reactos).

      Once it's got the NT4-esque layout, it's then easier to play catchup to the later versions.

      --
      ~The TwoTailedFox posts again....
    4. Re:ReactOS and WINE by LentoMan · · Score: 2, Informative

      ReactOS homepage used to say they were aiming for nt4.0 compatibility, but now it says: "The ReactOS® project is dedicated to making Free Software available to everyone by providing a ground-up implementation of a Microsoft Windows® XP compatible operating system. ReactOS aims to achieve complete binary compatibility with both applications and device drivers meant for NT and XP operating systems, by using a similar architecture and providing a complete and equivalent public interface." I'm sure they will adopt to any updates microsoft does and eventually catch up...even if it will take a few (or lots) of years.

    5. Re:ReactOS and WINE by FST777 · · Score: 1

      Whoah there, FreeDOS is NOT a curiosity for people like me who try to get some new live in other peoples Win98-boxen. Having said that, when 100% compatibility with NT 4.0 is reached, the step to NT 5.0 isn't that hard anymore. At least not when another project (wine) is looking at the recent API. Sure, it'll take time.

      --
      Free beer is never free as in speech. Free speech is always free as in beer.
  20. Re:No WINE Before Its Time by temcat · · Score: 1

    Now how is that offtopic? Not very funny, but certainly ontopic.

  21. Is there an analogy to doing that? by Grendel+Drago · · Score: 1

    Err... is there some sort of analogy for opening the specs of a complex and mostly-monopolized system so that competition is possible? I mean, if I were an 80 year old judge and the most complex technology I understood was the telephone, how would you sell me on this idea?

    --
    Laws do not persuade just because they threaten. --Seneca
    1. Re:Is there an analogy to doing that? by belmolis · · Score: 1

      Easy. The telephone system in the US went through exactly this process. It was once a monopoly. The phone company even owned the phone lines within your house and the telephones: you just rented them. You had to get your equipment from them and have them do all the service. Of course, this meant no competition and it suppressed innovation since depending on the case it was difficult or impossible to add third-party equipment to the system. Now, in contrast, there is competition and you can hook anything up that you want so long as it conforms to certain specs.

    2. Re:Is there an analogy to doing that? by KillShill · · Score: 1

      sounds sort of like apple.

      --
      Science : Proprietary , Knowledge : Open Source
  22. Property rights are a social construct. by Baldrson · · Score: 4, Insightful
    The day Bill Gates, Steve Balmer, Paul Allen, Larry Ellison, Warren Buffett, et al pay the cost of protecting their property rights is the day I'll consider respecting those property rights. Until then, everything they own is fair game.

    Since the primary function of government is the protection of non-subsistence property rights, it is sensible to charge a use fee for those rights. Note, I said "non-subsistence" property rights. The point here is that house and tools of the trade are protected from confiscation under bankruptcy law precisely because they are subsistence assets. Where government does not exist, subsistence properties are typically defended by the occupant, whose life is sustained by those assets. Government brings precisely the property rights we associate with civilization -- assets beyond home and tools of the trade.

    Given the relatively liquid nature of civilization, it makes sense to define "non-subsistence" in some dollar value of assets. Various ways of defining the dollar value are all approximately equal:

    • The median price of housing a person plus the median price of capitalizing a job.
    • The threshold used by the SEC for "qualified investor".
    • The level of savings insured by the FDIC.
    • Or, for the historically inclined: The market price of 20 arable acres in the Confederate south, a mule, a plow and a small house on such land.
    Until a citizen accumulates the subsistence net asset level, they should pay no tax and then pay tax only on the net assets they own above subsistence.

    Assessment should be by the owner, thereby establishing a "fair market value" for the exercise of eminent domain. Net assets only would be taxed and would be calculated by subtracting the fair market value of debts against the estate from the self-assessment of the occupant.

    Other forms of taxation could be eliminated in a revenue neutral way if net assets, in excess of subsistence levels, were taxed at the risk free interest rate (approximately the interest rate on the national debt).

    Indeed, given the centralization of asset ownership that has resulted from the subsidy of non-subsistence property, a subsidy inherent in civilization, it may be the failure to use this tax base is the ultimate cause of the repeated decay of civilizations from ancient times.

    1. Re:Property rights are a social construct. by Quarters · · Score: 2, Insightful
      Since the primary function of government is the protection of non-subsistence property rights...

      I'm assuming since you have a geocities.com address that you reside in the U.S. As such I'm basing my comments on the purpoes of the US Government. That being said, you're off your rocker with the above quoted statement.

      There is absolutely nothing in the US Constitution that deals with "non-subsistence property rights". I'm not even sure what that phrase means, to be honest. What exactly are property rights that don't deal with livelihood? Section 8 of Article 1 pretty clearly lays down the mega-rules for the Congress. Regulate interstate commerce, coin a national currency, build roads and the Post Office, maintain a Navy, regulate courts below the Supreme, call forth a militia when necessary, declare War, raise armies, punish counerfeiters, trade with other nations, and regulate copyright, etc... Note that copyright is clause #8 in Section 8. Even if that is what you refefing to, it is in no way the primary declared function of the US government. BTW, clause 1 of Section 8 is, "The Congress shall have Power To lay and collect Taxes, Duties, Imposts and Excises, to pay the Debts and provide for the common Defence and general Welfare of the United States; but all Duties, Imposts and Excises shall be uniform throughout the United States". Collect taxes, pay debts, defend the counry, and ensure taxes are equal. That's the primary duty. Property rights, of any type, don't factor in to that.

    2. Re:Property rights are a social construct. by Baldrson · · Score: 1
      There is absolutely nothing in the US Constitution that deals with "non-subsistence property rights".

      Yes it does.

      As I already pointed out, the government could simply not exist at all, and people would still have the "right" to "keep and bear arms", to "free speech" etc. All the bill of rights does is delineate areas of subsistence rights that the government is most likely to usurp once it is taken over by an oligarchy or tyrant. The entirety of the rest of the Constitution has to do with powers of the government to guarantee other rights. "Common defense and general welfare" can even be interpreted in a manner consistent with communism, and the citizens are still enjoying the property right of citizenship itself, which has benefits to which they are entitled as citizens.

    3. Re:Property rights are a social construct. by Quarters · · Score: 1
      There is absolutely nothing in the US Constitution that deals with "non-subsistence property rights".

      Yes it does.

      "Yes it does." Isn't a valid response, either logically or grammatically to my statement. Beyond that the rest of your post comes across as nothing more than rantings. I see you used the term "subsistence rights". Last time it was "non-subsistence rights". Not only do you make up illogical phrases, you can't even remember which phrases you've used. So is your version of the US Government protecting livelihood rights or non-livelihood rights? Exactly where in the US Constitution does it describe these (livelihood / non-livelihood) rights? Site Article and Clause, please. The Constitution is online in many places, so I'm sure you can do a "find" on it for that phrase. I already have, I got 0 hits. But, before you answer any of that could you please describe what in the world livelihood rights are? I need to adust my thinking to you slanted orientation before I can even think to understand what in the world it is you are trying to say.

  23. Wine? by Geoffreyerffoeg · · Score: 2, Funny

    The WINE project is 12 years old, so it's just about time.

    In other words...it aged for 12 years?

    1. Re:Wine? by belmolis · · Score: 1

      Actually, this is an important observation. It tells us that WINE is a red wine. Nobody would age a white wine for that long.

    2. Re:Wine? by Yaotzin · · Score: 1

      And also no body would use a glass of red wine as a symbol for white wine. :-)

      --
      Error: No error occurred
    3. Re:Wine? by leomekenkamp · · Score: 1

      Totally off-topic, but I have been to Slovenia last year, and the proud employee of a wine cellar ("We even export to France!") showed me their long-term white wine cellar; some of the bottles there were 50 years old.

      He told me the old whites were very pleasing to the taste buds, and in the dictatorial 'communist/socialist' age many a bottle has been poured down the throats of party officials.

      --
      Wenn ist das Nunstueck git und Slotermeyer? Ja! Beiherhund das Oder die Flipperwaldt gersput.
  24. Even better analogy by Lifewish · · Score: 2, Interesting

    With the advent of local loop unbundling, it's possible to have another phone company hook your handset up to the rest of the country, by allowing them to implement the backend half of that specification. The result is ultra-fast dark fibre MANs in places like France, Italy and Japan (iirc anyway). By comparison, bandwidth rates in most of the US stalled years ago - the only counterexample is New York, and that was only an attempt to wipe out the cablecos.

    (I worked for a business analysis company specialising in telecoms over the summer vacation. This is one of the few things I can remember after 4 weeks of maths.)

    --
    For the love of God, please learn to spell "ridiculous"!!!
  25. AWESOME!!!! by Hellad · · Score: 1

    Now I can finally play Duke Nukem Forever on Linux!!!!!!!!!!

    1. Re:AWESOME!!!! by kusanagi374 · · Score: 1

      Well, if the fact that the Wine project took 12 years to get where they are while chasing a moving target is anything to go by, I expect that the DNF team will have finally found the perfect engine just a couple of years after Wine goes final.

  26. open Windows compatible OS exists: ReactOS ! by free2 · · Score: 1

    It does exist, and yes, it uses some Wine code:
    http://www.reactos.org/en/index.html

  27. Wine! by zekemacneil · · Score: 1

    There's no WINE before its time and no Southern Comfort til the lights go out.

    --
    Take off every Sig.
  28. Congratulations by p3d0 · · Score: 1

    You got the joke.

    --
    Patrick Doyle
    I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
  29. Congrats Wine Devs by benow · · Score: 1

    That's a ton of work. Congrats!

  30. WINE on Windows by SimHacker · · Score: 1

    Somebody should port WINE to Windows, so then you wouldn't need Linux to run Windows applications.

    <EmilyLitella>Oh, never mind.</EmilyLitella>

    -Don

    --
    Take a look and feel free: http://www.PieMenu.com
    1. Re:WINE on Windows by CaraCalla · · Score: 1

      I kid you not. Wine does run on Windows. This is to ensure that the api test cases in their test suite return consistent results across both platforms.

  31. Obligatory Python quote. by Ignominious+Cow+Herd · · Score: 1, Funny

    "A lot of people in this country pooh-pooh Australian table wines. This is a pity as many fine Australian wines appeal not only to the Australian palate but also to the cognoscenti of Great Britain.

    Black Stump Bordeaux is rightly praised as a peppermint flavoured Burgundy, whilst a good Sydney Syrup can rank with any of the world's best sugary wines.

    Château Blue, too, has won many prizes; not least for its taste, and its lingering afterburn.

    Old Smokey 1968 has been compared favourably to a Welsh claret, whilst the Australian Wino Society thoroughly recommends a 1970 Coq du Rod Laver, which, believe me, has a kick on it like a mule: 8 bottles of this and you're really finished. At the opening of the Sydney Bridge Club, they were fishing them out of the main sewers every half an hour.

    Of the sparkling wines, the most famous is Perth Pink. This is a bottle with a message in it, and the message is "beware." This is not a wine for drinking, this is a wine for laying down and avoiding.

    Another good fighting wine is Melbourne Old-and-Yellow, which is particularly heavy and should be used only for hand-to-hand combat.

    Quite the reverse is true of Château Chunder, which is an appellation contrôlée, specially grown for those keen on regurgitation; a fine wine which really opens up the sluices at both ends.

    Real emetic fans will also go for a Hobart Muddy, and a prize winning Cueve Reserve Château Bottled Nuit San Wagga Wagga, which has a bouquet like an aborigine's armpit."

    --
    Lump lingered last in line for brains, and the ones she got were sorta rotten and insane.
  32. One exists for PHP, so its not out of the question by Richthofen80 · · Score: 2, Informative

    Visual Studio is pretty powerful, relatively speaking. There's a plugin for PHP, (http://www.jcxsoftware.com/) so it wouldn't be the first time an open source programming platform was used in a Visual studio plugin.

    Also, in the new Visual studio HTML editor, there's a web standards dropdown so that the code will flag as errors if not part of the selected standard. The same dropdown could exist for Wine code. I'd use it.

    --
    Reason, free market capitalism, and individualism
  33. Thank you! by Dr.+Spork · · Score: 1

    I never claimed that the idea was original or non-obvious, though I didn't expect something to have already been announced. Thanks for the link.

  34. Re:No WINE Before Its Time by Ibag · · Score: 1

    My guess (I didn't do the moderation) is that it is considered off topic because:
    (1) it appears to be mostly a complaint about the legal drinking age in the USA
    (2) "No WINE before its time" is more of a reference to the fact that certain wines are aged greatly and that aficionado's won't drink the wine before it has had sufficient time to age. The title was a reference to the age of the wine, not to the age of the wine drinker.

    Overall, it would have been a not very joke had the title been referencing drinking age, but as it stands it is merely an off topic complaint about the drinking age. The intent may have been humor, but I don't think that a mod of off topic is completely unwarranted.

  35. C++ on Windows != MFC by ClosedSource · · Score: 1

    You're right about the Win32 API having a C interface, but you can certainly use C++ for Windows applications without using MFC.

  36. What is wine good for? by emuman_de · · Score: 1

    Wine runs Buhl Tax.

  37. I guess that means... by edunbar93 · · Score: 1

    It looks like the next version of Windows will be coming out pretty soon then. :)

    --
    "No problem. I have the capacity to do infinite work so long as you don't mind that my quality approaches zero."-Dilbert
  38. Someone clear this up for me, please: by Progman3K · · Score: 1

    >>[...]once you got something working it has never meant it would continue to do so, or do so properly. There may have been display glitches or things not functioning properly[...]

    Are they talking about Wine here or Windows?

    --
    I don't know the meaning of the word 'don't' - J
  39. So, when does MS-Windows Leave Alpha? by darkonc · · Score: 1
    The reason we're saying it's alpha is because we believe we still have fundamental changes to make on the way the internals work.'

    By that definition, I'd ask if MS-Windows has ever been out of an Alpha development state.

    --
    Sometimes boldness is in fashion. Sometimes only the brave will be bold.
  40. does it run coLinux? by Falcon040 · · Score: 1

    Do you mean, does it run coLinux? http://www.colinux.org/ I wonder...
    This is the best way to try linux on Windows, however, maintain the instabilities and insecurity of Windows...