<story><title>Python 3.11 in the Web Browser</title><url>https://2022.pycon.de/program/SBCNDY/</url></story><parent_chain><item><author>modeless</author><text>I really, really wish it were possible for wasm modules like this to be shared between sites. That is, python.org could host an official wasm module, and the first time you visited a site using python the browser would download and compile it once and cache the result, and then any other website could use python with no download size or load time penalty. But unfortunately privacy concerns killed this utopia. Caches are now partitioned per origin, so every site that uses python has to download and compile the wasm module separately even if it&amp;#x27;s the exact same module from the same place, and that is unlikely to ever change: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;developer.chrome.com&amp;#x2F;blog&amp;#x2F;http-cache-partitioning&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;developer.chrome.com&amp;#x2F;blog&amp;#x2F;http-cache-partitioning&amp;#x2F;&lt;/a&gt;</text></item></parent_chain><comment><author>nine_k</author><text>While I understand how finding a particular unique resource cached may allow to glean some privacy-infringing info, I don&amp;#x27;t see how detecting a common library downloaded from a site that provides it for everyone (like python.org) would help reveal anything.&lt;p&gt;If users might define a list of sites trusted for cross-site caching (like fonts.google.com and other known library CDNs), this could help cache quite some common resources without downsides to user&amp;#x27;s privacy.</text></comment>
<story><title>Python 3.11 in the Web Browser</title><url>https://2022.pycon.de/program/SBCNDY/</url></story><parent_chain><item><author>modeless</author><text>I really, really wish it were possible for wasm modules like this to be shared between sites. That is, python.org could host an official wasm module, and the first time you visited a site using python the browser would download and compile it once and cache the result, and then any other website could use python with no download size or load time penalty. But unfortunately privacy concerns killed this utopia. Caches are now partitioned per origin, so every site that uses python has to download and compile the wasm module separately even if it&amp;#x27;s the exact same module from the same place, and that is unlikely to ever change: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;developer.chrome.com&amp;#x2F;blog&amp;#x2F;http-cache-partitioning&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;developer.chrome.com&amp;#x2F;blog&amp;#x2F;http-cache-partitioning&amp;#x2F;&lt;/a&gt;</text></item></parent_chain><comment><author>xpressvideoz</author><text>Wait, so the traditional &amp;quot;use the JavaScript CDN as a cross-site cache&amp;quot; method does not work anymore? How did I not know that!</text></comment>