Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: segaloco <segaloco@protonmail.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: White Backgrounds on GUIs after Dark Backgrounds on Terminals?
Date: Fri, 16 Jun 2023 12:08:21 -0400	[thread overview]
Message-ID: <CABH=_VR-k2_OWtm7_oRzMK9jnq9j8aQGtmUxsu7TcycCZqRYdg@mail.gmail.com> (raw)
In-Reply-To: <vIvtT738PyORxWFUpsDbn5Mw-22alGzJi8IgkPVXgKwhnqfRo29VZaMXLcRSeicCzARbhWjbiUDcmpOAh8uXwKKOJrbWx3SosIBZcZPaEpI=@protonmail.com>

On 6/15/23, segaloco via COFF <coff@tuhs.org> wrote:
>
> So terminals, they started as typewriters with extra steps, a white piece of
> paper on a reel being stamped with dark ink to provide feedback from the
> machine. When video terminals hit the market, the display was a black screen
> with white, orange, green, or whatever other color of phosphor they bothered
> to smear on the surface of the tube. Presumably this display style was
> chosen as on a CRT, you're only lighting phosphor where there is actually an
> image, unlike the LCD screens of today. So there was a complete contrast
> shift from dark letters on white paper to light letters on an otherwise
> unlit pane of glass.

The phosphors on CRT screens don't last forever.  You only want to
light them when necessary.  CRTs also suffer from the problem of
burn-in.  If you keep the same picture illuminated for a long period
of time that pixel pattern gets burned into the phosphors.  This is
why the later GUI CRTs had screen saver software that displayed an
ever-changing picture to prevent burn-in.  This isn't a problem with
the modern, non-cathode-ray displays.  Good ol' flying toasters.

-Paul W.

  parent reply	other threads:[~2023-06-16 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 20:55 [COFF] " segaloco via COFF
2023-06-16  1:24 ` [COFF] " Warner Losh
2023-06-16  2:57   ` Adam Thornton
2023-06-16 16:08 ` Paul Winalski [this message]
2023-06-16 16:44   ` segaloco via COFF
2023-06-16 16:51 ` Clem Cole
2023-06-16 17:33   ` segaloco via COFF
2023-06-17  5:28     ` Tomasz Rola

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=_VR-k2_OWtm7_oRzMK9jnq9j8aQGtmUxsu7TcycCZqRYdg@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=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).