Rick Berger
04-13-2000, 01:24 PM
I'm not sure what Glen Davis is complaining about - IE appears to support
emerging standards better than NS while at the same time, making best effort
to remain backwards compatible.
My experience has been that IE supports DHTML, CSS, and XML, (with coherent
access to the respective DOMs) much better than NS (although not so well
on MAC).
For CSS enabled documentation, I pretty much have to specify IE.
Backwards compatibility and support is a reality for any software company
(I've worked for several, & it has always been a headache, but a reality
that couldn't be ignored. Apple is about to learn this with OSX, I think,
which is going to require a huge leap on the part of both users and developers.)
The fact is, there are still people writing code for Win3.1(!!), let alone
older versions of browsers. MS's (and any other company's) loyalty ultimately
has to be to its customers.
-----------------------
Opinions 2c, dumb looks free.
emerging standards better than NS while at the same time, making best effort
to remain backwards compatible.
My experience has been that IE supports DHTML, CSS, and XML, (with coherent
access to the respective DOMs) much better than NS (although not so well
on MAC).
For CSS enabled documentation, I pretty much have to specify IE.
Backwards compatibility and support is a reality for any software company
(I've worked for several, & it has always been a headache, but a reality
that couldn't be ignored. Apple is about to learn this with OSX, I think,
which is going to require a huge leap on the part of both users and developers.)
The fact is, there are still people writing code for Win3.1(!!), let alone
older versions of browsers. MS's (and any other company's) loyalty ultimately
has to be to its customers.
-----------------------
Opinions 2c, dumb looks free.