yep, that is the plan.http://medium.com/@cramforce/2016-will-be-the-year-of-concurrency-on-the-web-c39b1e99b30f#.b0q22m3y6 …
-
-
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 -
Replying to @cramforce
a lot of the perf work I've done for the past 18 months has been for LinkedIn Mobile, which is also quite content rich.
1 reply 0 retweets 0 likes -
Replying to @wycats @cramforce
would you say the criteria is: "expects a lot of traffic from SRPs"?
1 reply 0 retweets 0 likes -
-
Replying to @cramforce
what counts as "content" then? Journalism? Or something else?
1 reply 0 retweets 0 likes -
Replying to @wycats
mostly: works with stale-while-revalidate caching model. Does not need app like functionality. Wants to be embedded into other apps.
2 replies 0 retweets 1 like
"app like functionality" seems too vague because of http://www.vox.com/2015/7/22/9013911/is-the-media-becoming-a-wire-service … - do you mean "workspace" like apps (live inside?)
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.