I had instant flashbacks to WAP 2.0 when I read about AMP..
Let’s make a variant of normal websites, that solves problems for mobile, by limiting
options on authors and readers alike..
Past experience shows that this just doesn’t work. At least not for those parties that are
already no able to deliver a proper secondary channel.
DJ
On 8 okt. 2015, at 19:23, Tilman Bayer
<tbayer(a)wikimedia.org> wrote:
Yes, the Niemanlab summary is really informative. Read it last night and this part kind
of jumped out at me:
"There are lots of clever ideas here, and it’s understandable why these constraints
would help improve performance. For better and for worse, this is essentially a rollback
of how HTML and web technologies have evolved over the past decade. It’s a little jarring
that so many of the sample AMP pages on display this morning look a lot like the web of,
say, 2002, shrunk down to a phone screen.: "
Reminds one of a certain website that's often accused (quite rightfully) of being
stuck in 2002... Another point of the article is that a lot of the perf improvements are
being achieved by ruthlessly banning third party ads and trackers, both of which Wikipedia
does anyway because of our neutrality and privacy principles.
On Thu, Oct 8, 2015 at 9:53 AM, Luis Villa <lvilla(a)wikimedia.org
<mailto:lvilla@wikimedia.org>> wrote:
Best big-picture article I saw on it last night was
http://www.niemanlab.org/2015/10/get-ampd-heres-what-publishers-need-to-kno…
<http://www.niemanlab.org/2015/10/get-ampd-heres-what-publishers-need-to-know-about-googles-new-plan-to-speed-up-your-website/>
On Thu, Oct 8, 2015 at 8:05 AM, Jon Katz <jkatz(a)wikimedia.org
<mailto:jkatz@wikimedia.org>> wrote:
FYI. Google just announced an open source project to create a speedier framework for
mobile browsing. It might be worth looking at what they're doing:
From:
http://tech.slashdot.org/story/15/10/08/035200/googles-effort-to-speed-up-t…
<http://tech.slashdot.org/story/15/10/08/035200/googles-effort-to-speed-up-the-mobile-web?utm_source=rss1.0mainlinkanon&utm_medium=feed>
Google has officially taken the wraps off its AMP project — Accelerated Mobile Pages
<https://www.ampproject.org/> — which aims to speed up the delivery of web content
to mobile devices <https://www.ampproject.org/how-it-works/>. They say, "We
began to experiment with an idea: could we develop a restricted subset of the things
we'd use from HTML, that's both fast and expressive, so that documents would
always load and render with reliable performance?" That subset is now encapsulated in
AMP, their proof-of-concept. They've posted the code to GitHub
<https://github.com/ampproject/amphtml> and they're asking for help from the
open source community to flesh it out. Their conclusions are familiar to the Slashdot
crowd: "One thing we realized early on is that many performance issues are caused by
the integration of multiple JavaScript libraries, tools, embeds, etc. into a page. This
isn't saying that JavaScript immediately leads to bad performance, but once arbitrary
JavaScript is in play, most bets are off because anything could happen at any time and it
is hard to make any type of performance guarantee. With this in mind we made the tough
decision that AMP HTML documents would not include any author-written JavaScript, nor any
third-party scripts." They're seeing speed boosts anywhere from 15-85%, but
they're also looking at pre-rendering options to make some content capable of loading
instantaneously. Their FAQ <https://www.ampproject.org/faq/> has a few more
details.
Google blog announcement:
https://googleblog.blogspot.com/2015/10/introducing-accelerated-mobile-page…
<https://googleblog.blogspot.com/2015/10/introducing-accelerated-mobile-pages.html>
_______________________________________________
Mobile-l mailing list
Mobile-l(a)lists.wikimedia.org <mailto:Mobile-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/mobile-l
<https://lists.wikimedia.org/mailman/listinfo/mobile-l>
--
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
Working towards a world in which every single human being can freely share in the sum of
all knowledge.
_______________________________________________
reading-wmf mailing list
reading-wmf(a)lists.wikimedia.org <mailto:reading-wmf@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/reading-wmf
<https://lists.wikimedia.org/mailman/listinfo/reading-wmf>
--
Tilman Bayer
Senior Analyst
Wikimedia Foundation
IRC (Freenode): HaeB
_______________________________________________
Mobile-l mailing list
Mobile-l(a)lists.wikimedia.org <mailto:Mobile-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/mobile-l
<https://lists.wikimedia.org/mailman/listinfo/mobile-l>