The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Cág <ca6c@bitmessage.ch>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Commercial UNIX was other stuff before
Date: Sun, 3 Feb 2019 17:20:59 -0500	[thread overview]
Message-ID: <CAC20D2PXkg-rKkfPHOK0yAdomKZvOdSGAGFvrUfLf9fgyTZmig@mail.gmail.com> (raw)
In-Reply-To: <ca1f283401a52e7edd7a473174a500d5@bitmessage.ch>

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

On Sun, Feb 3, 2019 at 4:10 PM Cág <ca6c@bitmessage.ch> wrote:

> I wish I could say that.  I feel like nobody needs Fortran anymore, and
> my skills are being wasted.
>
FYI - the last time I saw the numbers, about 75-85% of the production at
CERN was Fortran.  This is very similar to the USA's high energy labs.  I
have not seen the numbers of the Darmstadt European space folks, but I
would not be surprised if they are much different than NASA's.   That was a
little lower, but the heavy supercomputer codes NASA uses are still very
much Fortran dominate.

Finding good Fortran programmers can be difficult.  Most today are from the
natural sciences (like was true in the 50s before we created 'Computer
Science'), but there are still lots of jobs if you know it.  But I suspect
that those jobs are going to be near campuses that support heavy science
types.
ᐧ

[-- Attachment #2: Type: text/html, Size: 1857 bytes --]

  reply	other threads:[~2019-02-03 22:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 20:58 Clem Cole
2019-02-03 21:08 ` Cág
2019-02-03 22:20   ` Clem Cole [this message]
2019-02-04  9:33     ` Marcus MERIGHI
2019-02-04 12:32       ` Steffen Nurpmeso
2019-02-03 21:17 ` Larry McVoy
2019-02-03 22:14 ` Henry Bent
2019-02-03 22:23   ` Clem Cole
2019-02-04  2:16     ` Paul Winalski

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=CAC20D2PXkg-rKkfPHOK0yAdomKZvOdSGAGFvrUfLf9fgyTZmig@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=ca6c@bitmessage.ch \
    --cc=tuhs@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).