Locality and Wasasbi

description.md

Fine, so we have the following code

    Routes.get("/customer',
           basicAuthentication
           {
               log.write("Inline logging dude")
               next()
           },
           {
               response.send(customer)
           }
    )

It's very pretty, I like the way that these blocks fall off each other. Let's compare it to

     app.get('/customer',
           basicAuthentication,
           function(req, res, next) {
             log.write("Logging")
             next()
           },
           function(req, res) {
             res.send(customer)
           }
     )

What's the difference? Well for my money, I prefer the latter because I have req, res and next completely local to the function that is handling that particular step.

Sticking them as "members of the container class" doesn't give you a clear indication of scope or intent, they're further away from the real action and make the code slightly more opaque when you're skimming it over in a monday morning tweet.

Indidentally is this one of the reasons I'm not enjoying Ruby/Rails - lots of methods are springing into existence in the global scope "because", "magic", I prefer the explicit and the local over the magic and distant.

I'm not a fan of the JS frameworks either, I prefer the modules which return a single function and have that function documented - I don't have a problem with having to look it up because we should be doing that to gain proper understanding anyway instead of relying on our tooling to simply tell us only what it wants. (Blah blah blah, I've said all this before)

I agree with you in terms of magic. And I favor keeping it to a minimum.