Re: 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> wrote:

On Sun, Mar 18, 2018 at 10:26 PM, Henrik Rützou <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
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.