Hacker News Reader

For the record, I think Twitter is one of the only sites out there that have done JS interfaces the right way. I love the Twitter interface over any Twitter client or the old html interface. I think it's much smoother and works great for their platform. But hey, I'm just one man! Ha

View on HN

"A single tweet page is 2MB. This is one of the big challenges for Single Page Apps."

https://plus.google.com/app/basic/stream/z123j3wxwrm5jb0tv23...

Source: Comparison of various pages: http://mike.teczno.com/notes/bandwidth.html

I'm like 99% they went back to server-side a few months ago for performance reasons.

I think they just render the initial page on the server, then from there the client takes care of it. It makes sense, since it's common to include the data payload in the HTML to save a request anyway, and it's not much more work to just render the HTML too using the same templates as the client uses.

I actually think that is where the path we should go, Hybrid of both tech. Serving the initial view with HTML and the rest via client side JS.

Reply on news.ycombinator.com