Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What undocumented APIs / interfaces are not understood? Would seeing Microsoft source help?

0
10 Posted

What undocumented APIs / interfaces are not understood? Would seeing Microsoft source help?

0

The best solution would be if the Windows API were fully documented, so Wine could be a perfect “clean-room” implementation. Seeing the source code might make it harder to prove that no copyright violations have taken place. That said, the documentation is often bad, nonexistent, and even misleading where it exists, so a fair amount of reverse engineering has been necessary, particularly in the shell (Explorer) interface. The biggest problem facing Wine though is simply lack of manpower. At one point, over 5000 people were working on Windows 2000. While Wine doesn’t need to replicate all of Windows (we only cover the parts needed to make Windows programs work), that’s still nearly 8 times more people working simply on one release than have ever worked on Wine, in the history of the project.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.