The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (scj@yaccman.com)
Subject: [TUHS] Unix Circuit Design System [and FOSS]
Date: Sun, 3 Jan 2016 17:05:45 -0800	[thread overview]
Message-ID: <e7b50bf660a1d2d783608a016b106fb5.squirrel@webmail.yaccman.com> (raw)
In-Reply-To: <CAC20D2N41nLk0xH1TxFUKNqPnk4NhdACpbd9vm+1f4tC_x8irA@mail.gmail.com>

> You are absolutely correct, they sharing culture was around throughout the
> 50s and 60s.  In fact the IBM "DECUS" equivalent was (is) called Share.
> When I say, dop really was creating the idea of  FOSS, it was different
> from the sharing that had occurred previously.
>

I had an interesting experience with "open source" in the 1960's.  My
first published paper, called "Hierarchical Clustering Schemes", described
a way of taking non-dimensional data (e.g., "A is more like B than it is
like C") and finding clusters of objects that behave similarly.  I had
written a modest-sized FORTRAN program to carry out the algorithm--it was,
as I recall, between 100 and 200 lines long.  As a postscript to the
paper, readers were invited to write to Bell Labs and a card deck of the
program would we sent at no cost.  We expected a couple of dozen requests,
but in fact sent out, as I recall, nearly 500 card decks.  A couple of
years later I started getting reprints of articles that referenced my
paper, the authors' having analyzed their data with the program.  Many of
the papers were unusual, to say the least (in one, the program was used to
do organize the Latin curriculum in Poland, for example...).  The paper
had over 700 citation, and, the last time I looked, was still my most
cited publication.

Ah, the good old days, when people who used free software actually
acknowledged the original author(s)...



      reply	other threads:[~2016-01-04  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-02 18:35 Nelson H. F. Beebe
2016-01-02 21:30 ` Clem Cole
2016-01-04  1:05   ` scj [this message]

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=e7b50bf660a1d2d783608a016b106fb5.squirrel@webmail.yaccman.com \
    --to=scj@yaccman.com \
    /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).