> Am 08.07.2022 um 17:10 schrieb Colin Paice <[email protected]>:
> 
> I was told
> If it executes
> 
>   1. a million times a second - write in assembler
>   2. a thousand times a second write it in cobol or C
>   3. once a second - write it in Java
>   4. Else /bash/rexx/
> 
> Though if it executes once a year and runs for a week- I might look at C

As intriguing - and easy to memorize! - such listings are, they may quickly 
become totally misleading. E.g. Java has become able to run as quick as C/C++ 
and sometimes even faster than C/C++! 

One aspect that should be stressed in this context: given the ever ongoing 
improvements in hardware and software infrastructures benchmarks - if deemed 
important nowadays :) - need to be redone on a regular (yearly) basis. 

One interesting - REXX-related - table about speed improvements of different 
REXX/Rexx implementations over the decades can be found at the website of the 
father of REXX - Mike F. Cowlishaw - at: 
http://speleotrove.com/misc/rexxcpslist.html

Looking at these numbers (I do not know of any comparable historical table for 
other programming languages using the same benchmark program throughout the 
decades on different implementations of a language) one can see how 
breathtaking the technical improvements have been over the decades: going from 
114 RexxCPS in 1994 to 23,774,392 (!) RexxCPS in 2021.  So in 2021 Rexx 
programs would execute roughly 220,000 times (!) faster than in 1994!

—-rony 



>> On Fri, 8 Jul 2022 at 15:52, Dave Jones <[email protected]> wrote:
>> 
>> Timothy Sipples said:
>> 
>> "Which leads to an interesting thought exercise. In 2022 if you're trying
>> to choose a programming language for business application programming that
>> stands the best chance of being durable (being realistically maintainable,
>> extendable, enhance-able) for the next 40+ years — a common requirement for
>> many high value, nontrivial business applications — what programming
>> language would you choose? I suggest Enterprise COBOL ought to be a
>> candidate. (Any other nominations?)"
>> 
>> Enterprise PL/I, of course. :-)
>> DJ
>> 
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>> 
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to