Xref: utzoo comp.sys.mac:40717 comp.sys.mac.programmer:9892
Path: utzoo!attcan!uunet!ginosko!shadooby!mailrus!cornell!uw-beaver!uw-entropy!quick!happym!polari!6sigma!blm
From: blm@6sigma.UUCP (Brian Matthews)
Newsgroups: comp.sys.mac,comp.sys.mac.programmer
Subject: Re: 11 New Features
Message-ID: <311@6sigma.UUCP>
Date: 22 Oct 89 22:49:56 GMT
References: <969@bridge2.ESD.3Com.COM> <25744@santra.UUCP> <974@bridge2.ESD.3Com.COM> <14138@well.UUCP> <979@bridge2.ESD.3Com.COM> <25791@santra.UUCP> <8769@hoptoad.uucp>
Reply-To: blm@6sigma.UUCP (Brian Matthews)
Followup-To: comp.sys.mac
Organization: Six Sigma CASE, Inc.
Lines: 20

In article <8769@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
|As someone who has written two terminal emulators for the Mac and is
|working in his spare time on a third, I agree with Juri Munkki.  Any
|terminal emulator which does not use the Communications Toolbox is
|obsolete.

As someone who has never written a terminal emulator and doesn't plan to,
but who uses terminal emulators a lot for a lot of different things, I
agree with Tim and Juri.  There are enough different hardware and
communications protocols that I use and am likely to need in the future
that I don't want to have to find a communications program that supports
everything I need, and then have to buy a completely new one when a new
requirement comes along.  I also don't want to have to pay for a lot
of silly protocols/emulators/etc. that I don't need.

White Knight sounds nice, but I suspect I won't have to wait too long
before a program with similar features comes along that does support
the Communications Toolbox, so I'll make do until then.
-- 
Brian L. Matthews	blm@6sigma.UUCP