Module Pattern in JavaScript and CoffeeScript | Hacker News Reader

Module Pattern in JavaScript and CoffeeScript

robots.thoughtbot.com

28 pointsCroaky12 comments

A cleaner way of doing the immediately-invoking function in CS is to use a `do` statement.

    MyModule = do ->
      # module body

No need for any parens.

And you don't even need to use assignment. This works as well:

    do ->
      # module body

you don't need to assign it to something, unless you need to assign it to something.

sounds like op was specifically referencing to parens for execution.

Interesting, I looked this up.

> CoffeeScript provides the do keyword, which immediately invokes a passed function, forwarding any arguments.

Apparently in April 2012 they updated the code to make it simulate namespacing.

> A tweak to the semantics of do, which can now be used to more easily simulate a namespace: do (x = 1, y = 2) -> ...

I have only just started learning the details of JavaScript. While reading JavaScript: The Good Parts I found myself asking the question what the difference between a module and a closure is. As far as I can tell they are the same thing. Is that correct or am I missing something?

There aren't native modules in JS (though they are coming in ES6). The module pattern is a way of having private scope by wrapping everything in a closure. So yes, the module pattern just creates a closure and returns an object (or assigns to global scope) with its public members.

A module is a design pattern and a closure is a language construct. A module (in the context of the "module pattern") is a closure but all closures are not "modules".

Well I really prefer creating classes and AMD modules for almost everything. Using CoffeeScript this is just a couple of rows:

    class Calculator

        prettyText = "Answer is: "
        printResult = (result) -> console.log result
  
        add: (addedOne, addedTwo) => 
           sum = addedOne + addedTwo
           printResult prettyText + sum

    calculator = new Calculator();

Nice article....Is there a reason for having a separate return within each method? How about returning all of the methods with a single return?

This is pretty similar to what I've been doing. Does anyone have any thoughts on using CoffeeScript with RequireJS?

very clear tutorial. thumbs up

I've been sub-namespacing conventions of MVCs, too.

    new GlobalNS.App.MicroViews.TableRow extends Backbone.View
    new GlobalNS.App.Models.TableCell extends Backbone.View
    ...

Essentially you can namespace to Babylon from existing conventions and build "interaction models" (complex namespaces) for standard digital content types like "lists", etc., from say http://pea.rs

JS and Hypermedia have always been in harmony. Other boring ideas: https://github.com/nerdfiles/nerdfiles_net_dev/blob/master/t..., https://github.com/nerdfiles/nerdfiles_net_dev/blob/master/t...

Reply on news.ycombinator.com