Ask Jeremy White and Alexandre Julliard About the Future of WINE
Last week, after 15 years of development, tempered by the need for arduous reverse engineering, the WINE project released version 1.0. What "1.0" means for WINE is neither that the project is finished, nor that it is perfect, but rather that the software runs a small subset of specific freely downloadable Windows applications. That's not to say it doesn't run scads of others, too -- the apps database is proof that thousands of programs run to at least some degree. Here's your chance to ask WINE developer Jeremy White and WINE project lead Alexandre Julliard (both of Codeweavers) about the future of WINE, or any other questions about the project that cross your mind. The usual Slashdot interview rules apply; please ask as many questions as you'd like, but limit yourself to one question per post. We'll pass on the best questions to Jeremy and Alexandre for their answers.
I hear people often say that its important for Wine to be able to run major applications like Office and Photoshop. However, from a migrate to Linux point, I think the thing that holds people up the most is the small propreitary applications that are written for a specific function. Is there going to be any focus on those programs in the future? Disclaimer, I realize that there are tens of thousands of such apps, but maybe many have something in common.
Comment removed based on user account deletion
Has anyone from WINE engaged apple to see about getting wine better ported and available to OSX users? I am currently using parallels to support my win32 needs under OSX, but that is all. I do not like the idea of having to pay FRP for a full windows OS when all I want to do is run win32 apps. I think it would be awesome to see WINE shipping directly in 10.7, with support from apple.
Modding Trolls +1 inciteful since 1999
Wine was a great idea in its day but now with multi-core CPUs and excellent VMs (VMWare, VirtualBox, etc.) do you still see the need for Wine?
Question:
With Vista stumbling terribly and now XP being removed from the marketplace, in the medium term do you see Wine / Linux as a true potential commercial viable alternative rather than just a niche as it is now? If so, what financial steps have you taken to prepare for legal threats?
Thanks!! :)
How does your usual reverse engineering work flow look like? (How do you start, short note on tools, do you use (unit) tests)
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
What pieces of software that aren't working do you think are the most important to get working next? Have there been any programs that you never expected to have so many people request?
Comment forecast: Bits of genius surrounded by a sea of mediocrity.
Will the WINE project try to implement the Windows Vista APIs or will the project aim only for the Windows XP APIs? Seeing that Windows Vista didn't catch on and a lot of applications are still written for Windows XP. Maybe it is a good time to iron out the DirectX 9 and Windows XP DLLs.
From Zero to Hero... Starbuck Zero
When I first started using GNU/Linux in 1999, I knew that if I wanted to run Windows apps, the best way to go about it was to dual-boot. Now, it appears that the most convenient way to run Windows apps is to run Windows in a virtual machine. Since both dual-booting and virtualization appear to be more convenient ways to run Windows apps than WINE, where does WINE fit in?
I write sci-fi for metalheads
Hi,
Suppose that the APIs delivered with Windows XP are the 100% baseline for app compatibility that you want to achieve. Could you give an estimate of how much percent is already implemented and how much work it would be to implement the rest?
Thanks!
I would like to ask what your plans are to improve the process of/increase the number of people contributing to Wine? Do you plan to provide more feedback on patches (they are often ignored without comment), for example? Do you see Alexandre ever trusting other devs enough to take over subsystems/individual dlls?
Wine seems to making large improvements on ease of use in Linux desktops, especially with the simple installation afforded by package managers. However, installation of Wine on Mac OS X remains complicated.
Are there any efforts underway to simplify the use and installation of Wine on Mac OS X?
What is the biggest obstacle in getting 100% Win32 API compatibility? Is it undocumented "features"? Inaccurate documentation from Microsoft? Fundamental differences between "Windows" and "Linux"? Other technical limitations?
Wine today runs fine, but as desktop linux visuals become better with nice themes, wine becomes more and more an alien in your computer. Is this any plan to make it more native in the look & feel?
What plans do you have for better multi-threading support?
I've never used wine to run windows programs. However, I have used the source code as a form of documentation/verification while doing win32 programming. How do you feel about that?
Do you even lift?
These aren't the 'roids you're looking for.
With you working for codeweavers (which produces the excellent Crossover Linux package), do you see a conflict of interest in wine not directly supporting MSOffice 2K at the gold level?
As a related question:
How do you decide which portions of the code you write goes to wine and which are crossover-specific?
Help! I'm a slashdot refugee.
As I understand it, Wine was originally intended to be both (1) a set of libraries that Windows developers could recompile their code against to run on other operating systems; and (2) a compatibility layer to run unmodified Windows binaries on other operating systems. Which one was the "primary" intent of Wine originally?
Also, nowadays, it seems that the vast majority of people use Wine in mode (2). Few developers have used the Wine libraries to recompile their code. Is this a fair assessment? If so, how does this affect the way you develop the Wine codebase? Do you see this changing in the future?
Throughout all your adventures with the Win32 API, what would you say is the most brilliant part of the system, and which is the most horrible? Like, for which systems would you say, "Wow! I wish I had come up with that!" or "Dear GOD NO!"
I've loaded WINE numerous times over the past years - primarily to play 'legacy' video games/simulations. I've had limited success with the specific stable of games I am interested in and own. I've also paid for Cedega which was equally dissatisfying. With the demise of Loki Software, and the limited titles that have been ported directly to linux by icculus.org and LGP to date - there is still a very large sector of games that many would say hold back adoption of linux as a gaming platform.
What are your views on WINE gaming, and what are you doing (if anything) to address this issue?
Lodragan Draoidh
The more you explain it, the more I don't understand it. - Mark Twain
How much do the Wine and ReactOS teams contribute to each other's projects? What are your personal takes on ReactOS? Do you think it can become a serious Windows replacement?
Stupid flounders!
Any plans to implement DX10?
Or at least make DX9 games (like HL2EP2) work decently.
Will WINE or Codeweavers make a commitment to fully support a recent vintage of MS-Office (2007, 2003, XP) as a platinum app? By "fully", I mean everything in the suite--including Access, Outlook, Publisher, the little helper apps, VBA, clipart, etc. When I look at WINE's appdb, I see no consistency to the ratings people give to recent versions of MS-Office, which means users are having varying degrees of problems. Unfortunately, for many people (myself included), MS-Office doesn't work with WINE... Why not assign a group of coders & testers the task of getting 100% of the functionality of this one extremely popular app working???
Windows 3.1x calc: 3.11 - 3.10 = 0.00
Wine was started before the rise in popularity of FOSS and Virtualization. If Wine did not already exist and someone pitched the idea of Wine to you would you: A) Tell them that it'd be better to promote FOSS software that can be ported to other OSes. B) Tell them to just use a virtualization product. C) Start Wine. Would you do it even if you thought FOSS would become more common than closed source applications in the future?
My Hello World is 512 bytes. But it's also a valid Fat12 boot sector, Fat12 file reader, and Pmode routine.
I know about usb-storage support, it works perfectly, but what about full USB support?
Many USB devices require Windows apps to use them correctly. For me, Line6 USB products for audio come to mind, but i'm sure there are plenty of others.
From what I've seen in the wine-devel discussions, it looks like a tough challenge. Are there any takers yet? What are the main showstoppers? Or, am I totally wrong on my figures and these other USB devices are not used that much?
If these are a lot of questions, please stick to the first one :)
WINE shouldn't really release like a label or logo for games of some type that would allow buyers of some games to know that said game would play on an alternative platform than windows like Linux with WINE of course. that way it could help get the word out to regular people that yes many of the applications that you pay hundreds of dollars for can run on an open platform. you could do it through the website and the developers of other applications and games could include links to their apps being supported and links to bug fixes and stuff.
Hm... I'll bite!
Over the past few years we've seen major architectural concerns calm down. The DLL separation took a while, we had the major filesystem rewrite, and then in the past year we had the big windowing changes. Oh, and then throw in the big changes to support copy protection, real services, and oodles of D3D updates.
So where does that leave us? Are there any major architectural changes in the pipe? There are rumors Codeweavers will integrate a DIB engine - what does that do and why is that necessary? What about in the RPC world? Jeremy - you've battled with audio, how do you feel Wine is doing with regards to audio support?
----- obSig
Number of people ask what percent along are you.
Looking at where you are now, and what it's taken to get there... can you give an estimate of MAN hrs to get to a number of MILE stones you might pick..
win 3.1, win 95,win 98, win 98se, 2k, XP. .net versions
server versions
Vista?
direct x versions
(no i didn't miss ME is there anything that "requires it?")
I would think it's understood that one can't give 100% accurate numbers but i think it might be of value to everyone involved to have an estimated times for some target goals.
And thank you for your time and all the hard work you have put in to this.