Rails 3.1 and SproutCore (Interview)

Topics covered
Popular Clips
Episode Highlights
Server-side JS
Yehuda Katz explores the potential of server-side JavaScript, particularly with Node.js, while acknowledging its limitations. He appreciates JavaScript's suitability for event-driven programming, especially for applications like chat servers, due to its closure properties. However, he believes that the use cases for evented programming are narrower than often perceived. Katz shares his experience with Ruby Racer, a Ruby binding to V8, highlighting its seamless integration and reliability:
I ran Gem install the ruby racer and it actually built without any complaints and it never seg faulted, and all the bindings work perfectly.
---
This approach allows developers to leverage JavaScript's strengths in familiar environments 1.
  Â
Handlebars
Katz discusses the evolution of Handlebars, a powerful templating engine he developed to enhance JavaScript's capabilities. Initially inspired by Mustache, Handlebars allows for more flexible data handling through features like arbitrary paths and block helpers. These innovations reduce the need for JSON preprocessing, making templating more efficient. Katz is working on a bind helper to improve state management in JavaScript applications:
I'm trying to get at with handlebars, is make it possible to do things so that it's not just this huge blob of code of HTML.
---
This feature aims to update specific HTML sections dynamically, enhancing the user experience 2 3.
  Â
SproutCore & Wisdom
Katz provides insights into SproutCore's architecture, emphasizing its convention over configuration approach. He notes that while SproutCore's underlying code is powerful, its API can be uneven, making it challenging to use. Katz highlights the importance of recognizing the wisdom in mature codebases, advocating for refactoring over rewriting. He shares a lesson from the Merb-Rails merger:
People should give more credit to the wisdom in existing code. They should be willing to spend more time refactoring code.
---
This perspective encourages developers to appreciate the robustness of established technologies and focus on improving them 4 5.
Related Episodes


RubyGems and RubyGems.org (Interview)
Answers 383 questions

10+ Years of Rails (Interview)
Answers 383 questions

News Roundup (Interview)
Answers 383 questions

Ruby, TextMate, Red Dirt Ruby Conf (Interview)
Answers 383 questions

Rails is having a moment (again) (Interview)
Answers 383 questions

Vagrant and HashiCorp (Interview)
Answers 383 questions

CocoaPods and MacRuby (Interview)
Answers 383 questions

Ruby, Rails, the Cloud (Interview)
Answers 383 questions

Rails as a day job, Diesel on the side
Answers 383 questions

Rails Girls Summer of Code and Travis Foundation (Interview)
Answers 383 questions

Middleman and Static Site Generators (Interview)
Answers 383 questions

Sass, libsass, Haml (Interview)
Answers 383 questions

Octopress 3.0 (Interview)
Answers 383 questions

Pow, Rails 3.1 Asset Pipeline, CoffeeScript and More (Interview)
Answers 383 questions

CoffeeScript and JavaScript (Interview)
Answers 383 questions
