[Info-vax] Intel proposal to simplify x86-64

[Dan Cross]

In article <mddilburbyz.fsf at panix5.panix.com>,
Rich Alderson  <news at alderson.users.panix.com> wrote:
>cross at spitfire.i.gajendra.net (Dan Cross) writes:
>
>> In article <mddo7lo2nd4.fsf at panix5.panix.com>,
>> Rich Alderson  <news at alderson.users.panix.com> wrote:
>
>>> I only know enough vi to edit the password file (using the vipw command), or in
>>> the old days before autoconfiguration I could edit the Emacs configuration files
>>> to install a decent editor.
>
>> Over the years,I've found it useful to retain facility with
>> several different editors, selecting between them based on
>> context.  If I'm working on plan9, I'll use acme or sam; if
>> I'm on Unix, vi, though knowing how to use `ed` has been very
>> useful in many surprising ways; if I'm programming in Lisp, or
>> using Multics or TOPS-20, then emacs; on VMS I use EDT; etc.
>> For work-a-day programming these days I like VS Code with the
>> language server support.
>
>Fortunately for me, all the systems on which I worked prior to building PGA's
>museum had versions of Emacs available.  (Well, OK, not the IBM mainframes, but
>I could transfer files from a DEC-20 so did my editing there...)
>
>On VMS at the museum, I used TECO because it didn't require a lot of study, as
>I was using it on PDP-8 and PDP-11 and DEC-10 systems already.
>
>Different strokes for different folks, no?

Absolutely!  I've never understood editor holy wars.  People
should use the tools they're most comfortable with; why does
anyone feel the need to foist their favorite tool onto someone
else?

	- Dan C.