you can have a single language syntax for both your front and backends.


Last night I spent a couple hours reviewing content in various Node.js
tutorials on the Internet and felt quite at ease, due mostly to my
experience with JavaScript in the browser.

Even concepts like registering events with references to call-back
functions in connection with asynchronous I/O was familiar due to my prior
use of AJAX.

But even if you were to use JavaScript for both front-end and back-end
development, I still think is makes most sense to have a node.js back-end
evoke RPG code, perhaps through stored procedures or triggers or services
waiting on the other side of a data queue.

And the support for native interfaces in node.js for i is what makes it
even more appealing to me.

Nathan.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.