This 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 usuall

This 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