The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "A. P. Garcia" <a.phillip.garcia@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] SPARC is CRAPS spelled backwards.
Date: Sun, 23 Sep 2018 15:49:28 -0400	[thread overview]
Message-ID: <CAFCBnZufqk1SmOVdWLK19a0oQ1FjFe7ebDDa+T54yrNo=19eDw@mail.gmail.com> (raw)
In-Reply-To: <1686170E-4323-4BDF-B95C-8A6B3FFD5288@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

On Sun, Sep 23, 2018, 2:37 PM Don Hopkins <don@donhopkins.com> wrote:

> Its register windows have spilled out into the SCRAP heap of history.
> But to its credit, the SPARCSTATION represents PANTISOCRACY with NO RACIST
> PAST.
> It ROASTS CATNIP for SATANIC SPORT with no PARTISAN COST.
> It can create a CAT SOPRANIST with a CASTRATO SNIP.
>
In trying to steer this word salad towards some semblance of meaningful
discussion, is SPARC dead? Practically, yes, I would say so. Or at least it
seems to be heading in that direction. Is RISC dead? Not at all. ARM is
doing quite well, and the old "CISC vs RISC" thing seems to be a non-issue
now, as even the current x86 processors have adopted many design features
that originated in RISC research.

The saddest thing about the death of SPARC, in my opinion, is that it
likely also means the death of the most advanced OS with "true" UNIX roots.
CDDL was ostensibly chosen to prevent Linux from cannibalizing the best
parts of Solaris. But it only seems to have slowed that down.

[-- Attachment #2: Type: text/html, Size: 2002 bytes --]

  reply	other threads:[~2018-09-23 19:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.98.1535822297.3725.tuhs@minnie.tuhs.org>
2018-09-23 18:37 ` Don Hopkins
2018-09-23 19:49   ` A. P. Garcia [this message]
2018-09-23 21:17     ` Paul Winalski
2018-09-24 11:25       ` Tony Finch
2018-09-24 19:46       ` Peter Jeremy
2018-09-24 20:20         ` Paul Winalski
2018-09-24 20:45           ` Arthur Krewat
2018-09-26  6:20             ` Peter Jeremy
2018-09-26  6:46               ` Lars Brinkhoff
2018-09-26 15:03                 ` Theodore Y. Ts'o
2018-09-26 15:32                   ` Paul Winalski
2018-09-26 15:44               ` Henry Bent
     [not found]                 ` <ceae72ff-ca8b-4cc1-9666-82253c1e1683.maildroid@localhost>
2018-09-26 16:02                   ` [TUHS] Fwd: " William Pechter
2018-09-26 18:24                 ` [TUHS] " Donald ODona
2018-09-25 10:00         ` Tony Finch
2018-09-25 15:01           ` Larry McVoy
2018-09-25 19:48             ` Peter Jeremy
2018-09-25 18:34           ` Paul Winalski
2018-09-24 11:48 Noel Chiappa
2018-09-25 12:12 Noel Chiappa
2018-09-25 14:49 ` Theodore Y. Ts'o
2018-09-26 19:31   ` Derek Fawcus
2018-09-25 15:29 ` Arthur Krewat
2018-09-25 18:41 Noel Chiappa
2018-09-27  7:35 Paul Ruizendaal
2018-09-27  7:52 ` Arrigo Triulzi
2018-09-27 18:03 Nelson H. F. Beebe
2018-09-27 19:34 ` Nemo
2018-09-27 20:30 ` Dan Cross
2018-09-27 20:51   ` Cág
2018-09-27 21:01     ` Henry Bent
2018-09-27 21:04       ` Cág
2018-09-27 21:07 Norman Wilson
2018-09-28 12:08 Nelson H. F. Beebe

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='CAFCBnZufqk1SmOVdWLK19a0oQ1FjFe7ebDDa+T54yrNo=19eDw@mail.gmail.com' \
    --to=a.phillip.garcia@gmail.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).