The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tuhs@eric.allman.name
To: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Craft vs Research (Re: CMU Mach sources?
Date: Wed, 26 Jun 2019 17:16:07 -0700	[thread overview]
Message-ID: <5db5af7f-d11b-2d87-edd9-fa5aae855fb5@neophilic.com> (raw)
In-Reply-To: <20190626231926.EF38A156E40C@mail.bitblocks.com>

I think Larry is right, but also wrong.  I think I can speak from
experience.

The goal of research is not to produce consumer-ready code, but to
explore ideas.  Nasty things sometimes happen in that environment.

But that doesn't mean that code doesn't have to work.  My introduction
to coding on a research project was INGRES, at the time the competitor
to System R (now DB/2, better known as "anything SQL") from IBM
Research.  By the very nature of the problem, the main complaint was
that "Relational Databases Cannot Work" --- so proving that they could
was a major part of the research agenda.

At one point (pre-commercial) INGRES stored the telecom wiring diagram
of New York City.  It wasn't always a pleasant experience, but we
learned a lot, mostly happy, most of the time.  A lot of our motivation
was because real people were using our code to do real work.  Had we
hung them out in the wind to dry, we wouldn't have gotten that feedback,
and frankly I think RDBMS wouldn't have progressed so far and so fast.

But when I left INGRES I talked with Mike Stonebraker, who asked me
where I thought the project should be going.  At that point I thought it
was clear that the research objectives had been satisfied, and there was
the beginnings of a commercial company to move it forward, so I advised
that the old code base (which at that point I had written or
substantially modified well over 50%) should be abandoned.  Do a new
system from scratch, in any language, (and I quote) "even in LISP if
that's the right decision."  Unfortunately the first version of Postgres
was written in LISP --- my breed of humor was apparently unappreciated
at that time.  But from a research perspective the goal was no longer to
produce something that actually worked in the real world, but to explore
new ideas, including bad ones.  I wasn't involved with Postgres
personally, but I think Larry's analysis was essentially correct as I
know it.

I was extraordinarily lucky to have ended up at Berkeley in the mid-70s
when UNIX was just becoming a "thing", and I can assure you that while
there were a lot of people who just wanted to get their degrees, there
was also a large cadre wanting to produce good stuff that could make
peoples' lives better.

eric

  reply	other threads:[~2019-06-27  1:12 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23  4:38 [TUHS] " Chris Hanson
2019-06-23  5:15 ` Larry McVoy
2019-06-23  8:52   ` Andrew Warkentin
2019-06-23 13:39   ` Jon Forrest
2019-06-23 13:59     ` arnold
2019-06-23 14:03     ` Jason Stevens
2019-06-23  8:04 ` Jason Stevens
2019-06-23 14:54   ` Henry Bent
2019-06-23 21:52     ` Clem Cole
2019-06-25  0:06       ` Larry McVoy
2019-06-25  0:31         ` Theodore Ts'o
2019-06-25  0:45           ` Larry McVoy
2019-06-25  0:55             ` Kurt H Maier
2019-06-25  4:18               ` Larry McVoy
2019-06-26 23:19                 ` [TUHS] Craft vs Research (Re: " Bakul Shah
2019-06-27  0:16                   ` tuhs [this message]
2019-06-27 17:06                     ` Clem Cole
2019-06-25  1:00             ` [TUHS] " Richard Salz
2019-06-25  8:00               ` Kevin Bowling
2019-06-25 12:11                 ` Arthur Krewat
2019-06-25 12:17                   ` Arthur Krewat
2019-06-26  2:45               ` Kurt H Maier
2019-06-26  2:56                 ` Larry McVoy
2019-06-26 15:11                   ` Theodore Ts'o
2019-06-26 17:44                     ` Larry McVoy
2019-06-26 18:01                       ` arnold
2019-06-26 18:18                         ` Warner Losh
2019-06-26 19:22                       ` Chris Hanson
2019-06-26 19:32                         ` Ben Greenfield via TUHS
2019-06-26 20:21                           ` Larry McVoy
2019-06-27  0:22                             ` Chris Hanson
2019-06-27  1:02                               ` Larry McVoy
2019-06-27  1:26                                 ` Chris Hanson
2019-06-27  4:01                             ` Lyndon Nerenberg
2019-06-27 10:34                               ` Ben Greenfield via TUHS
2019-06-27 10:59                                 ` arnold
2019-06-27 11:13                                   ` Ben Greenfield via TUHS
2019-06-27 11:39                                     ` arnold
2019-06-27 14:58                                     ` Warner Losh
2019-06-27 17:25                                       ` Larry McVoy
2019-06-26 19:30                       ` Dennis Boone
2019-06-26 19:25                     ` Adam Thornton
2019-06-23  8:27 ` Kevin Bowling
2019-06-25  3:07 ` Gregg Levine
2019-06-25  8:15   ` Kevin Bowling
2019-06-25 18:18   ` Chris Hanson
2019-06-25 20:23     ` Gregg Levine
2019-06-26  1:04       ` Jason Stevens
2019-06-26  0:53     ` Jason Stevens
2019-06-25  7:49 ` Jason Stevens
2019-06-25  7:59   ` Andreas Grapentin

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=5db5af7f-d11b-2d87-edd9-fa5aae855fb5@neophilic.com \
    --to=tuhs@eric.allman.name \
    --cc=tuhs@minnie.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).