SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?


To: TigerPaw who wrote (45447)5/26/2000 11:31:00 AM
From: sandeep  Read Replies (1) | Respond to of 74651
 
If the WINE layer doesn't work because of undocumented APIs (and not new documented APIs), then Microsoft must be held responsible.

A remedy of requiring complete documentation and penalty for failing to do so is a good remedy, I think.



To: TigerPaw who wrote (45447)5/26/2000 11:53:00 AM
From: SunSpot  Respond to of 74651
 
Microsoft cannot document Windows API's themselves. The problem is not about whether Microsoft documents it or not, but that Windows source-code cannot be copied to Wine because it is intellectual property of Microsoft.

No matter how Windows was intended to be, there will always be bugs and bugs and bugs, and the cure has always been workarounds. These workarounds are part of the "Windows standard", and without simulating Windows bugs, Wine would never have come so far.

Wine is a nice tool for running some Windows apps on *nix, and it greatly simplifies porting Windows software to *nix, like Corel does, but it will never be another Windows. In business, Terminal Server solutions will probably prevail, and games will probably be ported in order to gain full speed. I have seen several Windows games on Linux, like Half Life and Quake, and they do run, but since they don't have access to DirectX, and they run using the X-Windows protocol, the performance is not so great.