Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] Old and Tradition was [TUHS] V9 shell
Date: Tue, 11 Feb 2020 13:41:01 -0500	[thread overview]
Message-ID: <CAC20D2NJSKUwZJFaATht=FmnyYTBZ5Tqhb3h+nRaCvptNu=XdA@mail.gmail.com> (raw)

moving to COFF

On Tue, Feb 11, 2020 at 5:00 AM Rob Pike <robpike at gmail.com> wrote:

> My general mood about the current standard way of nerd working is how
> unimaginative and old-fashioned it feels.
>
...
>
> But I'm a grumpy old man and getting far off topic. Warren should cry,
> "enough!".
>
> -rob
>

@Rob - I hear you and I'm sure there is a solid amount of wisdom in your
words.   But I caution that just, because something is old-fashioned, does
not necessarily make it wrong (much less bad).

I ask you to take a look at the Archer statistics of code running in
production (Archer large HPC site in Europe):
http://archer.ac.uk/status/codes/

I think there are similar stats available for places like CERN, LRZ, and of
the US labs, but I know of these so I point to them.

Please note that Fortran is #1 (about 80%) followed by C @ about 10%, C++ @
8%, Python @ 1% and all the others at 1%.

Why is that?   The math has not changed ... and open up any of those codes
and what do you see:  solving systems of differential equations with linear
algebra.   It's the same math my did by hand as a 'computer' in the 1950s.

There is not 'tensor flows' or ML searches running SPARK in there.  Sorry,
Google/AWS et al.   Nothing 'modern' and fresh -- just solid simple science
being done by scientists who don't care about the computer or sexy new
computer languages.

IIRC, you trained as a physicist, I think you understand their thinking.  *They
care about getting their science done.*

By the way, a related thought comes from a good friend of mine from college
who used to be the Chief Metallurgist for the US Gov (NIST in Colorado).
He's back in the private sector now (because he could not stomach current
American politics), but he made an important observation/comment to me a
couple of years ago.  They have 60+ years of metallurgical data that has
and his peeps have been using with known Fortran codes.   If we gave him
new versions of those analytical programs now in your favorite new HLL -
pick one - your Go (which I love), C++ (which I loath), DPC++, Rust, Python
- whatever, the scientists would have to reconfirm previous results.  They
are not going to do that.  It's not economical.   They 'know' how the data
works, the types of errors they have, how the programs behave* etc*.

So to me, the bottom line is just because it's old fashioned does not make
it bad.  I don't want to write an OS in Fortran-2018, but I can wrote a
system that supports code compiled with my sexy new Fortran-2018 compiler.

That is to say, the challenge for >>me<< is to build him a new
supercomputer that can run those codes for him and not change what they are
doing and have them scale to 1M nodes *etc*..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200211/5fd66145/attachment.html>


             reply	other threads:[~2020-02-11 18:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 18:41 clemc [this message]
     [not found] ` <CAP2nic2C4-m_Epcx7rbW2ssbS850ZFiLKiL+hg1Wxbcwoaa1vQ@mail.gmail.com>
2020-02-12  0:57   ` [COFF] Fwd: " athornton
2020-02-12  1:58     ` clemc
2020-02-12  3:01       ` lm
2020-02-12 18:12         ` clemc
2020-02-12 21:55           ` cym224
2020-02-12 22:11           ` imp
2020-02-12 22:45             ` sauer
2020-02-12 23:05               ` lm
2020-02-12 23:54                 ` [COFF] floating point (Re: " bakul
2020-02-12 23:56                   ` bakul
2020-02-13  1:21                   ` toby
2020-02-13  6:57             ` [COFF] Fwd: " peter
2020-02-16 21:47           ` wobblygong
2020-02-16 22:10             ` clemc
2020-02-16 22:45               ` krewat
2020-02-16 23:50               ` bakul
2020-02-18  0:17                 ` dave
2020-02-18 12:48                   ` jpl.jpl
2020-02-24  9:40         ` ik
2020-02-24 15:19           ` lm
     [not found]             ` <CAP2nic0fK+=eh=5MuY4BJH6zx4tCRMWcazmm1khYMzNmEdf8ug@mail.gmail.com>
2020-02-24 16:15               ` [COFF] [TUHS] Fwd: Old and Tradition was " clemc
2020-02-24 16:19                 ` clemc
2020-02-24 16:27             ` [COFF] Fwd: Old and Tradition was [TUHS] " clemc

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='CAC20D2NJSKUwZJFaATht=FmnyYTBZ5Tqhb3h+nRaCvptNu=XdA@mail.gmail.com' \
    --to=coff@minnie.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).