[no_wizard]

I like AMP conceptually, would make a good app platform for alot of types of websites and such.

I wish it was easier to fork, honestly. There's some good ideas within, though some questionable choices as well.

Unfortunately the project is rather opaque in a number of ways

[lern_too_spel]

How would forking work? The whole point of AMP is that a cache can validate that it is safe to prerender. If you added your own stuff, the caches would just reject it.

[room271]

AMP is both a Javascript framework, and a wider page contract that facilitates CDN inclusion.

I believe the parent is referring to the Javascript framework, which itself has many nice properties for interactivity and performance.

[no_wizard]

Yea and I will say I don’t think it would be terribly hard replicate the benefits of the CDN on something like Cloudflare Workers

[lern_too_spel]

The point of AMP is that the link aggregator owns the cache, not the publisher. You would have to convince Google, Bing, and all the other link aggregators to use your implementation for their AMP caches. That's why it has a standards body. If you don't understand why, you don't understand the problem that AMP solves. https://news.ycombinator.com/item?id=43733809