This article is outdated with the new router system. Basic application structure has changed a lot as you can see in the latest guide here: http://emberjs.com/guides/outlets/
I wrote this article while I was learning Ember, and in fact used it as a way of answering many of the questions I had that documentation didn't cover.
We've been rebuilding http://customer.io in Ember.js over the past week or so. After dabbling in ember on a few screens, we decided to take the plunge and go all the way. We're feeding data to ember from a private API on the back end. As the front-end guy in our duo, I love being able to bind UI to ember objects. It's really refreshing to be able to bind a text field and an h1 to the same ember object and watch the latter update in real time. And everything being in javascript makes it great to debug using the console in chrome. As ember matures and becomes more widely accessible, I'm excited to see even more great stuff being built on Ember.
As others have mentioned I'm using Github's Gist system for embedding code snippets. Makes it much easier to maintain and update, and also provides syntax highlighting and the ability for people to fork the snippet.
Apologies that you weren't able to see the samples. I'll have to consider how to manage that.
He has JavaScript disabled. The code samples are provided by github's gist stuff. It's an interesting example of JavaScript being used to render rather than enhance, complete with a lack of graceful fail.
If you have javascript disabled you should be used to pages not rendering sometimes, not the best practice, but common enough to not be surprised if something is off.
