When working on a web application that involves a lot of JavaScript, one of the first things you learn is to stop tying your data to the DOM. It’s all too easy to create JavaScript applications that end up as tangled piles of jQuery selectors and callbacks, all trying frantically to keep data in sync between the HTML UI, your JavaScript logic, and the database on your server. For rich client-side applications, a more structured approach is often helpful.

With Backbone, you represent your data as Models, which can be created, validated, destroyed, and saved to the server.

This is pretty cool. It is something in between JQuery and NodeJs but it require some migration from JQuery:

If UX wasn’t an issue and performance or a more objected oriented approach was needed, I would definitely consider it.

About mcloide

Making things simpler, just check: View all posts by mcloide

2 responses to “Backbone.js

  • juliancc

    Chris you have it all wrong. It allows you to create a more structured JS application, and it’s fully compatible with jQuery and NodeJS. In fact we are using backbone at our current job as our foundation. But we also include jQuery/Zepto to do all DOM manipulation, and Mustache for our templates. I would recommend you read a little bit more about it, it’s def worth checking out.

    • mcloide

      Julian that is why you know more js than I do. Anyways, I will definetly check it out. I’m reading more stuff out of PHP to play a bit more with it. Since you have more experience with backbone, do you have any posts on your blog on using it. I would like to reference it here…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: