Here's how annoying AMP is: Apple built an OS-level feature to get rid of it.https://daringfireball.net/linked/2017/08/23/ios-11-amp …
-
-
This is an easy point to make, but have you actually experienced the process?https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md …
-
Yes, we have a BDFL model. I’m open to changing it, but the request has to come from members of the community not random internet people.
-
It just means that the claim that "amp renders in every browser" is missing the most important issue.
-
It is a key distinction from tech like WAP.
-
But it's not a key distinction from 90s MSFT, which for example openwashed OOXML.
-
Bottom line is that I think it's reasonable to believe that the current structure is not a good fit for a web standard.
-
It's also reasonable to believe that the reason for AMP's nominal success is anticompetitive use of Google's search dominance.
-
I definitely feel like Google is cramming this down my throat, but "anticompetitive" implies competition to solve whatever it is AMP solves.
- 1 more reply
New conversation -
-
-
Ryosuke and others at Apple contributed a lot to custom elements and helped shape the class based version
-
He's referring to AMP web components, not web components in general.
- End of conversation
New conversation -
-
-
I do think we'll see great adoption of web components and more contributions to spec in the future though.
Thanks. 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.