Re: [EXTERNAL] Re: Rise of Node

Henrik,

Being a newbie, I am curious. Why would I want to use Node if I’m not leveraging the event loop with asynchronous programming? I understand in theory that I could have an instance of the event loop running that processes a batch script instead of handing it off to worker threads. But that why would I want to do that? I’m genuinely curious since I’m still learning and this may be a failure of my imagination.

Thanks,

Kelly Cookson
IT Project Leader
Dot Foods, Inc.
217-773-4486 ext. 12676
www.dotfoods.com<http://www.dotfoods.com>

From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Henrik Rützou
Sent: Monday, March 19, 2018 11:06 AM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [WEB400] Rise of Node

Nathan,

you don't have to code async if there is no need for that - a simple batch
process
that runs in its own instance hasn't other to compete with (so why async?)-
so you
code that sync - exactly as you are used to.

be aware of that nearly all async functions in node has a sync counterpart

const fs = require("fs")
fs.readFile <> fs.readFileSync
fs.writeFile <> fs.writeFileSync etc.

And BL also seems to be a big issue - what instructions has RPG to offer
that
javascript hasn't? Most BL is ADD, SUB, MULT or DIV anyway.



On Mon, Mar 19, 2018 at 4:13 PM, Nathan Andelin <nandelin@xxxxxxxxx<mailto:nandelin@xxxxxxxxx>> wrote:

On Sun, Mar 18, 2018 at 10:26 PM, Henrik Rützou <hr@xxxxxxxxxxxx<mailto:hr@xxxxxxxxxxxx>> wrote:

Nathan you are wrong, your statement should be await ...

While I appreciate the syntax improvement offered by asynchronous functions
and await blocks, that wasn't my point. That syntax is only available
recently. And callbacks are still occurring under the covers. My point was
that the event-loop architecture is poorly suited for the implementation of
data validation, business rules, and other functional requirements of
business applications.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx<mailto:WEB400@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400<https://lists.midrange.com/mailman/listinfo/web400>
or email: WEB400-request@xxxxxxxxxxxx<mailto:WEB400-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400<https://archive.midrange.com/web400>.

--
Regards,
Henrik Rützou

http://powerEXT.org<http://powerEXT.org> <http://powerext.org/<http://powerext.org/>>
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx<mailto:WEB400@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400<https://lists.midrange.com/mailman/listinfo/web400>
or email: WEB400-request@xxxxxxxxxxxx<mailto:WEB400-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400<https://archive.midrange.com/web400>.