not true. See the PWA support. Again, should work great with Ember.
-
-
-
Replying to @wycats @cramforce
believe me I'm pretty ready to do work to comply with open requirements that don't involve "notability" requirements.
1 reply 0 retweets 1 like -
Replying to @wycats
that is for 3ps. Ember is a 1p. Impl. is going on here: https://github.com/ampproject/amphtml/issues/3742 … We plan to build Ember, React and Angular examples.
1 reply 0 retweets 1 like -
Replying to @cramforce
@github our SSR support could in theory be a good fit for AMP but begging humans for approval for things sucks.1 reply 0 retweets 1 like -
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
@Medium btw I read this before and thought it was cool.
-
-
I disagree about vdom but that's just because glimmer isn't well understood as an architecture yet :)
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.