Jun 12, 2012
One of those frameworks is Backbone.js, which in one and half years old. Over time, it has attracted the attention of many developers, creating a great community, and now that community achieved the first backboneconf a few days ago in Boston.
The speakers at the event really promised a quality event. The conference was small and sold out quickly. The expectation was great.
Jeremy Ashkenas opened the conference with an introduction to Backbone.js. Jeremy started talking about the reason of its existence and why many of the developers attending the conference were there.
The controversy began when Jeremy mentioned that “There is no typical Backbone app”, instead of a working example Jeremy gave us a kind of guideline that we can use when we are creating backbone apps.
I can highlight the following from his talk:
- Backbone is not MVC, it is MV*
- DOM Independency
- Driven by use cases
- UI Agnostic
- Statelessness as a way of life
The first day at BackboneConf, except for the introduction of jeremy, there was no talks about backbone.js. Many of the speakers talked about backbone alternatives. Yehuda Katz talked about Ember.js and Vojta Jina, a Google engineer, talked about Angular.js, two very interesting alternatives to backbone, each one with its advantages and disadvantages.
On the first day, attendants could realize that backbone.js is not the only solution to the problem and that each of their creators invented their own particular wheel.
The second day was more focused on Backbone. Many of the speakers showed us their success stories using backbone.js and how they extended backbone in order to achieve their needs. It was until that moment that I realized of the high extensibility of Backbone and that backbone is only an initial set of tools we can extend according to our needs, just like a diamond rock.
Focused on design patterns, Brandon started splitting off the different concerns of the ajax call into separated backbone classes.