What if every browser vendor just started creating its own "standards" and shipping them? "Everyone can participate" but...
-
-
This is all theoretical. In reality it is drastically easier to participate in & influence AMP as a web dev than it is for web standards.
1 reply 0 retweets 1 like -
As a full time web developer who participates in standards too I can categorically say that this is false.
1 reply 0 retweets 13 likes -
Replying to @wycats @cramforce and
Web standards processes give leverage to participants, implementor or not. This is a source of frustration for some implementors.
3 replies 0 retweets 7 likes -
You are a laudable exception. For now AMP has 3x the GH contributors to HTML.
5 replies 0 retweets 0 likes -
Replying to @cramforce @wycats and
Unfortunate that you go there, as the comparison is DOA. AMP is not a network protocol that people can adopt, it's a Google Search product.
2 replies 0 retweets 0 likes -
Replying to @espadrine @cramforce and
Not only can you fork HTML, the most watched HTML spec is a fork, not the W3C one. You can't fork AMP. What would be the point?
1 reply 0 retweets 0 likes -
Replying to @espadrine @cramforce and
To me, the best test for open-source is: can you fork it? If not, you're just publicizing proprietary information and listening to customers
2 replies 0 retweets 1 like -
Replying to @espadrine @wycats and
Why can't you fork it? People certainly have and use it happily.
1 reply 0 retweets 0 likes -
Replying to @cramforce @wycats and
Because if Google Search doesn't use your changes, your fork has no value.
2 replies 0 retweets 1 like
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.