would love to get Ember 1st class support with AMP's PWA story. Ember and AMP should fit together nicely.
-
-
Replying to @cramforce
the problem is that amp blesses "notable" components and has no other escape valves.
1 reply 0 retweets 0 likes -
Replying to @wycats
not true. See the PWA support. Again, should work great with Ember.
1 reply 0 retweets 0 likes -
-
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 -
Replying to @wycats
yes, lots of thought on JS. No certification for publishers. You just publish and say: I am AMP
1 reply 0 retweets 0 likes
I'd be very interested in working on ways to expand the scope of acceptable JS so general purpose Ember apps could work.
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.