Computer Old Farts Forum
 help / color / mirror / Atom feed
From: lm at mcvoy.com (Larry McVoy)
Subject: [COFF] [SPAM] Re: Architectures -- was [TUHS] 68k prototypes & microcode
Date: Fri, 5 Feb 2021 06:56:18 -0800	[thread overview]
Message-ID: <20210205145618.GE13916@mcvoy.com> (raw)
In-Reply-To: <CAC20D2ONCSvaHJTbiisp7EqnszbGDxVu0GgqeQq1CJf2KmN5AA@mail.gmail.com>

On Fri, Feb 05, 2021 at 09:36:20AM -0500, Clem Cole wrote:
> FWIW:  Intel >>does<< know how to make a $20 SOC, but the margins will
> suck.  The question is what will management want to?   I really don't
> know.  So far, we have liked the server chip margins (don't forget Intel
> made more $s last year than it ever has - even in the pandemic).

I think Intel is sort of in the same place Sun was.  Fat, dumb, and
happy with the profits they are making and can't see what is coming.

It just didn't make sense to have $20,000 Sun workstations when a $2,000
PC was at least half as good.  I advocated for SunOS on x86, to me,
it was the operating system that delivered the value, everything just
worked on SunOS, for any other OS you were doing the configure dance.
Offer SunOS on x86 and capture the low end market.  The East coast Sun
did the road runner but West coast Sun sneered at it, patches for x86
were not processed very fast, if at all.  It's a shame.

If Intel doesn't want to make money off of the cheap, but very high
volume, $20 SOC, Apple has shown that it has the chops to make a cheap,
fast, and power sipping M1 chip.  Pretty impressive and if I were Intel,
I'd be nervous.  Apple has shown they can switch architectures pretty
painlessly repeatedly.  The x86 lock in isn't much of a lock in these
days.


  reply	other threads:[~2021-02-05 14:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1l5RL3-0002iv-Qv@tanda>
     [not found] ` <abf50209-5730-f5a0-0fd6-aec13ee68440@e-bbes.com>
     [not found]   ` <202102030759.1137x7C2013543@freefriends.org>
     [not found]     ` <CAHTagfHdykiYmqPCkhQkUQTU8fLqJBukPOyj-k1ef=Ur9rqH+Q@mail.gmail.com>
     [not found]       ` <202102030858.1138wuqd011051@freefriends.org>
     [not found]         ` <CAHTagfGOC7vgE2Os+kuP4oGzvot2kG3MERpQdLb2EoEhUoFpyg@mail.gmail.com>
     [not found]           ` <CAC20D2M_33YdQyuHdb7EM-UVNcdM0TXz9eJXpTftHekWxK0=Dg@mail.gmail.com>
2021-02-05  8:53             ` [COFF] [TUHS] AT&T 3B1 - Emulation available peter
2021-02-05 17:41               ` [COFF] " cym224
     [not found]             ` <27567.1612399305@hop.toad.com>
     [not found]               ` <bce2c77e-dd8d-a0f2-5b27-0f9239c76738@kilonet.net>
     [not found]                 ` <alpine.BSF.2.21.9999.2102041316080.70858@aneurin.horsfall.org>
     [not found]                   ` <4db6108e-73f0-6498-fe45-3fd422d1f389@kilonet.net>
     [not found]                     ` <alpine.BSF.2.21.9999.2102051312440.70858@aneurin.horsfall.org>
2021-02-05  2:53                       ` [COFF] [TUHS] 68k prototypes & microcode lm
     [not found]                 ` <20210204013356.GA16541@mcvoy.com>
2021-02-05  9:09                   ` peter
2021-02-05 14:36                   ` [COFF] Architectures -- was " clemc
2021-02-05 14:56                     ` lm [this message]
2021-02-05 18:31                       ` [COFF] [SPAM] " david
2021-02-05 22:02                       ` dave
2021-02-05 19:16                     ` [COFF] " athornton

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=20210205145618.GE13916@mcvoy.com \
    --to=coff@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).