Help me out if I'm missing something important, but this doesn't really seem to add much except for the conceptual overhead of another control structure. The e

Help me out if I'm missing something important, but this doesn't really seem to add much except for the conceptual overhead of another control structure. The examples given in the article are as clear or clearer without the do syntax. Compare: [1, -1, -0.5].map(x => do { if (x > 0) { x * 10 } else { -x * 10 } }) to [1, -1, -0.5].map(x => { if (x > 0) { return x * 10 } else { return -x * 10 } }) as well as var data = do { const data = pullSomeData() doSomethingElse() // sideEffect data } versus const data = pullSomeData() // or `var` if you wish doSomethingElse() // sideEffect Perhaps a more significant example is warranted here. My suspicion is that if you get code complicated enough to justify a `do` block, it's complicated enough to justify a function that can be independently tested.