[tdavis]

Excited for the technical write-up as well. I've been building an app in Angular myself and I absolutely love it. Coupled with a REST-ish API library, it's a breeze in terms of testing and separation of concerns. After using Angular, I can't stand the circus of "server renders HTML that includes JS that has server return JSON that's handled by JS that has server render this other thing..."

[nahname]

How is the last part any different? The server still renders HTML with a JS block requesting your view data (via JSON) and then the JS code (using Angular) renders it.

[tdavis]

The difference is that your application server doesn't render HTML; there is no view that produces HTML and sends it as the HTTP response. It's just flat HTML, served up by a generic web server.

This means, among other things, you don't need server-side URL routing or templates. (You need routing for the REST layer, but that can usually be dynamically generated.)

It's just a much stricter separation: the client deals with view logic and HTML and all that, the server deals with pure business logic behind defined interfaces and data formats.

[1qaz2wsx3edc]

curious, why not use the ngResource adapter? I've found it to be awesome unlike other adapters coughember-data

[geelen]

We actually do, within our controllers. I'll add something about that in our detailed AngularJS blog.