Hacker News Reader

I'm pretty amazed it wasn't architected this way from the beginning. Having to generate a monolithic JS file with every comment thread for every pageload for every user? Yikes.

View on HN

Why optimize before they need to? They've done well so far with the current js loading and now they're optimizing b/c it's time.

Because it seems to use up a lot of bandwidth and slows the client.

I just looked at the JS in Firebug, and it's over 100kb for the static portion.

It was rhetorical question. Build your app fast. Then optimize later, when you have scale.

Well, it is not for every comment thread for every page load for every user. For anonymous page views we cache the output so unless there is a new comment (or other changes to a thread) we serve cached (previously generated) javascript file.

Reply on news.ycombinator.com