4 ms·
They could have fixed this in a heartbeat by simply having pagerank penalize pages for adding external JS assets. No AMP needed; better experience all around,
by hedora 8y ago
They could have fixed this in a heartbeat by simply having pagerank penalize pages for adding external JS assets. No AMP needed; better experience all around, and with less effort.
- LordDragonfang 8y agoThat just leads to every page on the web hosting its own copy of jQuery. The whole purpose of external JS is to reduce load times by sharing cacheable libraries (admittedly with the side benefit of less bandwidth for the host). And if you think a whitelist would work, all it takes is one look at how rapidly new JS libraries come and go to render that unfeasible
- deleted 8y ago[deleted]
- anticensor 8y agoYou would use content names rather than location-based identifiers in that case.
- TFortunato 8y agoIt would be really nice if we started using URIs / URNs more instead of URLs for everything, and did a better job of separating "what" from "where"