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.
You're seriously underestimating the difference this makes. If this is rendr for angular it is a breakthrough for the angular community.
<script type='text/ng-template' id='hackernews.html'> </script>
And you can call one view with your usual "templateUrl: 'hackernews.html'"
Especially if I have many directives with more than a few lines of html. That way you can embed them in your main html or in a separate cacheable file.
does this mean it serves fully formed html like rendr[1] or highbrow[2]? I'm not sure what angular does, but all client-side apps I've seen, templates are compiled into javascript and concatenated onto the app code, so they're never an extra roundtrip.
1: https://github.com/rendrjs/rendr 2: https://github.com/wvl/highbrow