From: Tom Lyon <pugs78@gmail.com>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Perkin-Elmer Sort/Merge II vs Unix sort(1)
Date: Sat, 18 Jan 2025 08:25:08 -0800 [thread overview]
Message-ID: <CANxB0bTWZzN4XJ9mtJ=6+=OzNNRuQ0229WkH0o=V0bs3ifkQig@mail.gmail.com> (raw)
In-Reply-To: <2FC28EC8-6146-4D0F-BAB3-86F2A86332BB@iitbombay.org>
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
Related to the sort discussion, there's an oral history of Duane Whitlow,
founder of SyncSort, which was a big deal in IBM shops in the 70s. (and
perhaps later; I lost track)
https://archive.computerhistory.org/resources/access/text/2013/05/102702251-05-01-acc.pdf
On Sat, Jan 18, 2025 at 8:00 AM Bakul Shah via TUHS <tuhs@tuhs.org> wrote:
> On Jan 18, 2025, at 7:16 AM, Larry McVoy <lm@mcvoy.com> wrote:
> >
> > 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.
>
> Mainframes had usage based pricing, not unlike what you pay for renting
> resources in the cloud, so performance really mattered. Also note that
> users use whatever computing resources they have available to get their
> job done, ideally at the lowest cost. Elegance of any OS architecture
> is secondary, if that.
>
>
[-- Attachment #2: Type: text/html, Size: 2680 bytes --]
next prev parent reply other threads:[~2025-01-18 16:25 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
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 [this message]
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='CANxB0bTWZzN4XJ9mtJ=6+=OzNNRuQ0229WkH0o=V0bs3ifkQig@mail.gmail.com' \
--to=pugs78@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).