A good follow-up to @robconery’s “Ember Confuses Me” post, from @gilesgoatboy: How I understand Ember's MVC:
Rob Conery wrote, in a blog post about how Ember confuses him: A controller proxies the model, and then exposes itself to the rendering engine so that the view can consume it (you may need to read that sentence twice)... This is where I hit a conceptual wall. First: let me say that I'm not the best programmer in the world and I could be dead wrong on this. But as far as I understand it, this is about as tightly bound as we can make things. As stated above, a controller "proxies" the model onto itself for use in the view. I'm trying my best to reconcile this with the notion that a controller (classically speaking) is supposed to ... well control the view. Here, it's not doing that. The original post includes code samples, and I recommend checking it out. What I want to talk about here is very simple: I believe the confusion came from the fact that Ember's "MVC" is a port of...
Full article:
http://gilesbowkett.blogspot.com/2013/03/how-i-understand...