Cerulean
Member

Registered: Dec 1999
Location: Chandler, AZ
Posts: 289 |
Regarding Microsoft and product binding.. The biggest problem I see is where to draw the line.. Sure, it simple to point out an Acme Widget example where they are bundling their Widgets with their Gadgets, however, with regards to bundling with the OS .. how can you define what should and should not be included?
Technically everything beyond DOS 1.0 from Microsoft that is included with the OS would be bundled. Disk maintance utilities (instead of using PC Tools or Norton), compression routines (instead of Stacker), GUI (instead of the various GUI shells such as GEM..), TCP/IP stack, Networking drivers, and then finally Internet Explorer (or basic Internet APIs) ..
Sure .. technically you COULD rip out all of the internet functionality that Microsoft has included in their system, however, just think of all of the applications that now use that plumbing would instantly be broken because it was no longer there..
IF it was limited to not including this functionaility when competitors were able to add new functions to their base system, it would only be a matter of time before it is considered obsolete.
Granted, certain practices that Microsoft has done such as forcing companies to load Windows and only Microsoft software (Office, works, games, etc..) can fall under the traditional product binding and technically splitting the company into two parts (OS and Apps) would solve this issue. However, whats to stop the OS company to decide to bind many of the application features right into the OS? Ie, system wide spell check, database system, advanced page formatting, integrated web content editor (U have Wordpad for paper docs, so why not?), voice recognition, etc..
Its definitely an interesting subject.. Yet another area where traditional law just doesn't seem to have an answer...
|