Abuse of animation and skip of best-effort loading:
This is probably more relevant to the sluggishness and bad interoperability, rather than JavaScript.
[ Those abusing JavaScript for nefarious purposes: probably not the JavaScript to blame. ]
Standards established don't necessarily imply being well-designed:
Blindly following without thinking shall regardless trap.
Many current infrastructures are fundamentally flawed and difficult to fix:
1 step wrong, all steps wrong.
Over-engineering indeed, but it does address actual problems.
Primarily: Addressing what most browsers haven't well managed to handle: interaction with big files.
E.g. huge database-like Plain Text: browsers typically fail with OOM (Out of Memory).
I'll write a review of GitHub's delivery infrastructure when I have the time.
