4 ms·
That's highly unlikely. Archive Utility is just slow.
by pvg 10y ago
That's highly unlikely. Archive Utility is just slow.
- eric_h 10y agoI think you're probably right. I'd imagine that most of the code in Archive Utility.app is very old, and there's very little business reason to spend any engineering time on improving it beyond doing just enough work to make sure it works with API changes for later OS releases. There are third party GUI compression utilities that are faster that you'd find if you actually care about how long it takes to decompress your archives, and the CLI utilities are all there out of the box for people who don't need a GUI.
- ben0x539 10y agoIf it's really old, shouldn't it be faster as it would've been designed to perform adequately on way slower CPUs? ;)
- mwfunk 10y agoWhat is highly unlikely about that? That seems more plausible than, zlib is magically 1000x slower when used by Archive Utility.
- flashman 10y agoWhat seems more likely to me is that the "decompressing a large number of small archives" task is so rare that Apple hasn't optimised it. More likely than "Apple added an arbitrary delay to make the interface more satisfying."
- pvg 10y agoIt's unlikely it's on purpose. It makes sense in something like tax software you use once a year. It makes no sense at all when doing a bunch of i/o bound operations which are already potentially slow.
- coldtea 10y agoIt's highly unlikely that it's 1000 times slower than the command line utility to decompress, with which they share the same libs anyway...
- pvg 10y agoIt isn't because they don't do anywhere close to the same thing. Watch the video: http://robservatory.com/postimages/unzipping/finder_v_terminal_high.mp4 http://robservatory.com/postimages/unzipping/finder_v_termin... Where do you think the people who wrote the thing that happens on the left inserted a gratuitous sleep?
- espadrine 10y agoFor each file, a split second to animate the apparition of the window (or the increase of the existing window), another split second to show the empty progress bar, a millisecond to fork the decompression process, a couple of frames at 60 Hz to animate it being filled, and another split second to animate the disappearance of the window (or the decrease of the existing window).
- pvg 10y agoNone of these are deliberate idling to give the impression of work which is what the original comment was about.