Funny how all these articles make me think that lambda/closures are a very very nice syntax to create linguistic friendly structure. Automatically embedding of lexical scope avoid unnecessary names, assignments and side effects. Similarly to this talk https://news.ycombinator.com/item?id=3717715 where the author demonstrates how often we write classes with a bit of state, a constructor, and a single method [1].. which is a what a function does for us.

Some programming classes takes some time to describe this habit of unnecessary wrapping[2]. From

    ```
    if bool_var then true else false
    ```

, to theses functions-written-as-classes, or even, depending on the language you use, function that wraps other functions disguised as operators

    ```
    map(function add(x, y) { return x + y }, list)
    // aka `map + list` in deeply functional languages
    ```

[1] Java had many single method interfaces that can now be replaced by lambdas

[2] see Dan Grossman proglang on Coursera (taken from his original classes at UoWashington)