quarterto

Wouldn't that be nice. But Google don't control how relevant or fast something is, they can only decide how to rank them.

As soon as Google stops providing value to publishers, they lose their power in the industry. For now, we work with what we have.

As somebody who has implemented AMP for a major newspaper, these are in fact things that publishers want.

Sure, speed should be a ranking factor, but I'd much rather have a slow site that's relevant than a fast one that isn't.

That is a sticking point for me. Alternative AMP caches (with alternative UX, e.g. Ampersand generally keeps users on your site when they bounce) go some way towards solving this, but they're not (yet?) first-class ecosystem citizens:

> But these are just guidelines, and Google can’t guarantee they’re behaving well, so they’re not first-class citizens.

> I’d love for this to be something you could statically verify, just like AMP HTML, so that anybody could add a Cache to the ecosystem and get a lightning bolt on Google search results and Cloudflare links and Twitter Moments™, but I’m pretty sure this reduces to the Halting Problem.

> Google gonna Google. They’ve been dangling carrots in front of publishers for twenty-one years.

But that's the point: AMP allows far richer pages than just totally cutting out Javascript. Like it or not, the web is an application platform.

If you use Cloudflare as your CDN, is Cloudflare "siphoning your traffic"?

Node has supported all of ES6 except modules since 6.0.

Post with more comments than upvotes are penalised as a proxy for controversiality (remember HN doesn't have downvotes for posts)

It's Datasette that created the site