Ruby Video
Talks
Speakers
Events
Topics
Leaderboard
Sign in
Talks
Speakers
Events
Topics
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Help us caption & translate this video! http://amara.org/v/FG7j/
Date
Summary
Markdown supported
In the talk "A Tale of Two MVCs" presented by Yehuda Katz at GoGaRuCo 2013, the focus is on the Model-View-Controller (MVC) architectural pattern, particularly in the realm of GUI programming. Katz aims to clarify the various interpretations and implementations of MVC, especially in relation to modern frameworks such as Rails, Ember, and Backbone. Key points discussed include: - **Understanding MVC and GUI**: Katz emphasizes that many people lack a comprehensive understanding of the different MVC systems and how they apply to GUI programming. - **Common Steps in GUI Programming**: He outlines the basic steps in GUI programming from initial UI bootstrapping, translating user input into actions, updating application states, to notifying the UI of changes. These processes are consistent across different MVC architectures. - **Issues with Original MVC**: The talk identifies three main problems with traditional MVC implementations: - Lack of defined patterns for bootstrapping objects effectively. - Haphazard storage and management of application state across different widgets, leading to complexity. - Challenges in maintaining synchronous states between browser action and application state, especially during page reloads. - **Critique of Rails**: Katz discusses the misconception that Rails deviates from MVC, presenting it instead as a GUI design pattern with similarities to traditional MVC, while also acknowledging that Rails struggles with managing UI hierarchy and state effectively. - **Advancements in Modern Frameworks**: Insights into how frameworks like Ember and Cocoa improve MVC by introducing concepts like mediating and coordinating controllers, which enhance delegation and flexibility in event handling. He illustrates that Ember provides a clearer structure for managing state within its framework. - **Comparison of Ember and Rails**: Katz concludes with an assertion that Ember's architecture separates UI logic effectively while allowing Rails to concentrate on persistence infrastructure, suggesting that the two can complement each other rather than conflict. Overall, the talk seeks to provide clarity on MVC's evolution, advocating for a clear separation of responsibilities in application design to foster better development practices.
Suggest modifications
Cancel