The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: [TUHS] Questions for TUHS great minds
Date: Wed, 11 Jan 2017 20:46:50 +0100	[thread overview]
Message-ID: <20170111194650.pIbRmaw3g%steffen@sdaoden.eu> (raw)
In-Reply-To: <99f1301695eb38762765b91bff57b0486bc71af6@webmail.yaccman.com>

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

Hello.

"Steve Johnson" <scj at yaccman.com> wrote:
 |>>  Or does the idea of a single OS disintegrate into a fractal cloud \
 |>>of zero-cost VM's?  What would a meta-OS need to manage that?  Would \
 |>>we still 
 |recognize it as a Unix?
 |
 |This may be off topic, but the aim of studying history is to avoid \
 |the mistakes of the past.  And part of that is being honest about where \
 |we are now...
 |
 |IMHO, hardware has left software in the dust.  I figured out that if \
 |cars had evolved since 1970 at the same rate as computer memory, we \
 |could now buy 1,
 |000 Tesla Model S's for a penny, and each would have a top speed of \
 |60,000 MPH.  This is roughly a factor of a trillion in less than 50 years.

I am even more off-topic, and of course this was only an example.
But this reference sounds so positive, yet this really is no
forward technology that you quote, touring along several hundred
kilogram of batteries that is.

Already at the end of the eighties i think (the usual
")everybody(") knew that fuel cells are the future.  It is true
that i have said in a local auditorium in 1993 that i wished with
18 everybody would get a underfloor with fuel cells in the
sandwich that it is, and four wheel hub motors, and a minimalistic
structure that one may replace at will.

It was already possible back then (but for superior tightness of
the tank), just like, for example, selective cylindre
deactivation, diesel soot filter, diesel NOx reduction cat ("urea
injection").  (Trying to clean Diesel in the uncertain conditions
that multi-million engines at different heights and climate are in
is megalomaniacal, in my opinion.  And that already back then.)

Unfortunately fuel cell development has never been politically
pushed as much as desirable, and was mostly up to universities
until at least about 2006, and in Germany, to the best of my
knowledge.  It may not be popular in the U.S. at the moment, but
it is Toyota again, with the Mirai, who spends money due to
responsibility.  That is at least what i think.  (And again it is
the question whether a doubtful technology is spread millions and
millions of times all over the place, or whether only some
refineries have to be improved.)

--steffen


  reply	other threads:[~2017-01-11 19:46 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 [this message]
2017-01-17 13:09   ` Tim Bradshaw
2017-01-17 13:36     ` Michael Kjörling
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=20170111194650.pIbRmaw3g%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    /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).