ebryn

Django / other backends aren't mutually exclusive with Fastboot. You can use them together.

Unfortunately your example isn't a full reproduction as both the Ember/React examples reuse existing DOM which is important for selection state and the popover functionality.

Ember already has what you describe as "standard I/O."

I think you'll be happy with the stuff I've been working on. Should have something to show off in the coming weeks :)

Great job everyone! Open source FTW.

Ember is going to be as fast, if not faster, than React with HTMLBars integration. Expect to hear more about that in the coming weeks.

For more info, check out my talk at the Ember NYC meetup here: http://bit.ly/P2Wu6X

One of the best articles I've seen written about the future of the web and moving past the constraints developers place on UX due to the way we've built web apps in the past.

Hey, I'm Erik, an Ember.js core team member.

I'd be happy to help you track down the issues you came across and explain to you what is going on.

You can reach out on Freenode or Twitter, I'm @ebryn. Otherwise, email me at erik.bryn -at- gmail.

Something weird is going on with rawgithub.com. Here's an updated version: http://jsfiddle.net/Ut2X6/8/

I'm going to do everything in my power to see this happen :)

Actually, it doesn't "force" you to use get/set. You can just POJOs just fine w/ Ember, but you won't get property observation or unknownProperty support.

I also question your assumption that Object.observe will be as fast as Ember's observation system. I wouldn't be surprised if it was several times slower.

Object.observe also doesn't support array observation, which is something we support in Ember.

We've added download links :)

If you inspect the DOM, you can see the links to the MP4/WebM videos. We'll add download links and a podcast feed soon.

I think you meant to suggest: {{log controller}}

I just want to point out that Randy is advocating for the use of Cappuccino. Many people seem to be thinking that is the point. It's not.

I feel like this argument is similar to what people said when Rails hit the scene.