Skip to content

Instantly share code, notes, and snippets.

@jakecoffman
Last active July 5, 2017 18:55
Show Gist options
  • Save jakecoffman/09a82dc1b8c4ce44a5fe480cae6a2dd3 to your computer and use it in GitHub Desktop.
Save jakecoffman/09a82dc1b8c4ce44a5fe480cae6a2dd3 to your computer and use it in GitHub Desktop.
node good bad ugly

Bad

  1. can't trace uncaught rejections back to the calling code
  2. dependency hell, immature dependencies, forks on forks
  3. inconsistent use of promises, e.g. mongoose you need to remember .exec and it doesn't throw but returns null
  4. debugging is rough, end up console logging most of the time
  5. promises are confusing, you can avoid them for a while with async/await or co but eventually they will bite you

Good

  1. easy concurrency
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment