TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Google’s AMP Poised to Take the Lead from Facebook’s and Apple’s Walled Gardens

112 点作者 webdisrupt超过 9 年前

13 条评论

x1024超过 9 年前
(The article said to &quot;try any page from The Guardian with &#x27;&#x2F;amp&#x27; to test its performance&quot;)<p>Oh my: <a href="http:&#x2F;&#x2F;tools.pingdom.com&#x2F;fpt&#x2F;#!&#x2F;bniZiH&#x2F;https:&#x2F;&#x2F;www.theguardian.com&#x2F;world&#x2F;2016&#x2F;jan&#x2F;20&#x2F;bacha-khan-university-explosions-heard-as-gunmen-attack-pakistan&#x2F;amp" rel="nofollow">http:&#x2F;&#x2F;tools.pingdom.com&#x2F;fpt&#x2F;#!&#x2F;bniZiH&#x2F;https:&#x2F;&#x2F;www.theguardi...</a><p>&quot;Such mobile performance, wow&quot;. 4 megabytes of video(Preloading two different videos. Why?), maybe 10 different domains, downloading JS before downloading images...<p>And this is the <i>showcase</i> for AMP.<p>It&#x27;s almost as if &quot;there is no silver bullet&quot; for web performance, and &quot;actual programming skill&quot; is still a requirement.<p>There is a difference between AMP and non-AMP, yes: <a href="http:&#x2F;&#x2F;tools.pingdom.com&#x2F;fpt&#x2F;#!&#x2F;bAnV7C&#x2F;https:&#x2F;&#x2F;www.theguardian.com&#x2F;world&#x2F;2016&#x2F;jan&#x2F;20&#x2F;bacha-khan-university-explosions-heard-as-gunmen-attack-pakistan" rel="nofollow">http:&#x2F;&#x2F;tools.pingdom.com&#x2F;fpt&#x2F;#!&#x2F;bAnV7C&#x2F;https:&#x2F;&#x2F;www.theguardi...</a><p>But at this point in time, it seems that installing an ad blocker has about the same impact as &quot;conceding to view a crippled AMP-redesign of the page that doesn&#x27;t even have navigation&quot;.
评论 #10938048 未加载
评论 #10937729 未加载
评论 #10938091 未加载
评论 #10938224 未加载
franze超过 9 年前
ok, just to get this straight<p>if a publisher want to do everything right in todays internet, they need<p><pre><code> * a responsive website * with views for desktop, mobile and tablet * optimized for search, social and conversion * optional: augmented with schema.org * an iphone app (one or more) * an android app * optional: tablet&#x2F;ipad app * facebook channel * twitter channel * youtube channel * pinterest presence * whatsapp presence * snapchat presence * one or more newsletter * constant A&#x2F;B testing </code></pre> now add<p><pre><code> * facebook instant articles * google amp pages </code></pre> did i forget something?<p>yes page bloat, third party crap and webperformance is a serious issue for users and publishers, but solving it with throwing another half baked technology at the publishers will not work.<p>it&#x27;s cHTML all over again <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;C-HTML" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;C-HTML</a><p>AMP solves the right problem with a non solution.
评论 #10938492 未加载
评论 #10938839 未加载
评论 #10938082 未加载
评论 #10939683 未加载
评论 #10938905 未加载
评论 #10937625 未加载
评论 #10938319 未加载
hackercomplex超过 9 年前
Keep in mind that the AMP caching infrastructure will also be able to serve as a tracking platform because it records every single IP address. This effectively grants Google and associates a defacto monopoly in terms of an unblockable mobile tracking platform in a world where ad-blockers are becoming ubiquitous.<p>I think it&#x27;s a smart move on their part actually, but what I assume will eventually happen is other providers will come along and provide a similar free infrastructure but without retaining logs and then everyone will migrate to that. Google will have gotten the ball rolling, and benefited for a number of years from the data, but ultimately people on the web prefer not to be tracked.
评论 #10938956 未加载
评论 #10939580 未加载
评论 #10941926 未加载
评论 #10940286 未加载
fitzwatermellow超过 9 年前
From the F.A.Q:<p><i></i>Accelerated Mobile Pages are just like any other HTML page, but with a limited set of allowed technical functionality that is defined and governed by the open source AMP spec<i></i><p>And from the Spec:<p><i></i>Enable the AMP runtime to manage the loading of external resources, which may slow down the initial render or cause jank. Allow AMP authors to include functionality above and beyond standard HTML, while maintaining the security- and performance-minded requirement that no author-written JavaScript is executed<i></i><p>Appears we won&#x27;t have access to Canvas2D, WebGL, WebRTC, Fetch and other HTML5 Web APIs. AMP&#x27;s subset of declarative elements and caching will be great for longform-y &quot;static&quot; content. The kind of articles I find myself reading more of on Mobile Chrome during down times in transit. Thinking of Medium confessionals and NewYorker dispatches, etc.<p>But how do you implement something like ChartBeat? Snapshots of dynamic chart images and data pre-rendered on the server and pushed out to the cdn? Sort of eliminates the performance benefits of geospatial caching doesn&#x27;t it...<p>I do take heart however in Tony Haile&#x27;s pull quote from the ampproject.org homepage:<p><i></i>The mobile open web experience is terrible and some have suggested it&#x27;s too slow to compete. We can choose to see the mobile open web as a relic of its time and flee to the warm embrace of closed platforms and apps. Or we can say that the open web means something important to the world and if it’s broken it’s our job to fix it. I think we should fix it.<i></i>
digitalclubb超过 9 年前
The web is getting bigger, there is no denying that. People developing responsive sites irresponsibly, adding large images, videos and JavaScript libraries and frameworks.<p>What I don&#x27;t understand is why search engines don&#x27;t punish those individuals with larger pages rather than move everyone to something new? Is this taking us back to the mobile site days?<p>I love the concept of getting core content to the user fast but what is stopping someone adding a 2MB amp-img to their page and then we are right back where we were before?
VeejayRampay超过 9 年前
Past all the considerations of content ownership and all, it seems to be quite the technical feat, the impact on page load is real (or maybe my testing was partial or biased).
评论 #10937419 未加载
manyoso超过 9 年前
Even more centralization and single point of failure. If this continues the web as envisioned will be entirely replaced by a centralized system of walled gardens with big companies controlling access.<p>This is why we need IPFS sooner rather than later.
评论 #10938542 未加载
alexatkeplar超过 9 年前
Big fan of what AMP is doing, but I&#x27;m a little surprised by the statement that:<p>&gt; Today, multiple web metrics providers are on board, including Moat (who partner with Chartbeat), Nielsen, ComScore, Parse.ly, ClickTale, Adobe Analytics<p>As far as I know, our (Snowplow&#x27;s) PR into AMP is the first and only (so far) from a non-GA analytics vendor:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;ampproject&#x2F;amphtml&#x2F;pull&#x2F;1358" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ampproject&#x2F;amphtml&#x2F;pull&#x2F;1358</a><p>Maybe I&#x27;m looking in the wrong place?
r1ch超过 9 年前
In order to make my completely static non-JS site AMP compliant do I have to include the amp JS library or is Google smart enough to realize my site is plenty fast enough as-is?
评论 #10937887 未加载
glossyscr超过 9 年前
I tried the AMP versions mentioned in the article on an iPhone 6 connected to wifi and I am not impressed at all.<p>Something which loads <i>really</i> instantly is D&#x27;s forum, it&#x27;s incredibly how fast it is and it&#x27;s written in D:<p><a href="http:&#x2F;&#x2F;forum.dlang.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;forum.dlang.org&#x2F;</a><p>(I am not into D, just found this thing recently on reddit&#x2F;programming)
tombrossman超过 9 年前
From the article: <i>&quot;...most ad servers (not just Google-owned DFP) will be able to send ads in AMP pages. Some work remains to be done on the formats that will be deemed acceptable in AMP pages.&quot;</i> Deemed acceptable by who, and doesn&#x27;t this indicate it will become another walled garden?
评论 #10940532 未加载
评论 #10941941 未加载
ksk超过 9 年前
From: <a href="https:&#x2F;&#x2F;www.ampproject.org&#x2F;docs&#x2F;support&#x2F;faqs.html" rel="nofollow">https:&#x2F;&#x2F;www.ampproject.org&#x2F;docs&#x2F;support&#x2F;faqs.html</a><p>&gt; The reality is that content can take several seconds to load, or, because the user abandons the slow page, never fully loads at all. Accelerated Mobile Pages are web pages designed to load instantaneously – they are a step towards a better mobile web for all.<p>That&#x27;s kind of dishonest of Google. The &quot;content&quot; doesn&#x27;t take longer to load. The website does, but its because of Ads, pointless JS scripts that are spying on the user and a whole host of things that are _NOT_CONTENT_.<p>In any case, even if creating a new standard, or reduced-HTML, or w&#x2F;e made sense, I&#x27;d be less skeptical if it wasn&#x27;t controlled by an advertising company.
mtgx超过 9 年前
I&#x27;m fine with it long as all content&#x2F;analytics don&#x27;t pass through Google, but I imagine many content sites will be lazy and let Google handle everything.
评论 #10938933 未加载