9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] quotefmtinstall
Date: Mon, 10 Dec 2012 07:57:06 +0200	[thread overview]
Message-ID: <78587f5f1632c8cf8c715e64c46f6c40@proxima.alt.za> (raw)
In-Reply-To: <e96befc4818df6fc022798d2eae3e15d@chula.quanstro.net>

> 0.  the essence of charles' point is that persistent memory is cheep, and little
> fiddly bits are expensive, from a developer's point of view.  and by
> cheep, we're talking silly cheep.  1kb of disk costs 100 nanodollars.  it's the
> order of magnitude that's important here, a small integer factor won't
> make disks expensive.
>
The digital divide, what can I say?

Sadly, I can't buy nanodollars' worth of technology, even though it is
being discarded daily in the western world by the megadollar.  Even
the RaspberryPI is beyond reach (we can approach western sponsors for
funding, but that creates a form of slavery that africans are
understandably reluctant to depend on - our leaders don't mind, but
some of us have a social conscience).

I guess I'm asking you and Charles and others to keep that in mind
when you contribute to the conspiracy to make the digital divide
bigger, no matter how small your contribution.

> 1.  it can't be optional.  this is the sort of thing that got
> latter-day unix in so much trouble.  if you want your program to
> work everywhere (as most people do) you have to program for the
> least common denominator, so every program will need
> quotefmtinstall().  so there will be a net savings of zero.  and
> since the problem will now appear on some systems, it will probablly
> be harder to remember that you've forgotten to quotefmtinstall.
>
> 2.  if you want to save overall storage, the print library should ditch
> standard support for the rune*print() functions.  only 4 programs use
> them.

I understand the technological issues more or less well enough.  But
where I stand, I can't ignore the social implications of consuming
resources as soon as they become available.  I can think of a penalty
that could be paid by inefficient consumers, but in a world where
survival of the fittest is the guiding civilising principle, I am
geographically an endangered species.

++L

PS: Your "if you want your program to work everywhere (as most people
do)" is spurious.  Why are we programming for anything but MS Windows,
if that is the case?




  reply	other threads:[~2012-12-10  5:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-08 12:51 Charles Forsyth
2012-12-08 16:24 ` lucio
2012-12-09 14:49   ` erik quanstrom
2012-12-10  5:57     ` lucio [this message]
2012-12-10 15:03       ` erik quanstrom
2012-12-11  5:39         ` hiro
  -- strict thread matches above, loose matches on Subject: below --
2005-03-11 17:16 Charles Forsyth
2005-03-11 19:35 ` Ronald G. Minnich
2005-03-11 19:43   ` Charles Forsyth
2005-03-11 19:51     ` Ronald G. Minnich
2005-03-11 20:03       ` Charles Forsyth
2005-03-11 20:31         ` Ronald G. Minnich
2005-03-12  4:29           ` vdharani
2005-03-11 19:51     ` Ronald G. Minnich
2005-03-11 15:46 Ronald G. Minnich
2005-03-11 16:01 ` Wes Kussmaul
2005-03-11 16:24   ` Derek Fawcus
2005-03-11 16:51     ` David Leimbach
2005-03-11 16:56       ` Russ Cox
2005-03-11 18:52   ` Ronald G. Minnich

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=78587f5f1632c8cf8c715e64c46f6c40@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.net \
    /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).