[dkopi]

That's how a basic angular.js app with client side templating works if it has to fetch the the data from the server using AJAX calls.

A common optimization would be to preload the served javascript with the initial AJAX results. This still means rendering the content on the client side, but the content isn't fetched asynchronously. Another optimization is to actually render all the DOM elements in advance on the server, and only use client side rendering for updates.

[anton_gogolev]

This, I assume, is all done because 99% of web sites are trivially done with server-side HTML generation and that is not hipstery enough.

[mason55]

It's not a matter of being "hipstery", the drawback is that each time you refresh the view you have to resend all the markup. You're increasing the total amount of data that's going back and forth between the browser and the server. By sending the markup once and then dynamically populating it you can have much faster transitions between objects that use the same view.

What you really want to do is provide progressive enhancement where the first thing a user sees is usable and then more features become available without disrupting whatever the user has started doing (e.g. don't reflow the page while they're trying to read or browse). One way to achieve this is rendering the initial view on the server side and then doing updates via AJAX request but this has meant writing your rendering code twice, once on the server side and once on the client side. This is a reason that node.js and isomorphic JavaScript in general have become so popular.

[anton_gogolev]

Oh give me a break.

> ...the drawback is that each time you refresh the view you have to resend all the markup. You're increasing the total amount of data that's going back and forth between the browser and the server.

For like 99.9% of applications this is a non-issue. For crying out loud, StackOverflow itself has been doing server-side rendering since day one and is still heaps and bounds more usable than WhateverTheHellIsTrendingOnHn.js-based single page isomorphic rich web applications.

It might be my age showing, but, while completely agreeing with you on "progressive enhancement all the way", I find that too freakin' much resources nowadays are spent doing and re-doing and re-inventing something that was working fine in the first place.

[spiderfarmer]

I completely agree. I settled on using sockets.io for the small pieces of my website that can benefit from the realtime aspect of Angular and friends. It's shocking how little code you need to make an awesome 'modern' website. All pages load in under 200ms on first load and I can mostly stick to what I know.

[mipmap04]

There's not a lot of love for server-side generated content in the start up community right now, but it makes things a lot easier most of the time.

[spiderfarmer]

And better.

[plugnburn]

"Server-side HTML generation"... literally each word in this phrase shows how bad things are now in 99% of websites and - what's even worse - we still have to somehow follow these things for some sucky search engine bots that still don't run JS (yandex and other crap).

Let's begin from the end: generation. With a proper presentation layer, we wouldn't have to generate anything. We have data (from the server and/or local in-browser storage) and presentation modules, and we just feed data right into these modules on demand.

Next: HTML. In an ideal situation, we wouldn't touch any raw HTML string at all. Presentation modules, in effect, are responsible for DOM rendering of the page parts they are in charge of. And proper partial rendering usually doesn't involve innerHTML and other raw hacks (well, maybe for quickly clearing element contents, it will do). No escaping hell and other "fun" things.

Next: server-side. Screw all the dogmatic rules that the presentation layer must run on a server. The server should be responsible for handling all non-view logic providing the API for the client to communicate with (from simple AJAX/REST to something more complex like WebSockets) and serving our scripts and assets as fast as possible with proper caching headers, that's all.

This model, if applied wisely, will just make everything easier. I'm in the process of writing an article on it. But as I see Angular in this stack, this particular implementation doesn't show any sign of wisdom. :) Kill the overkill and keep it simple, stupid.

[Mahn]

> Another optimization is to actually render all the DOM elements in advance on the server, and only use client side rendering for updates.

Which is, you know, how the web is supposed to work.

[plugnburn]

Was. 15 years ago.

[uberneo]

You can use ng-if="results" for your result div and this will only display the div only when the $scope.results have got the values from AJAX call