TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: CSS with Netscape From:"Eric L. Dunn" <edunn -at- TRANSPORT -dot- BOMBARDIER -dot- COM> Date:Thu, 25 Mar 1999 14:09:10 -0500
"Wing, Michael J" <mjwing -at- INGR -dot- COM> wrote : <<Meanwhile, Microsoft's
browser has a robust and large document object model. It handles most types
of scripting and ActiveX controls. This is what Microsoft means by their
browser development being restricted by standards. If Netscape will not get
off their butts and make their browser better suited for web-based
applications, they will be left in the dust as these applications become
the next major programming environment.>>
However, I fail to understand why Microsoft can not respect the standards
and add all their "inovation" to the mix. Standards in no way whatsoever
hamper development of content or functionality outside the standard. It is
IMO be perfectly reasonable to expect software to fully respect the
standards in place as a base. Standards exist to lay down the minimum
reuirements not to hamper the development of newer or better ways of doing
things. It took Ralf Nader to whip the auto industry into shape and it's
about high time someone did the same for the software industry. Does
Volvo's safety inovations suffer due to automotive safety standards?
If you don't like a bare bones browser or require extra features, then
fine. Some people can make do with a Lada, some need/want more performace,
comfort, or luxury. But both have to meet the same minimum standards to run
on the road.
The point is that the "full featured" browser should treat bare bones code
in the same way as the bare bones browser and follow the stadards that have
been put in place.