Slashdot Mirror
First Release Candidate of Wine 1.0 Released
moronikos writes to mention that the first release candidate of Wine 1.0 was announced and released into the wild today. This new version includes only bug fixes as the team is in a code freeze while pushing for the full 1.0 release.
does it run linux?
"I think it would be a good idea" Gandhi, on Western Civilisation
I'll drink to that!!!
(seriously though...hooray WINE!)
I was always under the impression that WINE, based on how it is designed, would never be finished, or even close to a finished release point. I mean, yeah, I know 1.0 doesn't mean it's done, just that it hit a specific milestone, but even so, WINE, being considered a ⥠1.0 version seems to me like it shouldn't happen until it can at least come close to running most everything thrown at it.
Just my non-developer, non-programer, former WINE-user $.02.
"Don't meddle in the affairs of a patent dragon, for thou art tasty and good with ketchup." ~ohcrapitssteve
Because Wine is not an emulator, it is faster and uses less memory than emulators.
How well do 3d games work with emulators?
If you run Windows on a virtual machine, you will still need Windows for that. With wine you don't.
But obviously you are free to use what ever you like and what works best for you. As wine is not ready, it is not a perfect solution, even it does have some advantages for the applications that work with it.
Because WINE can run "Lander on the moon" from Windows 3.11 and Windows XP/later cannot.
What happens if I run Cedega from Wubi from wine from a virtual machine of Linux run from wine within linux?
I mean, I've been running Windows software under WINE for *years*. What's their definition of "1.0"? Does it really mean anything, or will we be getting 1.0.1, 1.0.2, etc monthly afterwards anyway just like before? Or is 1.0 some "complete feature set" release, suggesting that I can now run any windows software (I doubt that's true, considering that even MS Office is still a bit shaky).
http://www.winehq.org/?announce=1.0-rc1 pretty much has a list of bugfixes&features, just like any other release. Where's the beef in "1.0"?
A virtual machine is not an emulator either and 3D works in VMWare.
"Why would I want to use Wine when I can just run windows in a virtual machine?"
:)
You don't have a lot of spare RAM? (e.g. using VirtualBox requires enough RAM for the host OS + the RAM for the virtualized OS + the RAM for the app running in it; with Wine you eliminate the need for the virtualized OS)
You don't want to buy a Windows license/pirate Windows for a single app? (or more generally, you don't want Microsoft code on your system if you can help it?
.. before it is usable? :)
--I thought I was wrong once, but I was mistaken.
I think this is great Wine is finally reaching "1.0". I am hoping this version will be treated as a longer lived, stable, supported branch. This way developers might seriously target Wine as a platform or at least consider it a real "Microsoft Windows Compatible" target (Yea, it would be better if ports of apps were targeted to be Linux or Mac OS X native)
Sure it won't run all Windows apps perfectly - but then again, neither does Windows! There are lots of apps out there that have various bad code that often shouldn't even run at all but somehow gets away with working under a generic Windows XP install. Then they crash under Wine, Windows Vista, or even XP under odd configurations. And then there are the ones that do things different under different versions of Windows to get around bugs or varying behavior in Windows.
Also having a longer lived "1.0" branch would mean tips and tricks to getting individual programs to run would not become obsolete quite as quickly, and a Wine "1.0" users would not have to worry as much about apps breaking every few weeks.
At any rate, Wine has come a very long way - I remember when it was just trying to be a Windows 3.1 clone!
When I switched from Windows to Linux, it turned out that I was able to function without specific applications, there are Linux equivalents for pretty much everything.
Deleted
So, this would be Release Candidate version 0.01 right? ;-)
Because you do not want to support Microsoft by purchasing Windows? Besides, these days MS will not even sell you a version of Windows that runs best under a VM (XP for newest x86 computers, 98 for the rest).
.Net/Mono may be a better solution for a lot of developers.
I see a business model of developing programs for the dominant desktop platform but also certifying them to run properly under Wine for Linux users. If the application is explicitly Wine-aware, it shouldn't be that hard to get it Gtk+/Qt themed, use UNIX-styled file dialogs or call native libraries for Linux-specific functionality. Of course
I tried to find this from the Wine website, but couldn't seem to find it.
What does it mean to be 1.0 (if anything)? Is there any set of functionality that they were trying to hit for 1.0? Or is it just that "Many, many things work great, so let's just call this 1.0"?
Just curious...
Finally, I can test out Duke's new high-powered rocket launcher on my Hurd system!
doesn't wine still require windows files to run things like d3d? so to run it legally you still need to purchase windows anyway?
If you mod me down, I will become more powerful than you can imagine....
Just 2 more years until the actual 1.0 release?
Seriously now, this is good news. What bottle of wine should I open on the release day? Cab, merlot, syrah, late harvest... yup, late harvest cabernet it is!
"doesn't wine still require windows files to run things like d3d? so to run it legally you still need to purchase windows anyway?"
No.
"To any truly impartial person, it would be obvious that I am right."
Well... Lots of people have at one point or another in their life bought a computer that came bundled with a windows license. If you have and that computer currently isn't running windows or maybe isn't running at all, you can use the windows files legally.
/.Mattsson - My native language is not English, so please don't whine over linguistic errors. (That's lame anyway...)
..in 3 ..2 ...1 ....
I remember using it some time in 2004. It's been in development for quite a while...
Just look at the list of applications supported by Wine and you'll understand why I say that. Basically, if I can run Civ IV, Heroes IV and other strategy games on Linux, and with Matlab having a Linux version, there's very little to justify my using Windows. OK, there's Fruityloops, but that's it!
"The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
Unfortunately NO. If you read the license, the OEM kind, you see that this particular instance of Windows is only authorized to run on the hardware it was sold on. technically nothing block you to run it on another computer, but Legally, you can't (Especially if you can't get the little sticker sticked on the back of the computer).
The long answer is that not all of the DirectX features are quite there, I don't know if it's current but there's an overview here. The result is that some games won't play without native DLLs. Doing that requires the Windows files and adding an override in winecfg. This was a much larger issue before than it is now and it keeps getting fewer that need these overrides.
Live today, because you never know what tomorrow brings
Wine doesn't need any Windows DLLs to run Half-Life 2 and other d3d games, so no.
Those who would give up liberty to obtain working drivers, deserve neither liberty nor working drivers.
I can tolerate infantile tantrums, but I really hate sloppy use of language. Is our esteemed correspondent referring to people who copulate with coprophiliac goats, or coprophiliac individuals who enjoy the carnal pleasures afforded by goats?
Before Duke Nukem?
But you can download the direct3d runtime from microsoft without having to buy windows...
http://spamdecoy.net - free throwaway anonymous email - avoid spam!
Really? I'm looking at that page and don't you know, it seems that Direct3D v9 is 95% supported...
Nice to see Wine going 1.0. Does anyone know how much this impacts ReactOS?
The beef is described at
http://wiki.winehq.org/WineReleaseCriteria
In essence, 1.0 is just another release,
but with more stability (e.g. a month's
codefreeze and only very careful bugfixes)
and a few longstanding bugs
(e.g. serial I/O, dos apps) fixed not because
lots of people need them, but because it just
seemed wrong to reach 1.0 without fixing them.
Dan Kegel
Wine 1.0 Release Manager
You can also download Windows from The Pirate Bay without having to buy windows.
Blazing Spiders
Does this mean they'll start releasing binaries for OS X soon? I've compiled it a couple of times, but it's a lot of effort (you need to check out things from two separate svn repositories, run a script, hunt bugs, then compile for every version), and since they claim in the first paragraph of the front page to support OS X I'd really expect them to have regular binary builds.
I am TheRaven on Soylent News
If you read http://www.catb.org/~esr/writings/world-domination/world-domination-201.html#id247954 you will much better understand why they are pushing for a 'clean' 1.0 release. Its 'now or never' ...
:(
Personally I 'need' support for Rollercoaster Tycoon 3, not for myself, but for my girlfriend. It is the single showstopper for her linux experience, and until it is fixed, I'll never hear the end of it
Unfortunately, neither. He is simply stating that the subject shits while eating goat fuckers.
I'd like the opportunity to thank all of you who have been working hard on Wine all these years.
Recently Wine has saved my butt at work when my Windows machine auto-upgraded me to IE 7 (even though I have auto updates turned off). I was hard-pressed, then, to be able to reproduce a JavaScript bug that apparently was only present on IE 6 (and not 7, nor FF or Opera).
Being able to install IE 6 on my Ubuntu box was a godsend, and it worked well enough that I was able to reproduce the bug and fix it.
Kudos to you guys for your fabulous work, and thank you!
You can accomplish anything you set your mind to. The impossible just takes a little longer.
- ...don't have a copy of Windows to install and don't want to buy one.
- ...want the application window to use your normal X11 window manager rather than having to have an entire Windows environment with start menu and everything.
- ...don't want to wait for Windows to boot every time you want to run the application.
- ...want to run an application using 3D.
- ...don't have VMX hardware and don't want to shell out money for VMware.
- ...don't want the overhead of emulating the entire hardware.
I won't argue the reason that you don't want to run proprietary software, because if you're running Windows applications, that's probably not your problem. However, even so, I would feel it would be nice to be able to run e.g. a game without necessarily making my system a nest of evil. I've always felt that I don't mind games being proprietary -- they're a bit like movies or books in the way that it is the content, and not the code, that actually matters.That said, there are obviously lots of reasons for wanting to use Wine.
If I am going to make an application Wine-aware, why use the cruddy old Win32 API or (barf) MFC when I can use a true cross-platform API such as Qtk+/Qt as you mentioned but natively, not emulated? I see no reason to use OS-specific code for any newly-developed application anymore. All of my application coding is done in Java, or C++ with either Gtk+ or Qt. I want my crap to run natively everywhere, and with minimal effort.
24 beers in a case, 24 hours in a day. Coincidence? I think not!
"Is our esteemed correspondent referring to people who copulate with coprophiliac goats, or coprophiliac individuals who enjoy the carnal pleasures afforded by goats?"
The two behaviors are not mutually exclusive.
I'd continue this discussion at length, but I've got to go buy an elastrator. (Nip the competition in the bud, so to speak.)
"This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
32x games work pretty well on my Xbox :P
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
You ask why one would want to use WINE instead of a virtual machine (like VirtualBox or VMWare). Here are a few reasons that pop in my mind without thinking about it forever:
1) You don't want to buy an MS-Windows license
2) You don't want to support Microsoft
3) You don't want to waste multiple gigabytes of hard drive space for a virtual drive
4) You want to be able to browse and manipulate the MS-Win files under Linux
5) You want native Linux file permissions
6) You want higher possible performance
7) You don't want to waste many hundreds of megabytes of RAM
8) You want to be able to use thin client to display the resulting program
9) You don't want to have to install, configure, and maintain another whole OS
10) You don't want to fight possible viruses, auto updates that break things, Windows Genuine, etc, etc
11) You want each program to appear as a real process
12) You want to be able to compile a program to run cross-platform
13) You want native Linux filesystem access while in the MS-Win application
14) You want native CUPS/printing access while in the MS-Win application
There are LOTS of reasons for WINE to exist despite virtual machines. That is not to say that virtual machines are not useful, just different.
I hope so. I'll be less skeptical when Wine can run the games I actually play. CivCTP, for example, still doesn't work.
Now I'll have to find something else in pre 1.0 to use and childly complain about...
^[:wq!
Another reason you're forgetting, and I know at least this applied in the earlier days of Wine, but I've not verified it recently... if you're a developer (developer developer... etc) the wine libraries can also be used to compile linux native binaries from windows based source. It's not the ideal way to port software, but it works for a quick and dirty compile. The plus side is, while Wine is constrained to a single architecture for the purpose of executing windows binaries compiled for that architecture, the code could be compiled for any architecture or OS that wine runs under.
-Restil
Play with my webcams and lights here
Doesn't VMWare precisely emulate the hardware? I'm not really familiar with it, but I'm sure I don't have a direct access (well, manner of speaking) to the real hardware. Why is that if it is not an emulator?
(\__/) This is Lapinator
(='.'=) copy it in your sig
(")_(") so it can take over the world
The problem with wine has always been the moving target that is Windows. That's how Microsoft keeps itself relevant. Using its monopoly position to keep everyone on the upgrade treadmill.
With Vista so terrible and, really, only new machines going vista and old machines staying as they are on XP, the XP level of the Win32 API has remained fairly stable for a good number of years. In fact, it may be unlikely that Microsoft will ever be able to unify the user base on a new version of the API again.
(And yes I know that there are still users of 3.1, W95,W98,W98SE, etc. but these are static installations that typically don't buy new software.)
Wine, moving forward, has a very good chance of capturing a usable market because ISVs are reluctant to abandon XP in any meaningful way.
It's a fuzzy definition but I don't think VMWare so much emulates the hardware. It's probably more accurate to describe it as they provide drivers for some virtual hardware, that then maps to real hardware, and access to buses for some real hardware, mainly USB. Since it's not a direct emulation of the physical environment, that's probably why they themselves use "virtual machine" instead of "emulator" in their descriptions. That's a lot of words to say nothing ... oh well ... I typed it ... may as well submit it.
Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
Did they run out of numbers after the 0.999 version?
95% supported - is that sort of like 95% pregnant?
Technically VMWare is a visualizer because it executes the hardware instructions naively(except privileged instructions which require special handling). This makes VMware faster than emulators such as Bochs but virtualizers only provide virtual hardware that is roughly the same type as the host system. VirtualPC is an example of a product that is both. Virtual PC on Windows is a virtualizer. VirtualPC on the PPC Mac is an emulator. QEmu support virtualization but I think it also supports emulation as well for emulating say an ARM system on x86 hardware.
I've used Ubuntu for 3 or 4 years now, both on servers at work and a home desktop, I'm an EE and some of my design software is best run under windows so my work laptop has been winXP.
/home (.wine is here)
Recently bought a new personal laptop which came with Vista *cringe* this is my first experience using vista on a daily basis...
I tried an experiment, my desktop runs hardy and has a similar graphics card to my new laptop
Specs:
Laptop
Asus G1S-B2
Nvidia 8600M GT 256MB
3GB of ram
7200 RPM drive
1680x1050 screen (15.4")
Vista Home Prem
Desktop
2 8600 GTS non SLI driving 4 monitors @ 1680x1050
Raptor 10kRPM drive with OS on it
3ware RAID 5 ~1TB array with
4GB ram
Ubuntu Hardy
most recent wine stable from ubuntu reps
Compiz active, 4 screens, xinerma + twinview screen setup
Installed WOW as a test...
Installing wow in wine + wow was a breeze, obviously the drives involved were much faster but in terms of hand ups, there were none.
Installing wow in vista was fine until it wanted to update, i had figure out that i had to run the app as admin to allow it to install updates...why? no clue, bad programming.
Load times are obviously basically instant on the desktop, this is drive issue tho...
now the interesting bit.
FPS on the desktop are consistently 50% higher on the desktop with the same settings, even if I am rotating the cube in compiz wine runs wow faster than my desktop on a quite similar graphics card, granted the desktop 8600 runs with a higher clock (tho the asus laptop i have runs the 8600M faster than standard and is only 75Mhz core clock away from the desktop version) This is with the desktop card also driving a second screen and handing compiz. No hang ups closing and opening the window in ubuntu, flipping screens on the laptop results in a big ol' pause...
I'd tried wow under cedega a year or so ago and hated the graphics glitchs and the insane load times...
i have to say, wine has come a long way...the day when wine runs a graphics intensive app faster than it can run under windows is awesome, i find it hilarious that the wine guys can impersonate windows and run apps faster than they can run under the native OS....goes to show how poorly windows is really written...
anyway, i'm going to play with vista a bit more for my own knowledge then this laptop will most likely convert to hardy...given what i've learned i may try all my engineering apps with wine too, perhaps then i can convert completely...
-x
We know those stats aren't quite accurate. Here's basically how we generate them: we ask the various subsystems maintainers, "How close to complete do you think this is?" and then we munge in some true numbers on actual function calls (API's) exported by DLL's and the number we've implemented (and in and of themselves each API might not be 100% complete.)
So take those numbers with a grain of salt. In some cases, it's completely possible a DLL will be nearly 100% functional with not many of the API's implemented at all. Microsoft has invented thousands of API's over the years and some have been dead on arrival - no one has ever used them. Even Microsoft doesn't use all of their API's. That's why within Wine development there's an often cited development method of, "Show me an app that actually uses that."
Finally, Tom hasn't updated those stats in almost a year and we've done a lot of work since then. (Big kudos to Tom Wickline for tackling that stuff.)
So what Wine really aims for is to take the most common few thousand API's and try to do them really well. Then we flesh out some bits around that. Then we stub out things around that and finally there's bits we just haven't even started.
----- obSig
If wine were to be integrated in some of the larger distros I am convinced the larger exposure will speed along development, and speed the acceptance of Linux in the workplace.
Seven Days with Ubuntu Unity
Alright guys, this release is 15 years in coming. I'm not aware of any other free software project that's taken 15 years to get to 1.0.
We know we've got some core architecture just right. That's taken a long time to get there. Now we have a lot of bug squashing to do and in many cases it's pretty amazing how quickly regressions can be found, bugs tracked, etc if we just have a few more eyes on this release.
So we put together a list of things you can do to help us out - check it out here:
1.0 regression hunting. And hey! We're giving out t-shirts to the folks who help us out the most.
Notice we didn't say anything about jumping in and writing code? You're certainly welcome to, and in some cases there might even be some low hanging fruit. However, without development experience on Wine's codebase your valuable time might best be spent regression testing your favorite game!
As always, thanks for all the support!
----- obSig
IranAir Flight 655 never forget!
Some things you may have not considered: .NET package in it's most current version and runs on Windows, the dominant platform for most any (workstation-)thing today. .NET >=2005? You should, it may change your opinion. Eclipse and co. are nice, but as far from being competition to VS.NET as IE6 is from being a great browser. (IE7 ain't great either, but they changed the direction and 8 may even get close to useable).
- Performance: I don't care how fast Java benchmarks, every Java app I've ever used feels slow and laggy. Even if the language itself would execute stuff faster than hand-optimized assembler (which it obviously doesn't), the GUI-toolkits feel slow.
- Functionality: Go ahead and find me a toolkit, any toolkit that's as extensive as the whole
- The IDE. Have you ever used Visual Studio
Ummm... because the WIN32 code's already written?
.EXE should work on all X86-32 Linux distros. Can you say that for any other GUI toolkit?
There are a lot of windows programs out there whose developers would like them to be cross-platform, but can't afford the effort to rewrite them in a cross-platform toolkit. WINE allows them to test the waters and determine whether there's even any market for a Linux port.
One other (minor?) consideration. WIN32/WINE might just solve the problem of targeting multiple distros. Like it or not, you've got to admit that the Windows ABI hasn't changed much in years. And that's a good thing. It's been 'good enough' to base apps on for a long time, or at least app developers have worked around its defficiencies. In any case, a single
Posted from my Android phone. Oh, I can change this? There, that's better...
If you read my original post, I specifically said for all new development work.
24 beers in a case, 24 hours in a day. Coincidence? I think not!
I gave three examples, all of which run on Windows, all of which are extensible. I would rather write a solid core of OS-independent code and leave a few choice functions to be OS-specific, localizing that code and leaving the core business logic OS-neutral. In reality most of the time there is little to no need for OS-specific code unless you are writing 3D games (even then it's debatable, there are cross-platform libraries such as OpenGL) or something closely tied to the operating system to begin with (think Windows sysinternals).
I am not blowing smoke out my ass. I develop cross-platform software for a living, and spend less than 1% of my time dealing with anything operating system specific. And my application looks very nice, despite being Java. Of course we also have a custom UI layer on top of Swing, but even that is OS-agnostic.
Now to address your main point: I an not a .net developer but from what I have seen it is nice. I do use Visual Studio 2008, and I like it. Sure it is not perfect, but it works well and has a debugger that blows anything else out of the water. Learning the .net architecture in general and C# specifically are on my todo list, but I do spend time honing my Java and C++ skills so it is only a matter of time. I think maybe slowing the Earth's rotation would help so I have more hours in the day. Maybe I need a doomsday device first...
24 beers in a case, 24 hours in a day. Coincidence? I think not!
The ones I've seen says that you can only run the license on the computer the license-sticker is on.
If you move the sticker, you move the OEM-license.
Same thing if you buy a retail license. There's a sticker that you must attach to your computer. If you don't, Balmer will come 'n throw a chair at you. =P
Apparently, this will make it harder to make a counterfeit-version of windows. =P
Rant:
What the hell is a non-genuine windows anyway?
In my mind, this is something like GNU/Linux with Wine and a windowmanager that looks like windows XP that someone is selling as "Windows XP"
An unlicensed copy of Windows XP is still a genuine Windows XP.
licensed != genuine
unlicensed != counterfeit
Someone needs to give the people at MS marketing department an english-course.
/.Mattsson - My native language is not English, so please don't whine over linguistic errors. (That's lame anyway...)
Well the exact term on the page is "95% complete", and if the 5% that isn't implemented is just never used by game creators, it won't be missed.
DX8 support in wine has been solid for a while now, and it's listed as "95% complete" as well, for what it's worth.
Still...it's hard for me to be enthusiastic when the only piece of software that I really care about running in Linux (Google Talk) isn't functional...
Oh well, perhaps somebody will fully implement Jingle VoIP library in some Linux IM client really-soon-now (tm) (so I can talk with computer illiterate Windows users for which Google Talk is perfect when it comes to ease of use, Skype suffers too much for featuritis; oh, and Jingle/GTalk working better on slow connections is a nice bonus)
One that hath name thou can not otter
With regards to the "windows is a moving target" discussion that always comes up with WINE, the "but specific versions, particularly legacy ones, aren't." answer sufficiently addresses the platform's past. In fact, I strongly suspect that WINE on *nix could be a serious contender when certain cranky legacy systems have to be replaced. What I've seen less about is the future. The new .net stuff is probably mono's department; but loads of common windows stuff is still win32. There the moving target problem still exists.
It would make the future very much easier if the case could be made to software vendors that the *nix market is, or might soon be, of value. They would then have an incentive to keep WINE in mind while developing. The changes wouldn't need to be immediate or radical, just trying to keep out of ill-supported areas of win32, where possible, and bringing things that they run into to the WINE team's attention.
Obviously, some vendors would not, for technical or business reasons, be willing or able to do this(Office, some games, etc.); but those that can would be useful. In particular, this might be really helpful to address the class of critical but unsexy apps that *nix is often weak on. Bookkeeping, inventory, payroll, various other stuff in the category of boring but common business niche software.
The best performance under a VM is actually with 64bit XP. More APIC-friendly, newer codebase (based off Windows 2003, iirc) etc.
The problem with that is that 64bit XP is poorly supported at best, and for some reason I thought Microsoft never sold it directly, it was bundled with 64bit hardware sales... which basically leaves you with MSDN (if you have access) or piracy for most users, for an OS that may not even run what you want.
Virtualizing Windows just generally sucks.
Traditionally the monopoly has made some new API and just made it something you have to install. The old VB runtimes. The .net runtime. The whatever runtime/library/something-or-other.
They can still make up a new api every couple of years and get that running on xp too. Make the latest Visual Studio generated apps use it and you've got a lot of developers using it to make little programs. And big programs.
Which makes a lot of catching up for the WINE guys. Which is how the game is played I guess.
Maybe if they get far enough with XP compatibilty the new runtime installer would run in WINE. That'd be neat.
It would be nice if this application worked a bit better before going for a 1.0 release. Even with all the windows DLLs in place, it still proves to be a very unpredictable program with poor results for about 90% of the executables out there.
I'm not knocking the wine project, but it seems to be a LONG ways off from the whole number version realm.
No.
Furthermore, you can't use the native versions of the D3D dlls in Wine even if you wanted to, unlike some other more mundane dlls.
Game! - Where the stick is mightier than the sword!
...it's still not good enough. I will continue to have a full-fledged version of Windows on my computers until Wine can run MS Office flawlessly. That includes plugins for said suite. IOW, until I can run Excel and use Solver w/out the system crashing, it's not good enough.
Additionally, it would be nice to have MS Office 2007 support. I know you're working on it, keep up the good work, but until you get that done, I'm still going to use VMWare or reboot into Windows.
But seriously, can't wait until you figure out how to get Office 2007 supported; then I'll push my company's IT department to let me get Linux installed on my work laptop.
Maybe now the WINE team will start focusing on compatibility with 64-bit programs now that WINE 1.0 is going to be released.
You want developers and QA to spend most of their time on the platform that will be your primary market. Sadly, Windows will be the most common answer for a desktop application. Gtk+/Qt are not exposing all the capabilities of Win32 API. For a serious application, you will likely need custom controls that can not be easily ported even if you have the source code. You will want good interoperability with other Windows apps such as MSOffice through COM or copy/paste. When Java is not enough for your UI/system integration/performance needs, using Wine will save serious effort over maintaining multiple binaries.
Does the EULA let you *use* it without Windows, though? (Seriously, I'm too lazy to check for myself.)
Excellent year...!
"Still...it's hard for me to be enthusiastic when the only piece of software that I"
Maybe you could be enthusiastic for what it means to other people.
Damn Wine developers never finish anything they start do they? Not one single 100%
So what?
The Pirate Bay is not the Microsoft website.
We are Turing O-Machines. The Oracle is out there.
For C++ development I seriously prefer VC++, or Borland32 5.5 or even the Digital Mars compiler.
Compared to those, GCC has bugs and is slow as hell.
We are Turing O-Machines. The Oracle is out there.
We are Turing O-Machines. The Oracle is out there.
"happy for other people" - sure, why not :)
But enthusiastic...no, sorry, it only works that way when in given thing there's enough mojo for "me" (and I think the sentence you quoted was clearly enough from my point of view)
One that hath name thou can not otter
the point i was trying to make (though unsuccessfully) was that microsoft offer the direct x download for use in windows, not in linux.
Blazing Spiders
Wine might reach a point where it is more compatible with Windows apps than the latest Windows itself.
Good luck running 15 years worth of Windows apps on Vista. I'd bet Wine does that more than the latter.
Ohh the license.
In that case, yes, the difference between them is smaller, you can't legally use any of them (DX in linux or full WinXP from TPB).
We are Turing O-Machines. The Oracle is out there.