tmpfile

Yikes! It's a lot of effort to reduce memory use. They might be better off creating a new Go entrypoint/server that can call into CPython to reuse all their existing/tested modules (treat their Python as a microservice called by Go). They could then use Go to create/call new microservices or replace various routes on a selective basis.

I agree. I would think replaceAll would behave like the following:

/* Usage:

  > 'abcdefabc'.replaceAll('abc')
  'def'

  > 'abcdefabc'.replaceAll('abc', '+')
  '+def+'

  > 'abcdefabc'.replaceAll(/abc/, '+')
  '+def+'

  > 'abcdefabc'.replaceAll(/abc/g, '+')
  '+def+'
 */

 String.prototype.replaceAll = function (re_or_str, sub) {
     return this.split(re_or_str).join(sub||'')
 }

On a side note, is it just me or does the linked polyfill for String.prototype.replaceAll [1] seem wildly complex???

[1] https://github.com/es-shims/String.prototype.replaceAll/blob...

Sure, if everyone decides to host their own files, a CDN would never be used. Although, there are benefits to using a CDN, so it's likely the try-shared value could exist and would be useful.

Note the proposed scheme doesn't prevent anyone from using a CDN as the src while also trying other CDNs to increase the chances of a cache hit, which has its own benefits.

For example, <script src="https://code.jquery.com/jquery-3.4.1.min.js" try-shared="https://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.mi... try-shared="another-src">

One way to prevent a CDN from seeing every request for a shared resource could be a new attribute that allows serving the resource locally if the resource is not in the shared cache.

For example, <script src="/jquery-3.4.1.min.js" try-shared="https://code.jquery.com/jquery-3.4.1.min.js" try-shared="another-src">

@src can be locally hosted. If it's not in cache, the browser can try each @try-shared attr (without loading the resource from CDN). If no match, the browser downloads @src from your own domain.

Of course, this doesn't solve the Shared Cache issue raised by the article. Suppose the only way to solve that would require adding resources to the shared cache explicitly. The most effective way (I assume) would be a header provided by the CDN of a shared resource, eg, X-Shared-Cache: true, that a browser would recognize... Then @src/@try-shared could still get the benefits of the shared cache and developers don't have to worry about it.