The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Joseph Holsten" <joseph@josephholsten.com>
To: "Tautological Eunuch Horticultural Scythians" <tuhs@tuhs.org>
Subject: [TUHS] Collecting notes for future “historians” was: Earliest UNIX Workstations?
Date: Thu, 26 Jan 2023 13:29:26 -0800	[thread overview]
Message-ID: <c4b08a9d-a0eb-45f7-98c6-1e715cb58908@app.fastmail.com> (raw)
In-Reply-To: <202301261804.30QI4sd9132510@darkstar.fourwinds.com>

I love how I can fire off a query and get so much info. But I wonder: does TUHS have any way of consolidating these threads into easily digestible documents? What would be preferred, a wiki? or a source control repo with “articles”?

I’m mostly wanting summarize this kind of thread and include links to mailing list messages and other resources.
But also, I’m lazy and I am not committing to editing a journal.

On Thu, Jan 26, 2023, at 10:04, Jon Steinhart wrote:
> John Cowan writes:
>> On Wed, Jan 25, 2023 at 8:47 PM Chris Hanson <cmhanson@eschatologist.net>
>> wrote:
>>
>>
>> > > * What do I really mean by workstation? Ex.gr. If an installation had a
>> > PDP-11 with a single terminal and operator, is it not a workstation? Is it
>> > the integration of display into the system that differentiates?
>> >
>> > I think "a graphical system intended to be used by a professional to use
>> > in their work" is a good starting point for a definition. I should check at
>> > home tonight how "A History of Personal Workstations" defines it.
>> >
>>
>> WP says the Terak 8510/a was the first graphical workstation; it came out
>> in 1976-77 and ran the UCSD p-System.  I had never heard of it before. The
>> first *personal* workstation (non-graphical) was probably the IBM 1620 (aka
>> the CADET system, "Can't Add, Doesn't Even Try") from 1959.
>
> I think that WP is not correct here, the Tektronix 4051 beat it to market
> by a year.

  reply	other threads:[~2023-01-26 21:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26  0:31 [TUHS] " Joseph Holsten
2023-01-26  0:51 ` [TUHS] " segaloco via TUHS
2023-01-26  1:06   ` Luther Johnson
2023-01-26  1:15     ` Jon Steinhart
2023-01-26  1:01 ` Larry Stewart
2023-01-26 13:25   ` Marc Donner
2023-01-26 13:58     ` arnold
2023-01-31  2:03   ` Mary Ann Horton
2023-01-31 17:43     ` Marc Donner
2023-01-26  1:12 ` Tom Lyon
2023-01-26  1:47 ` Chris Hanson
2023-01-26  7:20   ` John Cowan
2023-01-26  7:33     ` Dave Horsfall
     [not found]     ` <CAD2gp_QtUPmd78yAixvKK1wzPX67HKZXzU5cJnVUbcWtMounGQ@mail.g mail.com>
2023-01-26 16:35       ` John Foust via TUHS
2023-01-26 17:58     ` Jon Forrest
2023-01-26 18:04     ` Jon Steinhart
2023-01-26 21:29       ` Joseph Holsten [this message]
2023-01-26 21:38         ` [TUHS] Re: Collecting notes for future “historians” was: " Jon Steinhart
2023-01-26 22:41           ` Joseph Holsten
2023-01-27  0:34             ` segaloco via TUHS
2023-01-27  0:36             ` G. Branden Robinson
2023-01-27  0:53               ` segaloco via TUHS
2023-01-27  1:28                 ` David Arnold
2023-01-27  1:35                   ` Warner Losh
2023-01-26  9:52 ` [TUHS] " emanuel stiebler
2023-01-26  9:58   ` Rob Pike
2023-01-26 10:09   ` Jaap Akkerhuis via TUHS
2023-01-26 15:14 ` Clem Cole

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=c4b08a9d-a0eb-45f7-98c6-1e715cb58908@app.fastmail.com \
    --to=joseph@josephholsten.com \
    --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).