Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
With the rise of Javascript MVC frameworks like Ember and Backbone, web programmers find themselves at a fork in the road. If they keep doing server-side web programming, they'll benefit from tried-and-true tools and techniques. If they jump into Javascript MVC, they may be able to offer a more responsive web experience, but at significant added development cost. Which should they choose? This talk will address the strategic costs and benefits of using Javascript MVC today. I will touch on subjects such as development speed, usability, conceptual similarities with desktop and mobile applications, the decoupling of rendering and routing from server logic, and the state of the emerging Javascript MVC community. I will also discuss the impact of this seismic change on Ruby, Rails, and your career as a software engineer. Help us caption & translate this video! http://amara.org/v/FGjF/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled 'The Front-End Future,' presented by Francis Hwang at GoRuCo 2012, discusses the implications of thick client web development in contrast to traditional thin client approaches, particularly within the Ruby on Rails community. Hwang emphasizes the growing trend of using JavaScript frameworks like Backbone.js and Ember.js, which shift the view logic to the browser and utilize a JSON-based REST interface for server communication. Key points discussed include: - **Definitions**: Thick clients move rendering logic to the web browser, while thin clients rely on server-side rendering. - **Complexity and Speed**: Thick clients add complexity and may require more initial development time, but can yield benefits like faster load times after the initial phase. - **Crawlability**: Web applications that heavily use JavaScript can suffer from indexing challenges on search engines like Google, potentially affecting visibility. - **Decoupling**: A major advantage of thick clients is the separation of concerns, allowing for a cleaner architecture and better scalability, particularly in mobile-first development. - **Responsiveness**: Hwang notes that a primary benefit of thick clients is improved user experience through enhanced responsiveness and faster interactions post-load. - **Future Considerations**: Adopting thick client methodologies is framed as a strategic decision that requires an organization's commitment to modern technologies, as well as an understanding of talent acquisition trends. - **Career Implications**: The talk highlights that while JavaScript’s popularity is rising, Ruby still holds value, and developers should focus on adaptability across technologies. - **Common Myths**: Hwang dispels misconceptions about thick clients, clarifying that client-side code still relies on server-side logic for security and data management. Hwang concludes by encouraging engineers to foster community discussions and adapt to the evolving landscape of front-end development, emphasizing the importance of addressing the challenges while harnessing the opportunities that thick client frameworks present. The takeaways underscore the necessity of thoughtful strategic planning in choosing between thick and thin client development, along with considering organizational capacities for emergent technologies.
Suggest modifications
Cancel
