Path: utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!ukma!xanth!mcnc!thorin!zeta!leech
From: leech@zeta.cs.unc.edu (Jonathan Leech)
Newsgroups: comp.windows.x
Subject: Re: ASCII terminals vs. X Window System terminals
Message-ID: <6235@thorin.cs.unc.edu>
Date: 18 Jan 89 19:56:45 GMT
References: <8901172105.AA06900@hydra> <8901181314.AA12697@LYRE.MIT.EDU>
Sender: news@thorin.cs.unc.edu
Reply-To: leech@zeta.UUCP (Jonathan Leech)
Followup-To: comp.terminals.misc
Organization: University Of North Carolina, Chapel Hill
Lines: 16
Summary:
Expires:
Sender:
Distribution:
Keywords:

In article <8901181314.AA12697@LYRE.MIT.EDU> swick@ATHENA.MIT.EDU (Ralph R. Swick) writes:
>of (any) window system.  It would be appropriate to think of an ASCII
>terminal as a governor (constrictor) on each user.  The two environments
>and the kinds of things users try to do with each are so vastly
>different that capacity planning based upon system overhead metrics
>is not likely to get very far.

    I find the 'window' tty-based window manager on BSD does 90% of
what I want a window system for. The only major thing missing is large
editing windows, and Ann Arbor can fix that problem.
    Followups to comp.terminals.misc.
--
    Jon Leech (leech@cs.unc.edu)    __@/
    ``After all, the best part of a holiday is perhaps not so much to be
      resting yourself as to see all the other fellows busy working.''
	- Kenneth Grahame, _The Wind in the Willows_