In a few days, Paul Bakaus from the AMP team will give a talk at WebExpo in Prague. I asked him a few questions: Whether AMP can be considered a successor to the jQuery ecosystem, about the issues associated with the potential opening of AMP benefits to all sites, and finally the AMP Bento subproject.

“AMP can save lots of maintenance and bug fixing time”

Paul, I look forward to you showing AMP as a front-end framework in your talk! The framework impressed me a while ago, but not everyone knows its benefits. Could you briefly list AMP framework advantages over current solutions for content and e-commerce sites — where jQuery is still the most common?

Great to hear! AMP is really a pretty misunderstood project. It was always a framework, but it’s often compared to other walled garden distribution formats. Most web developers are not aware that AMP can be used as a standalone framework.

I’m biased of course, but I do think you get a lot of cool things when you choose to go all-in with AMP. Our core philosophy is to allow developers to focus less on boilerplate code, and more on the code that actually matters, that differentiates them from their compe*****s. So we solve things at a much higher abstraction layer – we’re not a JS framework, we’re an HTML framework.