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.
>I would have thought only an independent author could produce a work
>so uncompromising. It says much for Apple that the company would have
>allowed its in-house writers to publish such information, and even
>given a copy to each customer.
Back before software became a big business it was considered normal to get
into all such details. One of the things that made the "IBM 650 Principles
of Operation" so much fun to read was it they described the admittedly
simple programmer-visible machine in complete detail. Early DEC, HP, and
Varian manuals did the same.
Few computer users nowadays know or care much about the programmer-visible
architectures of Pentium, SPARC, or PowerPC. Nor are they usually much
interested in the available system calls under windows, unix, or the mac OS.
When you work with FrameMaker of Photoshop, you're many layers above the
terra firma of the hardware.
It's so squishy up there and so vastly more complex than Applesoft BASIC,
that you couldn't write a complete description of it. The next version of
the software would be out before you finished, and you'd have to start over.