Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: Clem Cole <clemc@ccc.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: White Backgrounds on GUIs after Dark Backgrounds on Terminals?
Date: Fri, 16 Jun 2023 17:33:24 +0000	[thread overview]
Message-ID: <3j50sQfrIaP4KY538ptQg5480Fc8VW-NLkOlqM5hOrMo3sE8orBUPg3bxKnX3LtYZBV76G4K5elmvePm-OI-L3VlIFcOy8fk9uDY0Ro5gOs=@protonmail.com> (raw)
In-Reply-To: <CAC20D2NgVdMEqyvje6nVaDU83wYoO2C3+-svyW4JWrURhLb8Gg@mail.gmail.com>

> As for the current light on dark, I wonder if this is just a new set of engineers making their mark. I'm sure it's better. The cost is the same, so now it's just marketing and a way to show off being different - e.g., new/cool.

That kinda gets at the root of what I'm puzzling on too.  At times where a dark color scheme would've had some, if even minor, technical benefit, it was stepped away from (as you said, Xerox is a paper company, that all makes perfect sense), however, now we're seeing the pendulum swing at a time where any amount of phosphor relief or other potential power savings from not driving visual content are lost on modern display technologies.

And I'll be the first to admit the difference is probably negligible, it's not like I've done a power consumption analysis on a tube, although in this discussion it has made me curious if a noticable difference in power consumption could be measured between two tubes powered up to the same state but one has zero drawing going on (i.e. no electrons beaming to the screen) whereas the other one is on full blast bright white.  I'll add it to the list of experiments for this winter...

> side tidbit - he has the patent on the loadable curser - which was initially a martini glass, not an hourglass to show time

I was waiting for a work conference to kick off as I was reading this email, shared this tidbit.  Our resident COBOL/dinosaur era guy just remarked if programming at the time didn't drive you to drink there was something wrong with you.

- Matt G.

  reply	other threads:[~2023-06-16 17:33 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
2023-06-16 16:44   ` segaloco via COFF
2023-06-16 16:51 ` Clem Cole
2023-06-16 17:33   ` segaloco via COFF [this message]
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='3j50sQfrIaP4KY538ptQg5480Fc8VW-NLkOlqM5hOrMo3sE8orBUPg3bxKnX3LtYZBV76G4K5elmvePm-OI-L3VlIFcOy8fk9uDY0Ro5gOs=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=clemc@ccc.com \
    --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).