Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: COFF <coff@tuhs.org>
Subject: [COFF] Bell System and the Video Game Industry?
Date: Tue, 04 Jul 2023 01:57:55 +0000	[thread overview]
Message-ID: <_l_rdK2ywBoEAheCu4dCFyJ3cyXymIXgMK9-_bgAtMwLXtmr2sZnuRvjFc6jqn6K0X_E2MuSEMm5_iVO7eBeYTOpRHVRuypykZD_au00R-c=@protonmail.com> (raw)

So this evening I've been tinkering with a WECo 2500 I've been using for playing with telecom stuff, admiring the quality of the DTMF module, and it got me thinking, gee, this same craftsmanship would make for some very nice arcade buttons, which then further had me pondering on the breadth of the Bell System's capabilities and the unique needs of the video game industry in the early 80s.

In many respects, the combination of Western Electric and Bell Laboratories could've been a hotbed of video game console and software development, what with WECo's capability to produce hardware such as coin slots, buttons, wiring harnesses for all sorts of equipment, etc. and then of course the software prowess of the Labs.

Was there to anyone here's knowledge any serious consideration of this market by Bell?  The famous story of UNIX's origins includes Space Travel, and from the very first manual, games of various kinds have accompanied UNIX wherever it goes.  It seems that out of most companies, the Bell System would've been very well poised, what with their own CPU architecture and other fab operations, manufacturing and distribution chains, and so on.  There's a looooot of R&D that companies such as Atari and Nintendo had to engage in that the Bell System had years if not decades of expertise in.  Would anti-trust stuff have come into play in that regard?  Bell couldn't compete in the computer market, and I suppose it would depend on the legal definitions applicable to video game hardware and software at the time.

In any case, undercurrent here is the 2500 is a fine telephone, if the same minds behind some of this WECo hardware had gone into video gaming, I wonder how different things would've turned out.

- Matt G.

             reply	other threads:[~2023-07-04  1:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  1:57 segaloco via COFF [this message]
2023-07-06  8:48 ` [COFF] " steve jenkin
2023-07-06 22:29   ` segaloco via COFF
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='_l_rdK2ywBoEAheCu4dCFyJ3cyXymIXgMK9-_bgAtMwLXtmr2sZnuRvjFc6jqn6K0X_E2MuSEMm5_iVO7eBeYTOpRHVRuypykZD_au00R-c=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=segaloco@protonmail.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).