Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!caen!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!psuvm!dxb132
From: DXB132@psuvm.psu.edu
Newsgroups: comp.sys.amiga.tech
Subject: Re: What's Wrong with ARP!!!!
Message-ID: <90318.162021DXB132@psuvm.psu.edu>
Date: 14 Nov 90 21:20:21 GMT
References: <114.273F7E66@myamiga.UUCP> <1990Nov14.034507.19784@hoss.unl.edu>
 <7039@sugar.hackercorp.com>
Organization: Penn State University
Lines: 26

In article <7039@sugar.hackercorp.com>, peter@sugar.hackercorp.com (Peter da
Silva) says:

>In article <1990Nov14.034507.19784@hoss.unl.edu> 252u3130@fergvax.unl.edu
>(Phil
>Dietz) writes:
>> Hmmmph....with the discussion of wild cards, people have been coming
>> out of the cracks and harassing ARP.  Boy if my memory works right (256
>> bit of course), when ARP came out, it was the hottest thing to use.

>Not me, dude. I've been harassing ARP since the beginning.

>(a) It's all in assembler. That's a big no-no for me.
>(b) They never got it all together. It was missing major programs (like copy)
>    and the programs that did come out tended to have weird bugs (um, non
>    standard features if you like).

>I'm sure (b) was due to (a).

Oh, give me a break!!! ARP was a not-for-profit (ad)venture by a group of
very talented and enthusiastic programmers, and they did a damn fine job, a
lot better than those cheesy BCPL crap-garbage-explitive commands!!!

Feel free to flame me, but stop flaming ARP!

-- Dan Babcock