Blog

JSConf is a unique conference organization, because we aren't really a conference organization at all. We are a very loose federation of developers who share the same general idea about how a technical conference should be held. We don't believe that one model or process fits all communities, in fact we are big advocates of locally run events driven by passionate individuals dedicated to the community. We make events that aren't from the standard conference playbook because we believe you (attendees, speakers, and sponsors) deserve more than that. We focus on two things, pushing the boundaries of what is thought to be conceivable with JS and providing exceptional human social activities that encourage community and friendship building.

JSConf is a unique conference organization, because we aren't really a conference organization at all. We are a very loose federation of developers who share the same general idea about how a technical conference should be held. We don't believe that one model or process fits all communities, in fact we are big advocates of locally run events driven by passionate individuals dedicated to the community. We make events that aren't from the standard conference playbook because we believe you (attendees, speakers, and sponsors) deserve more than that. We focus on two things, pushing the boundaries of what is thought to be conceivable with JS and providing exceptional human social activities that encourage community and friendship building.

When you work with JS in complicated apps it's easy to get yourself into a mess of selectors, events, callbacks, functions and more. There is when frameworks like Backbone come to rescue us from that anarchy. Backbone give us a way to decouple things and give a structure(MVC) to our JS application.

"With Backbone, you represent your data as Models, which can be created, validated, destroyed, and saved to the server. Whenever a UI action causes an attribute of a model to change, the model triggers a "change" event; all the Views that display the model's state can be notified of the change, so that they are able to respond accordingly, re-rendering themselves with the new information. In a finished Backbone app, you don't have to write the glue code that looks into the DOM to find an element with a specific id, and update the HTML manually — when the model changes, the views simply update themselves."...