|
|
|
|
|
by CompuIves
847 days ago
|
|
Exactly, the result would've been different if the author would not have disabled caching. In this case it's because the iframes are loaded/unloaded multiple times, but we also spawn web workers where the same worker is spawned multiple times (for transpiling code in multiple threads, for example). In all those cases we rely on caching so we don't have to download the same worker code more than once. |
|
Even with caching it's absurd to download so much JS for a feature that probably most users will not use. It's a docs site after all.