Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: steve jenkin <sjenkin@canb.auug.org.au>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: Bell System and the Video Game Industry?
Date: Thu, 06 Jul 2023 22:29:09 +0000	[thread overview]
Message-ID: <C6cSqHE6kO6bEW3qG2_KHI_bK1owkpWbpI2X48Z0YSGXSKHzDiMWodxZEGpGdbhATU0l1m5znUj-XwzF-0_lt1hiPgfl0Xw_0DPY_ikOgb0=@protonmail.com> (raw)
In-Reply-To: <E7705361-1115-4086-BF12-D95AD1B24AA5@canb.auug.org.au>

> Their mismanagement killed the business, causing Bell Labs as we knew it, to eventually fade away.
> 
> I hope that’s somewhat an answer for me, if not correct & complete, it also explains why the ‘combatants’
> aren’t keen to talk about their experiences.
> 
> all my best
> steve

Oh I know that struggle all too well, what potential are we on the cusp of vs. what do the suits want/need.  Given WECo's legacy in the audio realm, I find that Plan9 story particularly disheartening, electrified (audio) signals and the complex manipulation and supplementation thereof is what one would think is the chief concern of a telecom behemoth.

I'd never heard the bit about the hardware business winding up with NCR, although I guess I've never looked in that direction as hard as the USL path through Novell.  That gives me more to study in my nebulous 3B20 and kin research.

I'm glad I wasn't in the know at the time of all the SCO stuff (and was a kid that didn't care) because I probably would've shoved all sorts of feet into my mouth in the sorts of debates over software freedom that were going on at the time.  Looking back, that must've been such a frustrating time, I don't blame folks for coming out of that with battle scars.

Well now I've got this morbid curiosity to see if I can FPGA a WE32000-ish video game console...but that goes on the endless pile of "eventually"s.

Thanks for the background Steve!

- Matt G.

  reply	other threads:[~2023-07-06 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  1:57 [COFF] " segaloco via COFF
2023-07-06  8:48 ` [COFF] " steve jenkin
2023-07-06 22:29   ` segaloco via COFF [this message]
2023-07-06 23:12   ` Brad Spencer

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='C6cSqHE6kO6bEW3qG2_KHI_bK1owkpWbpI2X48Z0YSGXSKHzDiMWodxZEGpGdbhATU0l1m5znUj-XwzF-0_lt1hiPgfl0Xw_0DPY_ikOgb0=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=segaloco@protonmail.com \
    --cc=sjenkin@canb.auug.org.au \
    /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).