Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!garnet.berkeley.edu!ked
From: ked@garnet.berkeley.edu (Earl H. Kinmonth)
Newsgroups: comp.misc
Subject: Re: UNIX needs a real text editor
Message-ID: <21437@agate.BERKELEY.EDU>
Date: 10 Mar 89 16:53:25 GMT
References: <222@imspw6.UUCP> <9653@bloom-beacon.MIT.EDU> <5552@brspyr1.BRS.Com>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 18

In article <5552@brspyr1.BRS.Com> miket@brspyr1.BRS.Com (Mike Trout) writes:
>In article <9653@bloom-beacon.MIT.EDU>, jik@athena.mit.edu (Jonathan I. Kamens) writes:
>
>your business.  But you should be aware that while you are putt-putting along
>in your Sopwith Pup, most of the rest of us have climbed into P-38 Lightnings.

How about something other than cute rhetoric?  How do you measure performance
and utility differences in editors?  How did you make such measurements?
Did you make such measurements?

There is also more to editors than perceived speed.  Here is a test for
your favorite editor.  Let me know if it passes.  vi does, at least on
Sony work stations.  The test:  can your editor process text and programs
destined for all of the world's largest computer and software markets.

(In case you've been too busy tooling around in your P38 to notice, Japan
is the second largest market, and in 1992 it will be the EEC.  That means
your editor must handle all European languages plus Japanese.)