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: Relevance of Java to TWers? From:Michael John Little <hypercom -at- C031 -dot- AONE -dot- NET -dot- AU> Date:Sat, 26 Oct 1996 09:55:08 +1000
Hello Majan, Chuck,
I read your email with interest, as I am currently developing a Java
training course. Like you, I am a technical communicator. I have included
my comments amongst yours.
> From: Marjan Bace <maba -at- MANNING -dot- COM>
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: Relevance of Java to TWers?
> Date: Friday, 25 October 1996 5:29
> At 10:15 AM 10/24/96, Chuck Beck wrote:
> >Esteemed colleagues:
> >In preparing to do a presentation at an upcoming STC regional
> >am grappling with the question of how Java is likely to impact on our
> >and careers as technical communicators.
If we are writing stock standard users manuals for software products, and
we don't have to look under the hood, then not a great deal. Perhaps for
software companies it means that the operating system becomes irrelevant,
so they will be able to better focus their software development onto one
product, instead of developing in parallel a product for Windows, MacOS,
and all the different variants of UNIX. It creates a tremendous level
playing field, so you could really see how fast CorelDraw runs on WinTel,
MacOS/PowerPC, or a Sun Solaris...
> >give some current examples of how they are being used on the WWW, and
> >out some thoughts about how this new techology will likely affect us,
> >specifically, as technical communicators.
For TWers, if we want to be content providers for the WWW?which is a
logical extension of developing online documentation?then at the moment you
for the programmers because it will run on ANYTHING!...toasters, washing
machines, faxes, mobile phones...if the microcontroller the Java Virtual
Machine, then you can write a Java application for it. For TWers writing
engineering documentation, that they will see a change, because my
prediction, in two years people will be writing code in Java, not C++
> >I have some ideas of my own, but it occurred to me that this
> >would be even more effective if I could offer insights others may be
> >offer. I would appreciate any thoughts any of you would care to share
> >me (especially if you have any personal experience with Java or
> >and I will be more than happy to give public credit where credit is due,
> >I use your input as part of the presentation.
MIchael John Little
Sine Timore, Per Ardua Ad Astra!
Knowledge is Power, yet True Power is Communicating Knowledge