Re: Express, React, Node.JS

Richard

but Aaron's example is maybe a little "overdoing" await because await comes
with a performance penalty.

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virusfri.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sat, Feb 24, 2018 at 7:08 PM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

Nice.

Essentially synchronous without blocking ?

Regards,

Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com

----------------------------------------------------------------------

message: 1
date: Sat, 24 Feb 2018 07:48:05 -0600
from: Aaron Bartell <aaronbartell@xxxxxxxxx>
subject: Re: [WEB400] Express, React, Node.JS

make Node development more procedural for developers ?

With Node.js v8.x there is the introduction of async/await. Here's an
example of how that makes things significantly simpler and brings
procedural appearances: http://bit.ly/2BOttaP

Aaron Bartell
IBM i hosting, starting at $157/month. litmis.com/spaces



--
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.