Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pacbell!att!occrsh!uokmax!metnet!p8.f30.n147.z1.FIDONET.ORG!Chris.Maidt
From: Chris.Maidt@p8.f30.n147.z1.FIDONET.ORG (Chris Maidt)
Newsgroups: comp.binaries.ibm.pc.d
Subject: How about un-compression?
Message-ID: <11.2434B9CB@metnet.FIDONET.ORG>
Date: 1 Apr 89 00:45:35 GMT
Sender: ufgate@metnet.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 1:147/30.8
Lines: 24


 BW> Hi,
 BW> There have been a lot of people comparing the various compression
 BW> programs, quoting the speed of *compression*.  But what about the
 BW> speed of un-compression?  It seems to me that this is a more 
 BW> common operation for most people.  I know that probably 90% of my
 BW> time spent with archives is looking at them to see if they are 
 BW> useful, or not.  I don't really care if the archive took the author
 BW> 2 minutes or 20 minutes to create.

Besides this being a test to see if this inter-domain stuff really works, I  
want to comment that for ME, speed and size are the most important parts of  
compression.  I write my own stuff, and have to constantly update it and send  
it off again ... I want it arced NOW and I want to be able to send it in  
nothing flat.  De-compression, on the otherhand ... I like care how long it  
takes to uncrunch ... although SEA's 6.01 takes the cake here unarcing whole  
tree structures in 10-15 minutes. 



--  
Chris Maidt - via FidoNet node 1:147/10
UUCP: ...!uokmax!metnet!30.8!Chris.Maidt
INTERNET: Chris.Maidt@p8.f30.n147.z1.FIDONET.ORG