The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] Questions for TUHS great minds
Date: Tue, 17 Jan 2017 13:36:32 +0000	[thread overview]
Message-ID: <20170117133632.GB12237@yeono.kjorling.se> (raw)
In-Reply-To: <512ABFFE-C238-45CA-9C43-CF9A84E4DE49@tfeb.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2176 bytes --]

On 17 Jan 2017 13:09 +0000, from tfb at tfeb.org (Tim Bradshaw):
> I think we've all lived in a wonderful time where it seemed like
> various exponential processes could continue for ever: they can't.

I'm personally inclined to agree with Tim here. That's not to say that
I don't think some of those processes could be pushed a bit farther,
but as much as we would love it in some cases, a function on the form
f(x)=Ca^{Dx} (for any values of C, D and a) describing something that
can exist in the real world simply cannot continue forever before
encountering some real-world limit.

Zoom out what appears to be an exponential curve and more often than
not, it turns out that what looked like an exponential curve was
really the first portion of a S curve or (even worse in many cases) a
portion of a parabola. Either that, or it's something like the
Tsiolkovsky rocket equation or the relativistic colinear velocity
addition formula, where the exponent is something you try very hard to
_avoid_ the effects of for one reason or another.

What could conceivably change that picture somewhat is a total
paradigm shift in computing, kind of like if large general-purpose
quantum computers turn out to be viable after all. But even in that
case I'm pretty sure that at some point we would realize that we are
on the same kind of S curve or parabola there as well, only having
delayed the inevitable or shifted the origin.

That's not to say that even steady-state computer power can't provide
huge benefits. It absolutely can. Even the computers we have and are
able to actually build today are immensely powerful both in terms of
computational capability and storage, and they are, to a large degree,
scalable with the proper software and algorithms. The kind of computer
I have _at home_ today (which wasn't even top of the line when I put
it together a few years ago) would have been considered almost
unimaginably powerful just a few decades ago.

-- 
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
                 “People who think they know everything really annoy
                 those of us who know we don’t.” (Bjarne Stroustrup)


  reply	other threads:[~2017-01-17 13:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11  2:33 Robert Swierczek
2017-01-11 16:25 ` Ron Natalie
2017-01-11 16:50   ` Jacob Goense
2017-01-11 17:01     ` Corey Lindsly
2017-01-11 17:54       ` Marc Rochkind
2017-01-11 20:32       ` Jacob Goense
2017-01-11 18:34 ` Steve Johnson
2017-01-11 19:46   ` Steffen Nurpmeso
2017-01-17 13:09   ` Tim Bradshaw
2017-01-17 13:36     ` Michael Kjörling [this message]
2017-01-17 19:55     ` Steve Johnson
2017-02-01 23:32       ` Erik E. Fair
2017-01-17 14:27 Nelson H. F. Beebe

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=20170117133632.GB12237@yeono.kjorling.se \
    --to=michael@kjorling.se \
    /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).