Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!hc!lanl!cmcl2!yale!spolsky-joel From: spolsky-joel@CS.YALE.EDU (Joel Spolsky) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: ARC/ZOO/ZIP for comp.binaries.ibm.pc Message-ID: <51968@yale-celray.yale.UUCP> Date: 27 Feb 89 02:48:20 GMT References: <1325@csm9a.UUCP> Sender: root@yale.UUCP Reply-To: spolsky-joel@CS.YALE.EDU (Joel Spolsky) Organization: Yale University Computer Science Dept, New Haven CT 06520-2158 Lines: 44 In article <1325@csm9a.UUCP> japplega@csm9a.UUCP (Joe Applegate) writes: > >The decision of whether to embrace one format or another based on availability >of processing tools on UNIX is rediculous! (1) The vast majority of c.b.i.p readers are on Unix systems (2) Very often they would like to read the documentation before wasting hours downloading a program which they aren't sure they need. (3) Even more often they have fancy high speed printers on their unix systems, to print said documentation. (4) Thus the availability of an unarc'er on Unix is a critical criterion for choosing a c.b.i.p format. >DOS programs should be processed >with DOS tools... This is meaningless drivel. >the idea of unarcing a program on Unix and then transmitting >multiple files at 30-50% the size when the .ARC file is available is >not pratical... we have excellant tools for DOS... not only is ARC available >for DOS but ZOO as well... and SIMTEL20 and many BBS' even carry Unix-style >tools such as uudecode/uuencode, tar, ar, and even compress... What is the point. > >Let's let posters use what ever format they want and let the reciever use >the available DOS tools to process it. In other words, anarchy? I vote for ZOO, because I would like ONE standard I can use for Unix and DOS, and for moving files between them. > - Joe Applegate - > +----------------+----------------------------------------------------------+ | Joel Spolsky | bitnet: spolsky@yalecs.bitnet uucp: ...!yale!spolsky | | | internet: spolsky@cs.yale.edu voicenet: 203-436-1483 | +----------------+----------------------------------------------------------+ #include