Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

Seems like the big confusion about the controller is that it is closer to a ViewModel (think MVVM) than to a Controller itself.

Potatos, Potahtos.



That's the hunch I had reading this (as someone with no EmberJS experience).

To digress a little, it's not much different than the terminology confusion in Backbone, where:

- Router(s) work as front controllers,

- templates (along with the browser's DOM) as views, and

- Views as presenters (from the MVP pattern).

Models are flavored with the Active Record pattern. Presenters and views are tightly coupled.

MVC and MVP coexist because the controllers respond to navigational input (mapping to model-presenter pairs) and the presenters respond to page-specific input (mapping to model manipulations and, possibly, server calls).


Model, View AND ViewModel? What kind of confusing terminology is that? I use KnockoutJS but I still don't understand why it's not just called MVC.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: