The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marc Rochkind <mrochkind@gmail.com>
To: Bakul Shah <bakul@iitbombay.org>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Perkin-Elmer Sort/Merge II vs Unix sort(1)
Date: Fri, 17 Jan 2025 12:35:13 -0700	[thread overview]
Message-ID: <CAOkr1zXMAoBJL0qXAD42Qz5WECkbgW7UWUpF=wy9cGCWt38qEQ@mail.gmail.com> (raw)
In-Reply-To: <67F7FAEB-551F-47AA-9E09-2D8948E4CCCF@iitbombay.org>

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

Why did you say "thoughtless agglomeration of features?"

Do you know anything about the design of the P-E S/M, or is just a biased
guess? Have you ever tried a large external sort with UNIX commands?

Marc

On Fri, Jan 17, 2025, 12:10 PM Bakul Shah via TUHS <tuhs@tuhs.org> wrote:

> On Jan 17, 2025, at 9:23 AM, Diomidis Spinellis <dds@aueb.gr> wrote:
> >
> > I also think that the design of Perkin-Elmer's Sort/Merge II shows the
> influence of salespeople forcing developers to tack-on whatever features
> were required by important customers.  Maybe the clean design of Unix owes
> a lot to AT&T's operation under the 1956 consent decree that prevented it
> from entering the computer market.  This may have shielded the system's
> design from unhealthy market pressures during its critical gestation years.
>
> IIRC sort/merge was/is a pretty major thing on IBM mainframes, with
> products from multiple companies. May be Perkin-Elmer were trying
> to compete with mainframe sort/merge products? Also, I suspect that
> for sorting terabytes of data Unix sort likely won't work as fast as
> mainframe sorts....

[-- Attachment #2: Type: text/html, Size: 1551 bytes --]

  reply	other threads:[~2025-01-17 19:35 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 [this message]
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
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='CAOkr1zXMAoBJL0qXAD42Qz5WECkbgW7UWUpF=wy9cGCWt38qEQ@mail.gmail.com' \
    --to=mrochkind@gmail.com \
    --cc=bakul@iitbombay.org \
    --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).