The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Ben Greenfield <ben@cogs.com>
Cc: Tuhs <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] CMU Mach sources?
Date: Wed, 26 Jun 2019 13:21:25 -0700	[thread overview]
Message-ID: <20190626202125.GA1206@mcvoy.com> (raw)
In-Reply-To: <04827B96-5B5E-473E-A95F-67C4292B69D1@cogs.com>

On Wed, Jun 26, 2019 at 03:32:32PM -0400, Ben Greenfield via TUHS wrote:
> I would be more impressed if those criticizing weren???t so hand-wavy and had more specific points???.

OK, I'll bite.  Go read the source in the FreeBSD tree, which has been 
reduced in size by 60% according to someone on the team.  Then come
back and draw me a picture of what it does.

I get that what I'm asking is non-trivial, I've tried to do it and failed.
As a pretty green guy it took me months to do that for SunOS but I could
feel myself getting closer.  I never got that feeling in the Mach code,
I kept getting lost in code that made me say "why is this here?"

What I've been trying to say all along is getting something to work is
different from making something that both works and is clean.  When
something is clean it is like a well written paper, it is actively
trying to help you understand the information.  I value clean code,
and I'm not a fan of people excusing messy code because researchers
did it.  As someone said to me in private, those same researchers 
are expected to write clear and understandable papers, why is code
any different?

I also agree with whoever said the Mach guys were trying out all sorts
of different ideas, that's cool.  What's not cool is that when those
ideas didn't pan out they left in all the substrate that had proven to
be not needed.

And I'll freely admit Mach left a sour taste in my mouth.  I read all
the papers and those lead me to believe that the code would be on par
with the SunOS code.  When I finally got to read it I felt like a kid
who was promised nice things only to have them taken away.  

  reply	other threads:[~2019-06-26 20:21 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23  4:38 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
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 [this message]
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
2019-06-23 22:08 Noel Chiappa
2019-06-23 23:54 ` Theodore Ts'o
2019-06-24 17:04   ` Jason Stevens
2019-07-01 13:20 Jason Stevens

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=20190626202125.GA1206@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=ben@cogs.com \
    --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).