The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jon Steinhart <jon@fourwinds.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Cole's Slaw
Date: Wed, 09 Dec 2020 18:12:16 -0800	[thread overview]
Message-ID: <202012100212.0BA2CGEd029177@darkstar.fourwinds.com> (raw)
In-Reply-To: <CAD2gp_SdbUQjT90fstuc9JvQ_ZzKnzeQ9M0x5kGqjtCxQEtYbw@mail.gmail.com>

John Cowan writes:
>
> That certainly worked for closing the Digital Divide.  Some suggested
> > allocating billions in tax dollars to subsidize the un-networked in the
> > 1990s and 2000's.  Instead we mostly just waited a few years.
> > Semiconductor economics plus consumer behavior (demand rises very
> > quickly as prices drop, which provides economies of scale) solve most of
> > the problem for you.
> >
>
> Not quite yet.  As of 2018, which is the latest data I can find, only 73%
> of U.S. households have 10 Mbps download speed or better, and only 46% have
> 100 Mbps service or better.  If you look at the lowest quartile of
> household incomes, the figures are 33% and 18% respectively.  (You want
> adoption figures, not deployment figures.)  Wiring up the whole country is
> fine, but if people won't or can't use it, it does little good.

This is not a really TUHS topic.  As one of those people who does not have
decent internet service and am still waiting I'd be happy to see some money
spent to broaden availability.  This is not being a matter of waiting years,
it's a matter of waiting decades so far.  Access is an equity issue as it's
essential for everything from participating in government, schooling, and
almost every other aspect of life today.  Maybe people with good service are
willing to have everyone else wait but IMHO society isn't well served that way.

Jon

  reply	other threads:[~2020-12-10  2:12 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  4:35 [TUHS] Were cron and at done at the same time? Or one before the other? M Douglas McIlroy
2020-12-09 15:40 ` Clem Cole
2020-12-09 15:46   ` Niklas Karlsson
2020-12-09 16:01   ` Bakul Shah
2020-12-09 16:11     ` Clem Cole
2020-12-09 17:05       ` Bakul Shah
2020-12-09 17:42         ` Dan Stromberg
2020-12-09 23:46           ` Nemo Nusquam
2020-12-14 20:28     ` Dave Horsfall
2020-12-14 22:23       ` Thomas Paulsen
2020-12-14 23:04         ` Andrew Hume
2020-12-14 23:59       ` Harald Arnesen
2020-12-17  4:08         ` John Cowan
2020-12-15  2:57       ` Bakul Shah
2020-12-15  3:05         ` Warner Losh
     [not found]   ` <CAC20D2PXZY9aWgDf-RknROs6JbKEUjzbQ2BRzfTgTR07pXni3g@mail.g mail.com>
2020-12-09 16:04     ` John Foust
2020-12-09 16:40   ` Warner Losh
2020-12-09 16:53     ` Jon Steinhart
2020-12-09 16:58   ` Theodore Y. Ts'o
2020-12-09 19:58     ` Dan Cross
2020-12-09 20:30       ` Will Senn
2020-12-13  1:07       ` Theodore Y. Ts'o
2020-12-13  1:56         ` Jon Steinhart
2020-12-13  2:58           ` Theodore Y. Ts'o
2020-12-13  3:07             ` Jon Steinhart
2020-12-13 16:49               ` Theodore Y. Ts'o
2020-12-13 19:06                 ` [TUHS] Were cron and at done at the same time? Or one before the other? [ really linux and filesystems ] Jon Steinhart
2020-12-13  3:02         ` [TUHS] Were cron and at done at the same time? Or one before the other? Dan Cross
2020-12-09 23:22     ` Bakul Shah
2020-12-09 23:44       ` Steffen Nurpmeso
2020-12-09 23:51         ` Steffen Nurpmeso
2020-12-10  0:19   ` [TUHS] Cole's Slaw John Gilmore
2020-12-10  0:29     ` Larry McVoy
2020-12-10  0:53       ` Erik E. Fair
2020-12-10  3:10         ` George Michaelson
2020-12-12 21:11       ` Dave Horsfall
2020-12-10  1:49     ` John Cowan
2020-12-10  2:12       ` Jon Steinhart [this message]
2020-12-12  2:56   ` [TUHS] Were cron and at done at the same time? Or one before the other? Dave Horsfall
2020-12-12 19:10     ` scj

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=202012100212.0BA2CGEd029177@darkstar.fourwinds.com \
    --to=jon@fourwinds.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).