[SDGT]

Depends on how you're using angular to inject views.

Vanilla angular views are requested, parsed, bindings added, and then presented. It's one request for the html, all the rest happens in browser.

angular ui views may be different, but according to my network panel on chrome its still one request for the template and whatever assets it brings with it.

I'm going to guess the guys meant they will preload the first view based on page state, which does indeed save a single round trip, but means nothing for any state changes that would occur after the fact. I would argue that an app which needs to micro optimize like this might not be built correctly from the get go, as you're really only saving 1 request and whatever small byte size of the content.

[KaoruAoiShiho]

Your response to someone making an amazing optimization is if you need optimizations your app is done wrong... seriously?

You're seriously underestimating the difference this makes. If this is rendr for angular it is a breakthrough for the angular community.

[benaiah]

That's not what he said. He said it probably wasn't rendr for angular. I'm pretty sure he's saying they preload the initial viewing template (not a prefilled template) based on app state - stuff like clientside routing and such. The browser still has to render the template, but it doesn't have to be fetched by a separate request.