Error Handling in Node.js
Some of this looks like horrible advice, particularly the defeatist attitude towards what the article calls &quot;programmer errors&quot;. Statements to the effect that you can never anticipate or handle a logic error sensibly so the only thing you should ever do is crash immediately are hard to take seriously in 2016. What about auto-saving recovery data first? Logging diagnostic information? Restarting essential services in embedded systems with limited interactivity? This article basically dismisses decades of lessons learned in defensive programming with an argument about as sophisticated as &quot;It&#x27;s too hard, we should all just give up&quot;.<p>As others have already mentioned, much of the rest is quite specific to Node&#x2F;JS, and many of the issues raised there could alternatively be solved by simply choosing a better programming language and tools. The degree to which JS has overcomplicated some of these issues is mind-boggling.