From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] unix "awesome list"
Date: Tue, 8 May 2018 12:32:00 -0400 [thread overview]
Message-ID: <CAC20D2MxJLPfwK3d149GAGFHfRCzpa=wa8CDK3SuKPMJS=C9wA@mail.gmail.com> (raw)
In-Reply-To: <146d3e969e94918e80c3d7dae01f0a839968e6bb@webmail.yaccman.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1824 bytes --]
On Tue, May 8, 2018 at 11:31 AM, Steve Johnson <scj at yaccman.com> wrote:
> Well, as I look to the future I see the whole approach we have to software
> running into a dead end. In fact, I think software is holding us back.
>
You might be right here, but where we disagree I think is economics. The
problem is that we can not afford to replace SW. As I like to point out,
Fortran still pays my salary -- why because all the data and codes that use
that data written since the late 1950s.
Its just worse in the commercial side. Word and Lookout/Exchange sucks -
but people use them and they are not going away. Think about the LISP
Machine or the CM1 - lots of people though they were 'better' for some
concept of goodness. But they failed in the end.
>
> ...
>
> Starting about 2000, this changed. Hardware was no longer offering
> increased speed. But what it was offering was massive parallelism. The
> response was to cling to the one instruction at a time model, introducing
> multicore and its attendant hardware complexity to try to cling to the
> previous model of programming. The hardware to make this possible is
> expensive and does not scale.
>
I agree but ... IMO its going to take a real Christensen disruption with a
new customer base. I just don't see that happening any time soon.
Without a new customer base to support the new technology, the economics
of the keeping the old running has and will continue to go forward.
>
> And it's exciting...
>
I agree and I'm a fan and cheering from the sidelines .... but I'm
skeptical of success because the economics don't play to success..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180508/facfc5f5/attachment-0001.html>
next prev parent reply other threads:[~2018-05-08 16:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 18:22 A. P. Garcia
2018-05-07 21:10 ` Dave Horsfall
2018-05-07 21:53 ` Steve Johnson
2018-05-08 12:24 ` Theodore Y. Ts'o
2018-05-08 13:51 ` Bakul Shah
2018-05-08 14:53 ` Clem Cole
2018-05-08 15:23 ` Jon Steinhart
2018-05-08 15:31 ` Steve Johnson
2018-05-08 16:32 ` Clem Cole [this message]
2018-05-08 17:33 ` Theodore Y. Ts'o
2018-05-08 18:40 ` William Cheswick
2018-05-08 21:25 ` Bakul Shah
2018-05-08 23:06 ` [TUHS] (early parallel/concurrent computing) (was: unix "awesome list") Lyndon Nerenberg
2018-05-09 0:25 ` Ron Natalie
2018-05-09 1:28 ` Kurt H Maier
2018-05-08 21:15 ` [TUHS] unix "awesome list" Bakul Shah
2018-05-08 16:31 ` Michael Parson
2018-05-08 17:20 ` Larry McVoy
2018-05-08 17:49 ` Michael Parson
2018-05-08 20:48 ` Dave Horsfall
2018-05-08 17:53 ` Theodore Y. Ts'o
2018-05-07 21:54 ` Steve Nickolas
2018-05-08 8:14 ` Mutiny
2018-05-07 22:34 ` Andy Kosela
2018-05-08 15:17 Noel Chiappa
2018-05-08 15:22 ` Warner Losh
2018-05-08 16:18 ` Arthur Krewat
2018-05-08 19:37 ` Dave Horsfall
2018-05-08 19:54 ` Grant Taylor
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='CAC20D2MxJLPfwK3d149GAGFHfRCzpa=wa8CDK3SuKPMJS=C9wA@mail.gmail.com' \
--to=clemc@ccc.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).