The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: Paul Ruizendaal <pnr@planet.nl>, "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: Origins of the frame buffer device
Date: Thu, 9 Mar 2023 09:42:36 -0500	[thread overview]
Message-ID: <CABH=_VSqcdVfy3nZXSjWuf7u=ZXObn5_6N=Q_jnTuOSAT3PLGg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2N266d=CxskhE8SzGShYxz+DMoh=XjKb2WdKBjkaH=9qg@mail.gmail.com>

On 3/8/23, Clem Cole <clemc@ccc.com> wrote:
(regarding the issue of the definition of "workstation")
> And herein lies the issue.  The term was taken from the
> engineering/architecture style definition of the 50s/60s - where someone
> had a desk/table/bench and *area to do 'work'*.

Correct.  According to etymologyonline.com, the term "workstation"
dates from 1950, and in the computer sense from 1972.  It is a place
(station) where one does one's work.  In a jeweler's shop the bench
where watches are cleaned and repaired could be called the
workstation.

Since the early 1980s when I first encountered them, I've always
regarded the distinction between a workstation, a PC, and a word
processor to be a matter of how the machine is used rather than the
hardware itself.  All three (workstation, PC, WP) are single-user
computing devices.  The distinction is that PCs are for non-business
use and word processors are limited-function devices.  A computer
workstation is a single-user, general-purpose computer used for
business or technical purposes.

>> Would a Tek 4014 connected to a VAX count?

If the VAX were only being used by one person at a time (i.e., not a
timesharing system), then I would say yes.  IMO the PDP-1 was often
used as a workstation.

-Paul W.

  parent reply	other threads:[~2023-03-09 14:42 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 15:01 [TUHS] " Paul Ruizendaal via TUHS
2023-03-05 17:29 ` [TUHS] " Grant Taylor via TUHS
2023-03-05 18:25 ` Kenneth Goodwin
2023-03-06  8:51   ` Paul Ruizendaal via TUHS
2023-03-06  8:57     ` Rob Pike
2023-03-06 11:09       ` Henry Bent
2023-03-06 16:02         ` Theodore Ts'o
2023-03-06 22:47       ` Paul Ruizendaal via TUHS
2023-03-06 23:10         ` Rob Pike
2023-03-08 12:53           ` Paul Ruizendaal
2023-03-08 14:23             ` Dan Cross
2023-03-08 15:06               ` Paul Ruizendaal
2023-03-08 19:35                 ` Dan Cross
2023-03-08 16:55               ` Theodore Ts'o
2023-03-08 17:46                 ` Clem Cole
2023-03-08 17:45               ` Clem Cole
2023-03-08 18:12                 ` segaloco via TUHS
2023-03-08 18:21                   ` Larry McVoy
2023-03-08 18:43                     ` Kenneth Goodwin
2023-03-08 18:45                     ` Steffen Nurpmeso
2023-03-08 22:44                     ` Clem Cole
2023-03-09 14:42                 ` Paul Winalski [this message]
2023-03-06 23:20         ` segaloco via TUHS
2023-03-07  1:24     ` Kenneth Goodwin
2023-03-08  3:07     ` Rob Gingell
2023-03-08 12:51       ` Paul Ruizendaal via TUHS
2023-03-08 13:05         ` Warner Losh
2023-03-08 13:17         ` Arno Griffioen via TUHS
2023-03-07  1:54 ` Kenneth Goodwin
2023-03-05 18:52 Noel Chiappa
2023-03-05 20:43 ` Rob Pike
2023-03-06 10:43   ` Jonathan Gray
2023-03-07  1:21 ` Kenneth Goodwin
2023-03-08  5:43 ` Lars Brinkhoff
2023-03-09 23:24   ` emanuel stiebler
2023-03-10  1:44     ` Lawrence Stewart
2023-03-06 23:16 Norman Wilson
2023-03-06 23:24 ` Larry McVoy
2023-03-07 12:08   ` arnold
2023-03-07 16:42   ` Theodore Ts'o

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='CABH=_VSqcdVfy3nZXSjWuf7u=ZXObn5_6N=Q_jnTuOSAT3PLGg@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=clemc@ccc.com \
    --cc=pnr@planet.nl \
    --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).