The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Andy Kosela <akosela@andykosela.com>
To: crossd@gmail.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] cat -v and other complaints
Date: Fri, 07 Sep 2018 06:40:37 +0200	[thread overview]
Message-ID: <5b920145.7aDYuhN/FRnTadNW%akosela@andykosela.com> (raw)
In-Reply-To: <CAEoi9W5BBxOsYvQ5RAiJWHy0CKRTxeUPOGFCDfs4zKkNvKmc6g@mail.gmail.com>

Dan Cross <crossd@gmail.com> wrote:

> On Thu, Sep 6, 2018 at 5:56 PM Andy Kosela <akosela@andykosela.com> wrote:
>
> > [snip]  Well, you can't tell me
> > this system was designed with the idea of running it using text terminal
> > and no mouse.
>
>
> I won't, because it wouldn't be true. You are correct that it was always
> intended to be used with a graphical console. But you keep talking about
> "text terminals" and therein lies the confusion: our text terminals haven't
> been purely "text" since the teletype days. Even green-screen serial
> terminals have graphics adapters to draw characters on the screen.

I think I was clear enough and meant 'text terminal' as a physical glass
TTY e.g.  vt220 from DEC, but understand now why someone might have
interpreted it differently.

There is also a big difference between a text mode (character mode)
where what we see on the screen is addressed in terms of characters
rather than individual pixels and a bitmap mode (graphics mode) also
known as APA (all points addressable) mode where every pixel is
addressable[1].

Inherent in the text mode is also the concept of monospace fonts which
some people prefer to this day.

>
> There is also no cursor addressing, no curses.
>
>
> Actually, there *is* a graphical program to emulate a vt-series terminal,
> but pretty much no one uses it. So while strictly speaking this is
> incorrect, it is essentially correct for all intents and purposes.
>
> But it begs the question: why would you *want* to use that sort of
> interface? That was appropriate for an HP or DEC terminal connected via a
> low-bandwidth link (e.g., serial) or a shared host computer. Once we moved
> onto personal workstation-class machines with graphics adapters, why
> continue with that paradigm? 

Why there are still people running C64, Atari XL/XE or Amiga?  Even
more, some of them think those computers are still better than the
machines of today...

In the Unix community there are some that still prefer to use old CRT
terminals or MS-DOS era PC monitors using only text mode.  Why I can't
speak for all of them, I can speak for myself and explain my motivation
behind it.  I instantly fell in love with a text mode when I first
started computing on Commodore and Atari machines in the 80s and then
naturally advanced to a text mode on MS-DOS era PC's. 

I never really ran Linux or *BSDs with X Window System -- always
preferred pure text mode.  It is aesthetically pleasing and most elegant
to converse with a machine using only text, and a text mode as displayed
on cathode ray tube (CRT) is the most beautiful representation of such
an idea. 

Although these days I'm using sometimes MacBook (who doesn't?)
which is using of course the bitmap mode, I still prefer to experience
the full text mode on a real CRT and actually collect them as they are
becoming more and more rare.

[1] https://en.wikipedia.org/wiki/Text_mode


--Andy

  reply	other threads:[~2018-09-07  4:41 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 14:25 Clem Cole
2018-08-29 22:34 ` Dave Horsfall
2018-08-29 23:36   ` Larry McVoy
2018-08-30  1:14     ` Clem cole
2018-08-30  1:15       ` Clem cole
2018-08-30  2:43       ` Kevin Bowling
2018-08-30  2:59         ` George Michaelson
2018-08-31  0:27         ` Dave Horsfall
2018-08-31  0:41           ` Dan Cross
2018-08-31  1:58             ` Larry McVoy
2018-08-31 11:38           ` ron
2018-08-31 14:41           ` [TUHS] UNIX System names - since UNIX was a Trademark Clem Cole
2018-08-31 15:13             ` Eric Wayte
2018-08-31 15:17             ` William Pechter
2018-08-31 15:25               ` Clem Cole
2018-09-01  0:10               ` John P. Linderman
2018-09-01  0:18                 ` ron
2018-09-01  0:55                   ` Nemo
2018-09-01  7:37                     ` Dave Horsfall
2018-09-01 13:54                       ` Nemo
2018-09-01 17:03                       ` Paul Winalski
2018-09-03  1:14                         ` Robert Brockway
2018-09-30 20:57                 ` Lyndon Nerenberg
2018-10-01 16:26                   ` Paul Winalski
2018-09-01  0:00             ` Dave Horsfall
2018-08-31 21:56 ` [TUHS] cat -v and other complaints Cág
2018-09-01  3:37   ` Andrew Warkentin
2018-09-03 18:04     ` Cág
2018-09-03 18:11       ` Kurt H Maier
2018-09-03 18:56         ` Cág
2018-09-04  6:10           ` Andy Kosela
2018-09-04  6:41             ` ron minnich
2018-09-04  9:34               ` Andy Kosela
2018-09-04 10:23                 ` Dan Cross
2018-09-04 14:22                 ` ron minnich
2018-09-06 20:02                   ` Andy Kosela
2018-09-06 20:49                     ` ron minnich
2018-09-06 21:55                       ` Andy Kosela
2018-09-07  1:59                         ` Dan Cross
2018-09-07  4:40                           ` Andy Kosela [this message]
2018-09-30 21:32           ` Lyndon Nerenberg
2018-09-03 20:08         ` Bakul Shah
2018-09-03 20:41           ` Kurt H Maier
2018-09-03 21:46             ` Bakul Shah
2018-09-04  0:52               ` Kurt H Maier
2018-09-06 20:29 Norman Wilson
2018-09-06 22:16 ` Andy Kosela
2018-09-08 12:02 [TUHS] [TUHS} " Doug McIlroy
2018-09-08 13:36 ` Will Senn
2018-09-08 14:22   ` [TUHS] " Ralph Corderoy
2018-09-08 16:10     ` Arthur Krewat

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=5b920145.7aDYuhN/FRnTadNW%akosela@andykosela.com \
    --to=akosela@andykosela.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).