errors-in-js.js

// try-catch style
// 
// Advantages: 
// 1. Familiar to OOP developers
// 2. Explicit error-handling code not required
// 3. Works well with async-await syntax
// 
// Disadvantages:
// 1. Inefficient
// 2. Explicit error-handling code not required
// 
const f = () => {
  throw new Error('Something has gone wrong. ');
};

try {
  f(); 
} catch (error) {
  console.error(error); 
}

// callback style
// 
// Advantages: 
// 1. Familiar to JavaScript developers
// 2. Explicit error-handling code is required
// 
// Disadvantages:
// 1. Pyramid-of-doom / callback-hell
// 2. Explicit error-handling code is required
// 3. Does not work well with async-await syntax
// 
const f = (callback) => {
  callback(new Error('Something has gone wrong. '), null);
};

f((error, result) => {
  if (error) {
    console.error(error);
  }
});

// functional-programming style
// 
// Advantages: 
// 1. Familiar to FP & Go developers 
// 2. Explicit error-handling code is required 
// 3. Works well with gradual type-systems 
// 4. Works well with async-await syntax 
// 5. Efficient 
// 6. Encourages purity
// 
// Disadvantages:
// 1. Explicit error-handling code is required 
// 2. Can be unfamiliar to OOP developers 
// 
const f = () => {
  return {
    error: new Error('Something has gone wrong. '), 
    result: null
  };
};

const { error, result } = f();

if (error) {
  console.error(error); 
}