Hacker News Reader

Comment by picardo | Hacker News Reader

I think what he is saying is since there is a network delay of 300ms for every request, it's better for him to make a single request for a large file than to have to make 10 requests for 200k files and wait 300ms * 10.

View on HN

If every requests adds this fixed latency, it would be much better to try and parallelize the requests vs bundling everything.

True, but these requests cannot be made simultaneously. The code is loaded only when the UI needs it.

If the files can be combined, the requests can be made simultaneously

You're right, and HTTP/2 was supposed to be a major boon here, but the problem is actually that the UI itself only loads these things once they've been rendered by the framework which is often after another component has loaded them, and even if they can be ran in parallel the response times can still vary, causing the UI jiggle you often see.

This isn't really a problem unique to high latency either, if you have a patchy connection in transit or for some other reason, the UI will suffer.

> but the problem is actually that the UI itself only loads these things once they've been rendered by the framework which is often after another component has loaded them

That just sounds like bad front end coding. A good framework used properly would not have that issue.

In webpack you can define which components are in which chunk, so you could organize them that way. I don't, but I know it exists.

Reply on news.ycombinator.com