...
We find this paradigm to be simpler to understand and implement and easier to use when multiple people are working on an application because the MVC pattern enforces separation of concerns and flow control. In other words, once person can work on a view and another can work on a controller without working on the same file and coming into conflict. Therefore, we expect each page to at a minimum have its own controller and at least one view (EJS file in our case).
Can.js currently supports one way data binding from the model to the view. In order to have a user change the model, we need to implement event listeners in the controller that add to or delete from the model, based on user input.
