Hi Paul,
You said: "...JAVA is a good example of this. The mainframe's JAVA
runtime is written to exploit machine assists and hardware instructions
that a PC doesn't have..."
Every time I've watched mainframe Java since OS/90 V1, it has been
painfully slow. Have you ever watched a WAS startup? ... It takes about
15 minutes on the fastest mainframes.
Good thing it has assists, otherwise it might take 2 days Feh!
Regards,
David
On 2023-03-02 08:31, Paul Gorlinsky wrote:
After watching this chain for awhile I have a couple of observations:
1) Not all compilers are equal in their tasks especially in the optimization
area. Some are lazy and just convert the code to pseudo code and store it as an
executable to remove one layer of processing.
2) The selection of a computer language for a given task should be based upon:
A) Shop standards
B) Limitations imposed by the OS or OS components the task is to be
integrated with
C) The performance requirements, that is does this new widget run once a
day, hour,minute,second,etc.
D) Time constraints ... execution time as well as development time
D) The skill of the programmer
Understanding the PROS and CONS of each computer language is the key to a
successful project.
Note: that a benchmark run with different languages on a commodity computer (
AKA PC ) is NOT transferable to the mainframe. JAVA is a good example of this.
The mainframe's JAVA runtime is written to exploit machine assists and
hardware instructions that a PC doesn't have. For example, all the string
manipulation instructions.
IMHO
----------------------------------------------------------------------
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
