News for hackers. Stuff that matters.
Re:Step by step from jQuery to Backbone by crescentfresh on Monday July 23, 2012 @09:47AM (#4280921)
IMO what the Backbone.js version has over the jQuery [only] version is readability in a large code base. I assume by "maintainability" this is one thing you mean.

You're only going to cover a small example in a tutorial, so the above benefit is not readily apparent.

Re:Step by step from jQuery to Backbone by DougWebb on Monday July 23, 2012 @10:29AM (#4281132)

   statement: {

       context: { opinion: "mine" },

       subject: "Backbone.js",

       type: new Comparison("jQuery [only] version"),

       filter: new FilterContext("large code base"),

       result: "readability",

       action: raise("assume", { subject: "maintainability" }),
   };


   on("assume") {
       belief: "one thing you mean"
   };

I disagree that this spread-out, boilerplate-rich format becomes more readable the more of it that you have. I think the larger your codebase is, the more important it becomes for distinct chunks of application logic and behavior to be written clearly and concisely.