2.2 Microsoft the Monopolist |
2.3 Practices I: Undocumented Calls |
In the beginning, nobody would write Windows programs anyway. As a result, Microsoft had to write them, just as the first Macintosh software was created by Apple. Once people started writing software for Windows, it was discovered that there were some undocumented system calls and routines that were regularly used by Microsoft programmers, but that were not broadcast to the outside world. In theory, undocumented calls make sense; Microsoft might want to experiment with a feature without committing yourself to a situation where thousands of developers around the world would count on its continued existance. In practice, credible allegations were made by many developers that use of these calls gave Microsoft programmers a significant competitive advantages, making their software run smoother and faster than competitors'. Books such as 'Undocumented Windows' and 'Undocumented DOS' explore this complaint in depth, and explain the controversial calls in detail. As a result, the advantage to Microsoft developers has been reduced, but the bitterness this has left in some people's mouths lingers on. Microsoft has claimed that a "chinese wall" has been erected between members of different development teams, making it impossible for in-house developers to take advantage of the undocumented calls. I find this impossible to believe, especially since the undocumented calls have clearly been used by Microsoft's programmers in applications like Word or Excel. There doesn't seem to be much question that people who have been steeped in the Windows culture are going to be best at programming under Windows. As a result, Microsoft's near monopoly on large Windows software packages is likely to continue. |