To be honest I haven't delved into the reasons much, only repeating what
I've heard.

Another question would be whether it is based on how well the processor and
OS do calculation intensive processing. Node.js is new to IBM i and also
fairly new to PowerLinux**, so maybe IBM i does it worse (better?)

**https://github.com/andrewlow/v8ppc

And for that matter, do we really do anything on IBM i that is calculation
intensive? Note we're not talking about an inventory bill-of-materials and
instead, I believe, scientific computation.

Aaron Bartell
litmis.com - Open Source and IBM i. No Limits.


On Fri, Aug 28, 2015 at 11:06 AM, Kevin Turner <
kevin.turner@xxxxxxxxxxxxxxxxxxxx> wrote:

"For example, it's been documented that Node.js shouldn't be used for
calculation intensive applications."

I wonder why. The only thing I have seen on this still boils down to the
impact long calcs have on the event loop - but if you are delegating to a
child process then it has no impact, and JavaScript is pretty powerful for
calcs isn't it?


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].