7 ms·
I don’t know, is it? I get it, sure data has to be loaded, but the problematic part is the work being done on that data, this is what takes much more time than
by kaba0 4y ago
I don’t know, is it? I get it, sure data has to be loaded, but the problematic part is the work being done on that data, this is what takes much more time than it should reasonably take.
Just take the example before, if twitter were server-side rendered, it would likely load in basically a blink of an eye.
The problem is code, which will later do more network calls which again have to be waited on, this is multiple round trips. Also, the fault lies probably a bit on web tech as well, html+css is just a terrible abstraction, layouting not being properly solved.
- norman784 4y agoMaybe a partial solution will be to use qwick approach, load js on demand when needed, instead of all at once, while ideally will be use strictly the necessary js (that in some cases could be none).
- meheleventyone 4y agoNetwork calls are IO reducing them greatly speeds up websites.
- kaba0 4y agoA network call waiting on the result of another call is still two times as long as it should/could be, no matter how efficient you make it.
- meheleventyone 4y agoOptimizing your IO is indeed a good idea. Back in the day we used to order game data on CD/DVD for efficient streaming.