[Wine] Code freeze, or catching up with new features

David Gerard dgerard at gmail.com
Sun May 11 15:40:34 CDT 2008

2008/5/11 James McKenzie <jjmckenzie51 at sprintpcs.com>:
> vitamin wrote:

> > Don't excpect anything spectacular out of Wine-1.0. It might run said list
> of programs without major issues. Other then that it will still be the same
> - mediocre - wide range of broken apps. Because they are just that - broken
> apps that shouldn't even run at all, but they do because windows coded to
> hide bugs.

>  Then we need to 'break' Wine in the same ways.  Just because the folks at
> Microsoft decided to use 'hidden' code to get things to work right does not
> mean that we have to take the high road and attempt to make them fix it.  We
> definitely need to fix code in Wine that is truely temporary and to continue
> to add features that should work in a 1.0 release.

Yes. Unfortunately, app-specific tweaks are how Windows actually does
things - so you can't implement a fully compatible Win32 API without
doing the same. Appallingly inelegant and a disgusting offence against
all decent software engineering as it may be. (Because you could say
just that about Windows.)

At least it can wait until after 1.0. Get it working first, *then* break it.

(friendblaster.exe detected, file size and MD5 match? Report user's IP
to spamcop and cause their PC to catch fire.)

- d.

More information about the wine-users mailing list