Skip to content
working on that thing you asked about
working on that thing you asked about


@phamtec @christophehurpeau @StandardResumeSponsors @AdrienGiboire @maraisr @dshaw @OussamaRomdhane @Jtalk @shawnharmsen @smcelhinney @6ewis @wuweiweiwu @chrisJohn404


@Vets-Who-Code @eslint @PeterDaveHello @tatianamac @sdras @vaidehijoshi @nzakas @gr2m @lynncyrin @zkat @hzoo


  1. JavaScript Style Guide

    JavaScript 97.6k 19k

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

    Shell 42.8k 4.2k

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

    JavaScript 6.9k 935

  4. A querystring parser with nesting support

    JavaScript 5.4k 496

  5. Tracking ECMAScript Proposals

    11.1k 447

  6. 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.
    ## Intro
    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.

Contribution activity

July 2020

Seeing something unexpected? Take a look at the GitHub profile guide.

You can’t perform that action at this time.