The C/C++ compiler runs in PASE.

The really good-performance Java now runs in PASE.

IBM is running a number of things in PASE, and not everything is doing poorly there.


On 4/8/2013 10:34 AM, John Yeung wrote:
On Mon, Apr 8, 2013 at 11:05 AM, <rob@xxxxxxxxx> wrote:
I've been burnt on stuff migrated from native to pase. Went from
performing reasonably well to abysmal. I'd hate to see more stuff plugged
that way with the myth that "write once, run anywhere".
My admittedly limited experience with PASE has also been that
performance was far worse than in the native environment. So many
people recommend PASE, though, so perhaps things have gotten better
lately. Either that, or everyone has such big, powerful boxes now
that even "several times slower than native" is still "twice as fast
as native on our old AS/400".

One of the attractive things for me about iSeriesPython is that it's
native, not a PASE version of Python. Yet it lets me use "mainstream"
Python packages. And it effortlessly accesses both QSYS objects
(including programs) and IFS stream files.

Also keeping in mind that javascript is not java anymore than HTTP is
Domino (even though the lpp got renamed DG1 for Domino Go). My
understanding (which may be flawed) is that javascript is solely intended
to be consumed by a browser.
If you're referring to a comment by Steve about garbage collection, I
think he's not saying that JavaScript is related to Java, just that
both happen to be garbage collected.

JavaScript is both a browser language and a server-side language. It
happens to be particularly popular in the browser because all browsers
support it, and because browsers are not guaranteed to support
anything else. On the server, there are a lot more choices. Python
and Perl in particular are strong competitors to JavaScript because
they are comparably powerful, arguably nicer to program in, and come
standard on any Linux or Unix you are likely to encounter.


This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page