From: nobozo@gmail.com (Jon Forrest)
Subject: [TUHS] shared objects in Unix
Date: Fri, 30 Mar 2018 13:52:44 -0700 [thread overview]
Message-ID: <be27e8d3-8549-a056-9a1f-0fb31fca4eab@gmail.com> (raw)
In-Reply-To: <048A69EA-7B2C-4D2C-A69B-76CE8E082826@ccc.com>
[Larry McVoy said ...]
>> CMU's Mach, mem, I am by no means a fan (I bought into the hype, read
>> all the papers, when I finally got to see the code, wow. NOTHING like Sun's
>> VM system, I mean, nothing. It claimed to be the same sort of thing, it was
>> an ugly mess and it still is.
This is typical of university research projects. To those of us who
worked in the Postgres research group at UC Berkeley, one of the great
mysteries of the world is how the PostgreSQL community was able to take
the research Postgres code and make it into the production quality
database it is now.
Most research projects suffer because the goal of the people who
work on it is to hack on it to get their research done, so that
they can get their MS/PhD and then get the hell out. Code quality
is rarely a major concern. Postgres (and Ingres) benefited from
having a Chief Programmer who attempted to minimize this problem.
Jon Forrest
next prev parent reply other threads:[~2018-03-30 20:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 21:37 Paul Winalski
2018-03-29 22:01 ` Henry Bent
2018-03-29 22:26 ` Warner Losh
2018-03-29 23:11 ` Dave Horsfall
2018-03-29 23:22 ` Warner Losh
2018-03-29 23:24 ` Larry McVoy
2018-03-30 0:22 ` Clem Cole
2018-03-30 1:46 ` Larry McVoy
2018-03-30 4:28 ` Clem cole
2018-03-30 20:52 ` Jon Forrest [this message]
2018-03-30 22:42 ` Clem Cole
2018-03-30 23:29 ` Paul Winalski
2018-04-03 15:49 ` Derek Fawcus
2018-03-30 1:20 ` Lyndon Nerenberg
2018-03-30 0:40 ` Clem Cole
2018-03-30 1:35 ` Charles H. Sauer
2018-03-30 2:10 ` Larry McVoy
2018-03-30 2:34 ` Charles H. Sauer
2018-03-30 3:04 ` Warner Losh
2018-03-30 20:33 ` Charles H Sauer
2018-03-30 3:00 ` Ron Natalie
2018-03-30 21:53 ` Steve Johnson
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=be27e8d3-8549-a056-9a1f-0fb31fca4eab@gmail.com \
--to=nobozo@gmail.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).