From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Request new Ruby release
Date: Sat, 05 May 2018 03:41:00 -0000 [thread overview]
Message-ID: <d41360e8-0bac-e813-3868-6f3595074ce3@SystematicSw.ab.ca> (raw)
In-Reply-To: <5aed015b.1c69fb81.6a87b.524b@mx.google.com>
On 2018-05-04 18:56, Steven Penny wrote:
> sorry, did you really just invoke fortran as a serious argument? fortran is
> arguably the oldest programming language still in use, if you can even call it
> that. you can't even do HTTP with it:
> http://rosettacode.org/wiki/HTTPS#Fortran
That's what web servers are for, written in more suitable languages, but search
for fortran+fastcgi+nginx, or have a look at https://github.com/rlcarino/heeds
for a production GPL3 web based Fortran app.
> youll notice that ADA already got the axe:
> http://github.com/cygwinports/cygwin64-gcc/blob/master/cygwin64-gcc.cygport#L52
On Cygwin, but GNAT is still part of GCC 9.
ADA is heavily used in safety critical, RT, embedded avionics and ATC where the
focus is on decades long, exhaustive documentation archival, maintenance,
support, and testing of almost static libraries and tools after release,
requirements for which GNU projects are ill-suited, but in which aerospace and
gov/mil project companies and their suppliers have long experience.
Cobol has similar requirements for bread and butter enterprise and government
financial systems, with high requirements for maintainability to handle
legislative and business changes, and long term platform compatibility and support.
> this could happen to fortran as well.
I thought I'd have seen that by now, but there's too much carefully validated
(parallel) HPC (especially modelling) and scientific code, libraries, apps, and
systems used by various government agencies, institutions, and departments for
heavy or important computation in many fields, that it doesn't look like it'll
ever be allowed to die ;^>
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-05-05 3:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 20:51 Steven Penny
2018-05-03 23:17 ` Steven Penny
2018-05-04 3:09 ` Yaakov Selkowitz
2018-05-04 6:05 ` Brian Inglis
2018-05-04 12:09 ` Steven Penny
2018-05-04 13:16 ` Marco Atzeri
2018-05-05 0:57 ` Steven Penny
2018-05-05 3:41 ` Brian Inglis [this message]
2018-05-05 5:27 ` Marco Atzeri
2018-05-05 6:56 ` Steven Penny
2018-05-05 16:18 ` Stephen John Smoogen
2018-05-06 5:54 ` Yaakov Selkowitz
2018-05-06 14:08 ` Steven Penny
2018-05-14 16:10 ` cyg Simple
2018-05-15 4:17 ` Steven Penny
2018-05-15 13:27 ` What is Cygwin and MinGW [WAS: Request new Ruby release] cyg Simple
2018-05-15 14:37 ` Request new Ruby release Adam Dinwoodie
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=d41360e8-0bac-e813-3868-6f3595074ce3@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).