For those of you who haven't been following Icelandic politics, something unusual has happened.
For the first time our government is a coalition of a right-wing party, a centre party, and a proper environmentalist left-wing party who intend to operate along the lines of Nordic-style consensus politics.
The last time something even remotely like this happened was in 1959 when a right-wing/left-wing coalition appointed Iceland's first healthcare minister and built the healthcare system.
RT @ID_AA_Carmack@twitter.com If the $35 smartphones for the developing world were programmed like old game consoles, they could have 60 fps, super responsive interfaces.
RT @AaronToponce@twitter.com Bitcoin mining is now consuming more electricity than 159 countries. I never thought that the end of the world would come because of Internet play money.
I've been following the developments surrounding JSON Feed with interest as their approach seems so completely different from anything at the W3C.
Namely, it's mostly a bunch of long-term, experienced coders who've spent years dealing with RSS and Atom and are trying to make dealing with feeds easier.
They aren't trying to bring in a better architecture, add use cases or bridge gaps to future functionality.
AMP could make it really easy for you to make systems where the entire page is archived when you like a link. Or it could make it easier for you to make a reliable copy for yourself to annotate. Regular pages have a habit of breaking when slurped up from one location to another whereas that's specifically what AMP is for.
AMP has downsides, sure. But most of those are largely caused by the fact that the current primary consumer of AMP is an amoral tech co. It doesn't have to stay that way.
The potential tragedy of AMP is the same as with feeds: of the entire tech industry, only Google seems to see the potential of the model.
AMP lets you build apps where you can aggregate, store, & serve _locally_ large parts of the web without making deals with individual sites. For Mastodon, this could mean, for example, your local instance storing caches of AMP articles, pre-rendering them when they are linked to in your feed, causing them to load instantly when clicked.
You could either rail against AMP or marvel at the fact that Google has effectively convinced most of the web to turn on full content feeds.
AMP is designed to be portable from origin to arbitrary locations (caches). It's basically Syndication 2.0, succeeding where RSS/atom didn't.
Rather than seeing AMP pages as crippled-but-fast web pages, think of them as full content feeds with substantial additional support for interactivity and styles.