×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The design of the Node.js event loop allows it to absolutely excel at
performance when it needs to process multiple things at once. For
example running a web server -- even if that web server needs to
maintain state -- is awesome in Node, nothing else can touch it.
It is versatile as well, able to do any sort of program, and the
language (JavaScript) is very elegant.
But, the design of the event loop does lead to added complexity when you
have to wait for external events, such as waiting for database or other
file access. In Node, you have to either deal with "callback hell"
(like you do in browser-based JavaScript) or resolving Promises...
though, honestly, once you get good at Promises they work very well. So
for multi-processing, its hard to beat.
On the other hand, Python is simpler because you don't have to worry
about Promises/Callbacks. It's a bit more clunky for web programming,
writing REST APIs, or other types of server code (unless the server is
very simple or low-volume) than Node.js, but for stuff like scripting
(similar to what you'd do in CL, REXX, bash scripts, etc) Python is
considerably easier.
They are both Open Source (no charge) and cross-platform (you can run it
on your existing PC, Mac, IBM i, Linux box, whatever) so you don't
really need to choose one or the other... just use what works best for
the application at hand.
On 8/3/2021 10:38 AM, midrangel@xxxxxxxxxxxxxxxxx wrote:
John Yeung Says: . "And frankly, it's not like Go is *so* much better than
Python or Node.js that the practical choice for someone who knows none of
the three is to pick Go and wait and hope."
I've gone down the Python route but not heavily enough that the decision is
final. So which of the choices has the most reasonable learning curve,
feature/function and most importantly longevity in the project?
--
Jim Oberholtzer
Agile Technology Architects
As an Amazon Associate we earn from qualifying purchases.