Hi Jon,
In one paragraph, you're talking about application code. In another
paragraph, you're discussing system-level programming.
My argument has nothing to do with application code; I've always
maintained that application code should be written in a High Level Language.
As to your second paragraph, those of us who work in the real world (I
used to work at IBM) don't have the luxury of Internal Use Only software
tools.
Your argument is very weak tea.
Regards,
David
On 2023-09-12 08:04, Jon Butler wrote:
There will be a need for assembler programmers for quite a while, but mainly
because over the last forty years, and long after even COBOL II added functions
and a case construction in 1987, very, very clever people decided they would
write application modules in assembler... and not waste time with comments.
Today, when companies are trying to make their systems Highly Available...or
even convert to a cloud provider's service...no one has a clue what the modules
do. Many could have been easily replaced by COBOL's ADDRESS OF or LENGTH OF or
PL/I Pointers, but of course that would have been way too easy. Very few
application programs need to control channels.
When I was interviewed by the Db2 Utilities group at the Santa Teresa lab in San Jose
(Now Silicon Valley) in 2001, I said I suppose I needed to brush up on my assembler.
They laughed and said "no one uses assembler any more." All the Utilities were
written in PL/S, now PL/X.
Not to denigrate assembler programmers, or those that decide to take up
Sanskrit, but it is a dying art.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
