News for hackers. Stuff that matters.
Re:Accelerated Mobile Pages Project by antichaos on Wednesday October 07, 2015 @02:08PM (#10347770)
According to the spec, AMP developers are prohibited from adding their own JS, yet they are mandated to include a <script src="https://cdn.ampproject.org/v0.js" async></script> tag as the last element in the <head>. I find it amusing that the JavaScript library itself is 137KB big (38KB gzipped).
Re:Accelerated Mobile Pages Project by callahad on Wednesday October 07, 2015 @04:55PM (#10349031)
<img> and <video> are also prohibited in favor of mandatory custom elements like <amp-img> and <amp-video>.

...and vendor-specific tags like <amp-youtube>, <amp-twitter>, and <amp-instagram>, the library of which is controlled by a single gatekeeper.

There must be less invasive ways of achieving the same goal.

Re:Accelerated Mobile Pages Project by 51Cards on Wednesday October 07, 2015 @02:15PM (#10347826)
However like any CDN content, the goal would be for it to be cached if it's in common use across AMP sites. One JS module that covers a large number of content delivery sites seems like a plus to me. I can't vouch for the whole concept yet though, still reading through their spec.
Re:Accelerated Mobile Pages Project by cramforce on Wednesday October 07, 2015 @04:20PM (#10348786)
Also: We can use a Service Worker for reliable caching of the JS.
Re:Accelerated Mobile Pages Project by niutech on Thursday October 08, 2015 @07:02AM (#10351900)
Now compare this to Instant Articles spec: https://developers.facebook.com/docs/instant-articles/refere... No JS, no Custom Elements, just pure HTML.