As a customer, I don't like this behavior at all. I do not like AMP, mostly for the small issue that it's very difficult to link to the base page. Minor consistent inconvenience, major feature rage.
But I can't imagine what it's like for a web developer. You need to support a whole other platform just to maintain your audience, which is also your lifeblood. Also, that audience won't actually see your page; just the text with some Googly UI. Avoiding it would be fantastic, but it also wouldn't be a realistic option.
[0] https://www.alexkras.com/please-make-google-amp-optional/#co...
How would using WebAssembly make the web less free any more than using other new features like Async/Await?
Why is Google Analytics ok and not their CDN?
Serving widely used libraries out of a CDN is a best practice for a reason. Most visitors will already have it in cache. What alternative are you supposing? Local hosting? That has drawbacks, including more cache misses and increased bandwidth costs for the website provider.
Besides providing jquery themselves, websites can use a CDN from another provider. OK, that might cost an extra 20 ms.
Presumably once Google traps you into an unblockable ad channel (on mobile or whatever) they will unleash the tracking they've been doing on you.
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
<script>
if (typeof jQuery == 'undefined')
{
document.write(unescape("%3Cscript src='/serverHostedJquery.js' %3E%3C/script%3E"));
}
</script>99% of websites won't function if they lose a key library.
WebAssembly is an open-standard.
Sure, it has a text format, but it's the equivalent of Lispified Java bytecode. (https://developer.mozilla.org/en-US/docs/WebAssembly/Underst... (uninformative but current), http://loyc.net/2016/lesv3-and-wasm.html (2016, from when wasm wasn't finalized, but has some good concrete examples that look like the wasm in the first link))
With this being said, it may actually be easier to figure out wasm than frameworkified JS since you can apply IDA-style reversing to it.
Open question: what existing tools and research are good at inferring the high-level behavior of stack machines? Eg, research papers, or (preferably open source) tools for reversing eg Java code. I want links I can throw at Ph.Ds.
It's bytecode. I'm not sure if it is a big downgrade from 100,000 lines of minified JS code.
>With this being said, it may actually be easier to figure out wasm than frameworkified JS since you can apply IDA-style reversing to it.
It may.
I can't imagine this accounts for more than a tiny number of visitors and people technical enough to do this will know what to reenable.