Pinned

1. airbnb/javascript

   JavaScript Style Guide

   JavaScript 102k 19.8k

2. nvm-sh/nvm

   Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions

   Shell 45.4k 4.5k

3. es-shims/es5-shim

   ECMAScript 5 compatibility shims for legacy (and modern) JavaScript engines

   JavaScript 7k 945

4. qs

   A querystring parser with nesting support

   JavaScript 5.7k 550

5. tc39/proposals

   Tracking ECMAScript Proposals

   12.1k 484

6. Array iteration methods summarized

   1

   While attempting to explain JavaScript's `reduce` method on arrays, conceptually, I came up with the following - hopefully it's helpful; happy to tweak it if anyone has suggestions.

   2

   3

   ## Intro

   4

   JavaScript Arrays have lots of built in methods on their prototype. Some of them *mutate* - ie, they change the underlying array in-place. Luckily, most of them do not - they instead return an entirely distinct array. Since arrays are conceptually a contiguous list of items, it helps code clarity and maintainability a lot to be able to operate on them in a "functional" way. (I'll also insist on referring to an array as a "list" - although in some languages, `List` is a native data type, in JS and this post, I'm referring to the concept. Everywhere I use the word "list" you can assume I'm talking about a JS Array) This means, to perform a single operation on the list as a whole ("atomically"), and to return a *new* list - thus making it much simpler to think about both the old list and the new one, what they contain, and what happened during the operation.

   5