From: Larry McVoy <lm@mcvoy.com>
To: Diomidis Spinellis <dds@aueb.gr>
Cc: Marc Rochkind <mrochkind@gmail.com>,
Bakul Shah <bakul@iitbombay.org>, TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Perkin-Elmer Sort/Merge II vs Unix sort(1)
Date: Sat, 18 Jan 2025 07:16:56 -0800 [thread overview]
Message-ID: <20250118151656.GQ1701@mcvoy.com> (raw)
In-Reply-To: <c210583f-4417-4b1e-a0ed-4c9ab1fcaac0@aueb.gr>
On Sat, Jan 18, 2025 at 04:51:15PM +0200, Diomidis Spinellis wrote:
> I'm sure the mainframe sort programs did some pretty amazing things and
> could run circles around the puny 830 line Unix Seventh Edition sort
> program. The 215 page IBM DOS VS sort documentation that John Levine posted
> here is particularly impressive. But I can't stop thinking that, in common
> with the mainframes these programs were running on, they represent a mindset
> that has been surpassed by superior ideas.
I disagree. Go back and read the reply where someone was talking about
sorting datasets that spanned multiple tapes, each of which was much
larger than local disk. sort(1) can't begin to think about handling
something like that.
I have a lot of respect for how Unix does things, if the problem fits
then the Unix answer is more simple, more flexible, it's better. If
the problem doesn't fit, the Unix answer is awful.
cmd < data | cmd2 | cmd3
is a LOT of data copying. A custom answer that did all of that in
one address space is a lot more efficient but also a lot more special
purpose. Unix wins on flexibility and simplicity, special purpose
wins on performance.
next prev parent reply other threads:[~2025-01-18 15:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 17:23 [TUHS] " Diomidis Spinellis
2025-01-17 19:10 ` [TUHS] " Bakul Shah via TUHS
2025-01-17 19:35 ` Marc Rochkind
2025-01-18 14:51 ` Diomidis Spinellis
2025-01-18 15:16 ` Larry McVoy [this message]
2025-01-18 15:40 ` Paul Winalski
2025-01-18 16:54 ` Marc Rochkind
2025-01-19 3:45 ` sjenkin
2025-01-18 16:00 ` Bakul Shah via TUHS
2025-01-18 16:25 ` Tom Lyon
2025-01-18 17:07 ` ron minnich
2025-01-18 19:39 ` Marc Rochkind
2025-01-17 20:07 ` John Levine
2025-01-18 4:46 ` Dave Horsfall
2025-01-17 18:12 Douglas McIlroy
2025-01-18 4:29 ` G. Branden Robinson
2025-01-21 21:53 Douglas McIlroy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250118151656.GQ1701@mcvoy.com \
--to=lm@mcvoy.com \
--cc=bakul@iitbombay.org \
--cc=dds@aueb.gr \
--cc=mrochkind@gmail.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).