|
On Jan 25, 2017, at 3:18 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:
On Wed, Jan 25, 2017 at 1:22 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
I think there is one big difference John. With PHP Zend have already built and included many of the add on components that are needed into the IBM i base. With Python you seem to always have to get hold of those "extra" things and install them yourself. I have started using Python, but have been slowed down by encountering similar dependencies to the ones Paul has encountered. That has never yet happened to me with PHP.
I agree that IBM, if they're serious about (pick whatever technology),
should be providing more of the libraries which do not have an
automated installation process on the i, or partnering with someone
who can. In the case of most dynamic languages, that means stuff that
is compiled to native machine code rather than to the dynamic
language's runtime.
So yes, PHP does have a leg up on the i because Zend did a lot of the
work. But it's also not free. I keep forgetting that part, because the
PHP language itself is, ostensibly, open source and free.
There are relatively few "linchpin" Python libraries that must be
compiled to native code, but these are dependencies for huge numbers
of other libraries (which I believe contributes to the sense on the i
that Python is always missing something). In particular, IBM really
should bite the bullet and build NumPy for PASE already. That would
open up a ton of Python applications, some of which I doubt PHP has
any near equivalent. Another major area that needs native code is
encryption/security/SSL/SSH. It's tough to talk to the Web these days
without secure connections (understandably so). I'm not sure how many
C libraries that involves, but it can't be more than a handful, and
again, that would open up a ton of applications.
As a small aside, iSeriesPython does come with an ILE-compiled crypto
package, which means out of the box it can use some libraries that
IBM's Python for PASE can't.
John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.