Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uunet!bfmny0!tneff
From: tneff@bfmny0.BFM.COM (Tom Neff)
Newsgroups: comp.unix.sysv386
Subject: Re: Pcomm / A ProComm lookalike
Message-ID: <67828727@bfmny0.BFM.COM>
Date: 8 Feb 91 00:50:45 GMT
References: <6248@spdcc.SPDCC.COM> <1991Jan29.132526.1577@nstar.rn.com> <1991Jan30.205523.2874@rfengr.com>
Reply-To: tneff@bfmny0.BFM.COM (Tom Neff)
Lines: 16

In article <1991Jan30.205523.2874@rfengr.com> rfarris@rfengr.com (Rick Farris) writes:
>YAM is great for writing scripts, but, for interactive use,
>it cannot compete in any way with Qmodem or ProComm.

That's what the scripts are FOR.  With scripts you can INDEED be as cute
as Procomm or Qmodem.  Chuck's sin is not supplying them pre-written as
a YAM front end.  His bet is that his target audience doesn't really
want them anyway.

And it's true that within the UNIX/GUI tool philosophy, the cycling,
tagging, and cute boxes ought to lie outside the comm engine.  Once the
engine is running, YAM has little serious competition.

-- 
"Nature loves a vacuum.  Digital    \O@/    Tom Neff
  doesn't." -- DEC sales letter     /@O\    tneff@bfmny0.BFM.COM