One query though: All that talk about the shiny new hardware and Ruby being slower in rendering pages under 50ms and the comparison to StackOverflow; isn't that a little unfair? I am trying to understand better and not making claims of knowing better than Jeff. :)
How can you compare a completely server side solution (in ASP.NET MVC) to an almost completely client side solution (in Ember.js), which only uses the Rails API for the backend alone and say .NET is superior to Ruby? Especially when the page rendering time seems to be the only profiled checkpoint for the performance.
Wouldn't JavaScript and the whole Ember.js be adding to the slowness at all?
Semantic versioning states everything inthe public API should be considered unstable and changing until the major version is 1.
So whatever code samples are out there on blogs and SO were from the initial days of the API when it was changing a lot. I am with you and have been going through the pain of weeding out examples from the web that works with the latest version on GitHub. There were many methods that weren't even available in the current API.
Given the paradigm shifts with Router and the Controller, maybe what the Ember team needs to do now is to stop doing everything else and finish up on the documentation for their 1.0.0-rc.1 release before it is finalized to 1.0.0
Downloaded the source and took a look at it. It is a PhoneGap powered Android app, that serves as a viewer to some hard rock artists' videos on YouTube.
Come on, JetBrains !