El 2024-03-19 02:40, David Crayford escribió:
On 19 Mar 2024, at 9:08 am, Andrew Rowley
<[email protected]> wrote:
On 19/03/2024 11:05 am, David Crayford wrote:
If you’re care so much about Java catching errors at compile time
then why don’t you use Kotlin instead? NPE’s are one of the most
common form of Java runtime errors that can be eliminated using
Kotlins null safety.
Java's not perfect, but it is powerful and it is pretty much
universally available on z/OS. I'm writing functions for others to
build on e.g.:
https://static.blackhillsoftware.com/easysmf-rti/javadoc/com.blackhillsoftware.smf.realtime/com/blackhillsoftware/smf/realtime/package-summary.html
So using/targeting the language that is most available makes sense.
But my question was: Why Python? What are the reasons for using Python
rather than e.g. Java?
Though the conversation initially compared REXX to Python, it's clear
they are fundamentally different beasts and different ends of the
spectrum. Python is a powerful and widely-used programming language
with applications across various industries. It underpins critical
systems like the backend of Instagram's photo-sharing platform, and is
utilized by major players such as Tesla, Spotify, Uber, Amazon, NASA,
Netflix, and Facebook. Notably, IBM is investing in Python for z/OS,
with the ability to run on a zIIP with a 70% generosity factor and
libraries facilitating integration with RACF, enabling the use of RACF
keyrings with micro web frameworks like Flask. Certainly, IBM's
investment in Java is crucial for the future sustainability of z/OS.
On the other hand, REXX is likely supported as cheaply as possible by
a very small team, along with TSO.
David,
Do you have more details about the enabling of RACF keyrings in Python?
We are developing a Flask webapp and that would be fantastic.
Thanks!
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
