@github our SSR support could in theory be a good fit for AMP but begging humans for approval for things sucks.
-
-
maybe that isn't how it works in practice. How does a new publisher get "amp certified"?
2 replies 0 retweets 0 likes -
also, has there been any thought about a subset of JS APIs that could run in an AMP context?
2 replies 0 retweets 0 likes -
I designed DOMChangeList to be a reasonable fit for AMP-like contexts that want to restrict all JS on the UI thread.
1 reply 0 retweets 1 like -
maybe allowing blanket workers is acceptable?
1 reply 0 retweets 0 likes -
Replying to @wycats
yep, that is the plan.http://medium.com/@cramforce/2016-will-be-the-year-of-concurrency-on-the-web-c39b1e99b30f#.b0q22m3y6 …
2 replies 0 retweets 0 likes -
Replying to @cramforce
@Medium cool! You should like DOMChangeList then. https://github.com/whatwg/dom/issues/270 … maybe an AMP polyfill can move us forward.2 replies 1 retweet 1 like -
Replying to @wycats
I'll take a look. In general: AMP wants to limit itself to content-only use cases. Nothing that falls into app realm.
1 reply 0 retweets 1 like -
Replying to @cramforce
sure, but lots of content sites have "rich" content or social structure (like Bustle, Vox or Discourse)
1 reply 0 retweets 0 likes -
Replying to @wycats
yeah, so what you describe is exactly what we want to support.
2 replies 0 retweets 0 likes
fwiw I have also described this problem as "the coordination problem" and have thought a lot about the needed primitives.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.