While maintaining some code recently I found myself writing out of pure habit Object.hasOwnProperty.call(obj, 'prop') as is expected in almost all OSS I've contributed to, and quickly editing that to just !!obj.prop which I chose because it worked more succinctly in my use case but I
We know the Node.js engine runs our code asynchronously, and we know it does that using an event loop. When Node.js is used to handle web requests it is capable of managing them over each CPU available via its cluster functionality achieving incredible performance over rival server-side languages.
This new release of node aims to improve performance, reliability, usability and security. Node 6.0 supports 93% of ES6 features. > Only 6 months after Node Foundation announced version 5.0 Announcement can be found here; https://nodejs.org/en/blog/release/v6.0.0/ Support for older versions LTS
The WRONG Way There is always a exceptionally bad way of doing something in NodeJS (or any language) so I figured covering this will put perspective on the alternatives. Listening for uncaughtException Listening for events on the global process variable is easy, and this is likely why we see this
Purpose and use case Generally your functions are executed asynchronously with some exceptions, and the challenge for some is when you have a piece of code that can not be executed until previous functions are complete or data is returned. > So then why exactly would you want to process functions
