Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!atanasoff!hascall
From: hascall@atanasoff.cs.iastate.edu (John Hascall)
Newsgroups: comp.lang.c
Subject: Re: Portability and the Ivory Tower (was Re: Book on Microsoft C)
Message-ID: <948@atanasoff.cs.iastate.edu>
Date: 3 Apr 89 14:33:32 GMT
References: <754@oravax.UUCP> <225800146@uxe.cso.uiuc.edu> <9937@smoke.BRL.MIL> <425bf40d.b11a@falcon.engin.umich.edu> <3653@ficc.uu.net> <42674c5e.b11a@falcon.engin.umich.edu>
Reply-To: hascall@atanasoff.cs.iastate.edu (John Hascall)
Organization: Iowa State Univ. Computation Center
Lines: 19

In article <42674c5e.b11a@falcon.engin.umich.edu> ejd@caen.engin.umich.edu (Edward J Driscoll) writes:
>In article <3653@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
  
>>Machine independent code does not imply teletype compatibility. There have

>You're right, 'vi' is an excellent example.  I tried to teach a
>Mac programmer (with an MS from MIT) how to use it, and he
>thought it laughably brutal compared to even the most simple
>Mac editor.  Do you really prefer h,j,k, and l to using a mouse?

    Yes.  I'm certainly not the worlds largest fan of vi, but using a mouse
    to do simple cursor positioning is ludicrous.  Why take your hands off
    the keyboard just to move over a couple of spaces?

    By the way, I'm not being anti-mouse here (I have one on my workstation
    and it is great for things like cut&paste), but I think it's silly to
    try to do everything with it.

John Hascall / ISU Comp Center