Not to be an apologist for Microsoft, but this is one case where they
are at least less guilty than some.  Instant Messaging was first
introduced by AOL.  Microsoft created a client that would allow
communication with AIM (AOL Instant Messaging), and AOL immediately
rewrote their client to break Microsoft's software.  There were several
iterations of this process, all designed to require everyone wanting to
talk to AIM to use AIM.

But, the basic point is certainly valid.  If we build to standards,
rather than trying to create our own, the world is better off.  AOL's
Instant Messaging, Netscape's custom tags and lack of support for HTML
4.0 and CSS, and Microsoft's "Embrace and Extend" policies are all
egregious examples of software approaches that are intended to "require"
the use of a specific tool.

Denis Anson, MS, OTR
Computer Access Specialist
College Misericordia
301 Lake St.
Dallas, PA 18612
email: [log in to unmask]
Phone: 570-674-6413


>
>         The nearest thing I can compare it to is the deliberate
> incompatibility built in to the instant messaging systems of
> Microsoft's and others software.  If you need to talk to a friend
> who is, so to speak, on the other side, you better pick up the
> phone, send email or get on your skate board and go see him or
> her because you are otherwise up the creek.
>