In September, I took a break from blogging here at to publish three posts with the Safari Books Online Blog.

  • Rendering with named outlets - After talking about complex architectures with Ember in late August, I realized the outlet API was unknown to many Ember users. This knowledge gap made the core ideas in that talk harder to understand. If you haven’t used named outlets or explicit render calls in your apps, this post is an excellent place to start.
  • Introducing Ember App Kit - EAK has been my build pipeline of choice for a several months, and the core concepts behind it are amazingly powerful. The number of tooling options for Ember is growing rapidly now, but EAK has the most interesting ideas and, I think, the brightest path moving forward. Give it a look.
  • Ember.js, À La Carte: Examining Feature Libraries - Over the summer there were several blog posts disparaging single page JavaScript apps, and frameworks in general. Several set Ember.js up as a straw-man. They complained about file-size, then demonstrated a solution to their specific problem without using a framework. Ember isn’t the right tool for every job, and it doesn’t claim to be. Its file-size is a trivial issue for an ambitious and reasonably complex client-side app. Regardless, Ember.js is built of several more focused libraries, many of which are best-of-breed solutions for their respective problem spaces. These libraries can be used alone, and in this post I introduce each with explanations and examples.

Working with the Safari staff to publish these posts and get them read was a pleasure.