From: crossd at gmail.com (Dan Cross)
Subject: [COFF] COBOL.
Date: Mon, 13 Apr 2020 15:30:09 -0400 [thread overview]
Message-ID: <CAEoi9W7y2osOt4aiGScWgMo65p8wRE6cVQ_KpsMS+nRo8qW+tA@mail.gmail.com> (raw)
In-Reply-To: <71a36ea4-236e-4b87-b973-912491ed2d36@localhost>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Mon, Apr 13, 2020 at 2:16 PM Michael Kjörling <michael at kjorling.se>
wrote:
> On 13 Apr 2020 13:59 -0400, from crossd at gmail.com (Dan Cross):
> > I read an estimate somewhere that there are something like 380 billion
> > lines of COBOL out there, and another 5 billion are written annually
> > (mostly by body shops in the BRIC countries?). That's a lot of code;
> surely
> > not all of it is good.
>
> Ars quotes an IBM press release claiming 220 billion LOC "being
> actively used today", at <
> https://arstechnica.com/tech-policy/2020/04/ibm-scrambles-to-find-or-train-more-cobol-programmers-to-help-states/
> >.
>
Sadly (??) that number seems to come from a 2009 estimate. I'm not sure of
the veracity of the 390BLOC number, though.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200413/0951448c/attachment.html>
next prev parent reply other threads:[~2020-04-13 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 17:59 crossd
2020-04-13 18:09 `
2020-04-13 19:30 ` crossd [this message]
2020-04-13 22:22 ` krewat
2020-04-13 20:40 ` clemc
2020-04-13 21:27 ` thomas.paulsen
2020-04-13 22:24 ` dave
2020-04-13 22:28 ` lm
2020-04-13 23:58 ` clemc
2020-04-14 9:24 ` skogtun
2020-04-14 10:06 ` dave
2020-04-14 8:18 ` wobblygong
2020-04-14 16:11 ` cym224
2020-04-15 6:58 ` thomas.paulsen
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=CAEoi9W7y2osOt4aiGScWgMo65p8wRE6cVQ_KpsMS+nRo8qW+tA@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).