Hacker News Reader

As someone who's just getting started with Backbone, I'd be very interested to see that talk, and here suggestions for what to do instead of 'this.model.view = this'.

View on HN

If Spine is anything to go by, you bind events from the view to the model and then trigger them from your code on the model instance.

Usually that's the case -- but if you know for certain that there's a one-to-one relationship between a model and it's view, then there's no harm in having a direct reference for convenience. Pragmatism > Purity, where UI code is concerned.

I agree with you. I'm concerned about memory leaks from the circular references, though.

Circular references are garbage collected -- no need to worry about them.

You might be thinking of a terrible old IE bug where circular references between JavaScript objects and DOM nodes were never collected, but that's never been an issue with JavaScript-only references.

Oh, I didn't know that. That alleviates many of my concerns, then, thank you.

The Responder pattern used in SproutCore (inspired by Cocoa) is very elegant.

Reply on news.ycombinator.com