Sorry isn't this just another web developer complaining that they have to use someone else's technology? I mean the first time I looked into supporting AMP I had that same visceral reaction "f this it sucks". After spending sometime with it it's not that bad and I get the value prop - AMP is content being served up directly on google.com or cloud flare or any cdn provider that is essentially the evolution of google's cache. Pretty cool if you stop to think about it. In the past to access google's cache you got a pretty fast page response but it was kind of also very broken because not all of the essentials would load correctly. Now with AMP you have some control over that cached page that is offloaded for free to google's servers. I think there are some UX issues for sure - IMO it's open source so you can always open a pull request/issue and try to make it better... or ignore it and continue to build something great... if you have something great people will find it whether you use AMP or not.