17 Jun
2026
17 Jun
'26
10:21 a.m.
On 17/06/2026 15:56, Bill Gunshannon via cctalk wrote:
On 6/17/2026 10:51 AM, Johan Helsingius via cctalk wrote:
Nothing, but we will disagree on defining its domain which I believe
must include hardware and software.
So if I am extending something written in COBOL on an IBM Mainframe or
Mid-range then yes, that Is the domain of COBOL.
For something thats going to run in the cloud with a web front end unlikely.
On 17/06/2026 4:49 pm, Bill Gunshannon via cctalk
wrote:
Other than the dearth of programmers, why not? What's wrong with the
language when the project is in its domain?
I came on the scene of a Honeywell to Univac-1100
migration 46 years
ago. Mostly COBOL a little Fortran and a tiny bit of other silly
stuff. Not only was there no thought of converting the COBOL to Ada
at the time but the last time I checked they are still running some
of the COBOL I wrote when I was there.
Sure, but would anyone starting a new software project choose
COBOL as the implementation language?
And, while we are on the subject. Does no one else
see the potential
for profit in teaching COBOL again? If no college wants to do it,
what about these trade schools we keep hearing about?
Not really. The issue with COBOL as I see it is that employers think
COBOL staff have no other skills, are desperate for work, so they can
pay 1950s rates.
Dave
G4UGM
bill
Dave