The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com (Aharon Robbins)
Subject: [TUHS] curmudgeon credit
Date: Sun, 28 Apr 2013 08:34:53 +0300	[thread overview]
Message-ID: <201304280534.r3S5YrSu002857@skeeve.com> (raw)
In-Reply-To: <20130427224146.GR664@bitmover.com>

> What I'd like is a new 64 bit PDP-11.  That assembler was wonderful to
> read and write, only a short distance from C.

True.

> x86 makes me puke.  MIPS and Alpha aren't much better

Dunno if this is the right forum, but I have to wonder about the fact
that many old-time Unix and Plan 9 folks rant and rave about different
architectures.  (I mean, I know people who are *still* pining for the
DEC-10 with TOPS-10 and TOPS-20.)

IF you are not writing the compiler or the low level OS routines, what
freaking difference does it make?  I've been doing C, Unix, C++, Linux,
etc., for over 30 years, and what matters to me more are things like
what facilities are in my C library, how standards compliant a system is,
whether the library and OS behave like they should (cf MirBSD, which is
brain dead on at least 2 counts), and so on.

The only assembly language I ever learned was the PDP-11, and that was
on a Univac system using an assembler and simulator written in Algol-W
circa 1979.   And I agree, the architecture was beautiful.

But even though my home systems and much of my work has been on x86 Linux
for close to 20 years, I don't find myself constantly moaning and groaning
that the underlying instruction set isn't clean and elegant.

So other than the curmudgeon credit, what am I missing?

Arnold



  parent reply	other threads:[~2013-04-28  5:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27 21:26 [TUHS] Need a new PDP-11 or VAX? Dave Horsfall
2013-04-27 22:41 ` Larry McVoy
2013-04-27 23:53   ` Dave Horsfall
2013-04-28  0:12   ` Ronald Natalie
2013-04-28  1:39   ` John Cowan
2013-04-28  3:38     ` Nick Downing
2013-04-28  3:48       ` Larry McVoy
2013-04-28  3:57     ` Larry McVoy
2013-04-28  5:57       ` John Cowan
2013-04-28  5:34   ` Aharon Robbins [this message]
2013-04-28  7:08     ` [TUHS] curmudgeon credit Nick Downing
2013-05-14  6:11       ` Aaron J. Grier
2013-05-14  6:52         ` emu
2013-05-14  7:51           ` David Evans
2013-04-28 16:28     ` Larry McVoy
2013-04-28  7:45   ` [TUHS] Need a new PDP-11 or VAX? Peter Jeremy
2013-04-28 10:50     ` Ronald Natalie
2013-04-28  0:15 ` Ronald Natalie

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=201304280534.r3S5YrSu002857@skeeve.com \
    --to=arnold@skeeve.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).