From: steve jenkin <sjenkin@canb.auug.org.au>
To: TUHS <tuhs@tuhs.org>
Cc: Bakul Shah <bakul@iitbombay.org>
Subject: [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler)
Date: Sun, 5 Feb 2023 21:42:31 +1100 [thread overview]
Message-ID: <B7AA4E29-17E8-40D2-94A3-D9EFE51BECF2@canb.auug.org.au> (raw)
In-Reply-To: <B5EE26EC-68AB-479F-A69F-A1429FE443CB@iitbombay.org>
> On 4 Feb 2023, at 04:45, Bakul Shah <bakul@iitbombay.org> wrote:
>
> We still seem to be in the “Cambrian explosion” phase
> where every new complex system is a new species.
You just perfectly described the computing world before 1965 & IBM’s 360.
A range with 10x - 20x (? recall failure) of compatible models.
This was repeated with microprocessors
- at each ‘process step’, one clock frequency option for many years.
Can’t recall who invented the range of CPU options we now have:
server, desktop, laptop, tablet and ‘embedded’
Might’ve been two variants of 486, can’t recall.
There was a tower of babel with Networking for decades,
first the physical layer,
then the packet layer,
then network / protocol layer.
We ended up with cat-5/6 twisted pair as the most common
physical layer (with RJ-45’),
async packets framed with Ethernet,
running IP protocols over the network layer.
“Internetwork” is a give away in the name “I.P.”.
This, despite IBM & Microsoft’s (& others) considerable efforts otherwise.
Mature markets require “Standard” parts / services,
so consumers can mix-n-match as they wish.
Standards facilitate “substitutes” & competition necessary
to generate low-margin, high-volume commodity markets.
By definition, commodity markets trade “fungible goods”
destined for consumers. So many of these, hard to list.
Standards - where manufacturers agree on common designs -
only appear when manufacturers agree they’ve a common
interest in building “volume”, not locking customers in.
This happened very early with bipolar TTL logic.
Smart phones are mostly Linux / Android,
with Apple still able to sell non-commodity designs
at premium prices.
Remember Microsoft’s foray, via Nokia, into Mobiles?
“Pocket PC” and “Windows Mobile” / Windows Phone:
Crashed and burned.
Even Nokia, then largest phone seller,
with the proven Symbian O/S,
failed against Android.
--
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
next prev parent reply other threads:[~2023-02-05 10:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 19:02 [TUHS] Typesetter C compiler Noel Chiappa
2023-02-02 21:57 ` [TUHS] " Jonathan Gray
2023-02-03 0:43 ` Jonathan Gray
2023-02-02 22:36 ` [TUHS] Proper use of TUHS (was Re: Typesetter C compiler) Dan Cross
2023-02-02 22:41 ` [TUHS] " Larry McVoy
2023-02-02 22:47 ` Jim Capp
2023-02-03 1:44 ` Dave Horsfall
2023-02-03 13:17 ` Alan D. Salewski
2023-02-03 13:55 ` Larry McVoy
2023-02-06 20:02 ` Chris Hanson
2023-02-03 14:11 ` Chet Ramey
2023-02-03 14:15 ` Larry McVoy
2023-02-03 16:39 ` Dan Cross
2023-02-03 16:54 ` Larry McVoy
2023-02-03 17:08 ` Dan Cross
2023-02-03 17:11 ` Steve Nickolas
2023-02-03 17:26 ` [TUHS] move to COFF " Will Senn
2023-02-03 17:31 ` [TUHS] " Will Senn
2023-02-03 17:45 ` [TUHS] " Bakul Shah
2023-02-05 10:42 ` steve jenkin [this message]
2023-02-04 8:03 ` [TUHS] A List for New Systems Influenced by History. (Was: Proper use of TUHS) Ralph Corderoy
2023-02-04 13:56 ` [TUHS] " Larry McVoy
2023-02-04 17:31 ` [TUHS] Re: A List for New Systems Influenced by History Angel M Alganza
2023-02-03 6:36 ` [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler) Lars Brinkhoff
2023-02-04 22:38 ` Tomasz Rola
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=B7AA4E29-17E8-40D2-94A3-D9EFE51BECF2@canb.auug.org.au \
--to=sjenkin@canb.auug.org.au \
--cc=bakul@iitbombay.org \
--cc=tuhs@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).