IO is also the bottleneck on the web, unsurprisingly.

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.

Maybe 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).

Network calls are IO reducing them greatly speeds up websites.

A 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.

Optimizing your IO is indeed a good idea. Back in the day we used to order game data on CD/DVD for efficient streaming.

I don't think so.

My Internet connection saturates my PLC at 10MiB/s, my ping is under the 15ms, and Twitter still takes ~2.4s to load and render a random tweet.

Twitter is a terrible piece of garbage website, isn't that why everyone uses it as the ultimate example of the web sucking?

Twitter wants you to download their app and sign up so they intentionally neutered their web experience. It would probably require 0.1% of their 7500 employees to spend 3 months to fix it entirely, but it's business that drives the bad tech, not the developers

I build internal apps that load collaborative an entire app with MBSE capabilities that have a time to interactivity of < 10s. Google docs takes like 7s to spin up a new doc and interact with it. I can promise you Twitter could reduce rendering some stylish HTML/CSS and a 280 character tweet to a single round trip and see maximum 0.5s browser parse & paint if they wanted to

Taking a quick look at a random tweet through the network tab, about 2/3rds of the time spent is on downloading files. Now should Twitter preload a bunch of videos from recommended tweets it shows below the tweet? Probably not. Does Twitter need megabytes of JavaScript just to show a tweet? I'd hope not. Those things do appear to be the main bottleneck however.

That's not true.

I dunno it definitely seems that way. In our own product reducing IO significantly sped up time to live.