3 ms·
When someone realized you pay a lot for cycles at the server, but you pay nothing for cycles at the client, that was the moment the world-wide web began to die.
by erik_seaberg 7y ago
When someone realized you pay a lot for cycles at the server, but you pay nothing for cycles at the client, that was the moment the world-wide web began to die.
- dimgl 7y agoWell this is hyperbolic.
- deleted 7y ago[deleted]
- _bxg1 7y agoThis is baseless mudslinging. The bottleneck on the client is virtually never the cycles consumed by the actual running of the actual app's JS code. It's usually, in order starting with the most common: - Piles of ads/analytics scripts which have no motivation not to slow down the page - Reflow; i.e. needlessly many elements on the page causing the browser to do extra work calculating layout - The initial loading and JIT-ing time of a needlessly heavy JS bundle