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.
>> NS will eventually read VBScript, too, so
>> the compatibility will flow both ways.
I'm not so sure I'd count on that one. An astute observer recently pointed out
that MS had to support Java if it wanted to be taken seriously in the Web
world. But the opposite doesn't hold true. NS has to do everything in its
power to prevent MS from being able to blend its Web capabilities down into
the operating system. As long as NS doesn't do VB -- and IE does do Java --
people will have to pause and think about which systems they build their
system architecture on. If NS **does** do VB, then MS servers become much more
of a no-brainer -- especially if they come pre-installed on every desktop unit
sold in the USA.
Doesn't invalidate your basic point -- just that if I was making the choice
right now, I'd be learning Java.