The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Matt Day <fjarlq@gmail.com>
To: Dan Cross <crossd@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] First machine to run rogue?
Date: Fri, 2 Jul 2021 20:21:07 -0600	[thread overview]
Message-ID: <CAHrGxA2bB31JctWvXxN_46-Y+zo4JcuYXpGZQXd3aHZNB6Y5ng@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W6Tr=b7O2Bn+GkXYCadCqrDdXiLTkL=eX-RaDZ9a7m+bw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3680 bytes --]

Quoting from David Craddock's book, Dungeon Hacks (2015), pages 34-35:

> By the time Toy and Wichman started at UC Santa Cruz, BSD UNIX had entered
> widespread usage across UC campuses and was branching out to other schools.
> Each new version of BSD, released on cassette tape, included handy programs
> written by Joy and other hackers. One program was curses, written by Ken
> Arnold. Arnold had written curses according to the UNIX creed: a simple
> tool fashioned for a specific purpose. Wielding curses like a paintbrush,
> users could place text such as letters, numbers, and symbols at any
> location on the screen.



The moment he used curses, Toy saw its potential. In 1980, he went to
> Wichman and suggested they use curses to create a graphical adventure game
> with a twist. Unlike Colossal Cave Adventure and its derivatives, their
> game would construct brand new environments and challenges every time. An
> avid Dungeons & Dragons player, he invented a fantasy-themed setting and
> premise. Players would assume the identity of an adventurer who entered the
> Dungeons of Doom, a series of levels filled with monsters and treasure.



Wichman loved the idea and dubbed the game Rogue. "I think the name just
> came to me. Names needed to be short because you invoked a program by
> typing its name in a command line. I liked the idea of a rogue. We were
> coming from a Dungeons & Dragons background, but we were creating a
> single-player game. You weren't going down into the dungeon with a party.
> The idea was that this is a person going off on his or her own. It captured
> the theme very succinctly."



Apropos of UNIX, Toy chose to write Rogue in the C language. C produced
> fast code, while BASIC was slower and meant for smaller programs. Wichman,
> still a few steps behind Toy in programming prowess, learned C by watching
> Toy program their game. "The early alpha versions of Rogue were probably
> all my code, but Glenn [Wichman] made lots of contributions in terms of
> design," Toy recalled. "I think it's quite fair to say that the game was a
> pretty straight collaboration between Glenn [Wichman], Ken [Arnold], and me
> by the time it was done. I feel pretty good about that."



Toy and Wichman realized they wouldn't be able to stay at school during all
> hours to write their game. Fortunately, they didn't need to. As employees
> of the computer science division, they had special lab privileges. Setting
> up an ADM-3a terminal in their apartment, they could dial into the VAX
> 11/780 shunted off in a basement somewhere at UC Santa Cruz. The connection
> was established through their 300-baud modem -- a device that would take
> several minutes to transmit the text on an average-length Wikipedia page
> today -- enabling them to write the vast majority of Rogue from the comfort
> of their apartment.


Craddock's notes explain that the quotes of Michael Toy and Glenn Wichman
"come from interviews conducted via phone, Skype, and email over 2012-2014."

I think you must be right about the first machine being something running
BSD UNIX.

Matt

On Thu, Jul 1, 2021 at 8:07 PM Dan Cross <crossd@gmail.com> wrote:

> What was the first machine to run rogue? I understand that it was written
> by Glenn Wichman and Michael Toy at UC Santa Cruz ca. 1980, using the
> `curses` library (Ken Arnold's original, not Mary Ann's rewrite). I've seen
> at least one place that indicates it first ran on 6th Edition, but that
> doesn't sound right to me. The first reference I can find in BSD is in 2.79
> ("rogue.doc"), which also appears to be the first release to ship curses.
>
> Anyone have any info? Thanks!
>
>         - Dan C.
>
>

[-- Attachment #2: Type: text/html, Size: 5335 bytes --]

  parent reply	other threads:[~2021-07-03  2:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  2:05 Dan Cross
2021-07-02  2:51 ` Clem Cole
2021-07-02 11:24   ` Dan Cross
2021-07-02 11:40     ` arnold
2021-07-02 12:14       ` Dan Cross
2021-07-02 13:07         ` Clem Cole
2021-07-02 15:24           ` Brad Spencer
2021-07-02 16:27             ` Adam Thornton
2021-07-02 21:09           ` Dan Cross
2021-07-10  3:17             ` Mary Ann Horton
2021-07-10  4:00               ` Erik E. Fair
2021-07-10  5:04               ` Jon Forrest
2021-07-10 21:09                 ` Mary Ann Horton
2021-07-02 13:11         ` Bakul Shah
2021-07-02 13:22           ` Richard Salz
2021-07-03  1:10             ` Dan Cross
2021-07-02 13:04       ` Clem Cole
2021-07-13 17:48         ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-07-03  2:21 ` Matt Day [this message]
2021-07-03 14:15   ` Clem Cole
2021-07-03 15:08     ` Warner Losh
2021-07-03 22:25       ` Eric Allman

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=CAHrGxA2bB31JctWvXxN_46-Y+zo4JcuYXpGZQXd3aHZNB6Y5ng@mail.gmail.com \
    --to=fjarlq@gmail.com \
    --cc=crossd@gmail.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).