(the bars are raw/cached/canonical, and the groups on the X axis are min/max/median/90th)
How fast is AMP really?
21–30 of 167 posts
Re: How fast is AMP really?
#22A suggestion for the author: Please avoid commas (or dots) as thousands separators. My brain parses "4,604ms" as "about four milliseconds", which would be amazing, but is very much not what you mean. ISO recommends half-width spaces as thousands separators to avoid this kind of confusion. Also, I think thousands separators can just be skipped if your numbers are only four or five digits wide.
IMO we should introduce locale-dependent number formatting to HTML.
Re: How fast is AMP really?
#23A suggestion for the author: Please avoid commas (or dots) as thousands separators. My brain parses "4,604ms" as "about four milliseconds", which would be amazing, but is very much not what you mean. ISO recommends half-width spaces as thousands separators to avoid this kind of confusion. Also, I think thousands separators can just be skipped if your numbers are only four or five digits wide.
IMO we should introduce locale-dependent number formatting to HTML.
Re: How fast is AMP really?
#24A very low quality article. The whole point of AMP is to define a restricted subset of HTML that is safe to prerender and still provide working analytics to the publisher. When you prerender, the advantage of AMP is substantial as it is impossible to beat a user experience of instant, which is why users prefer it and why publishers go through the trouble of implementing two web versions of their web pages (in additio…
Publishers go through the trouble in order to get the boost in Google's rankings. As an iOS user I find AMP to be quite buggy, and AMP versions of pages like reddit are borderline non-functional. I don't prefer it at all.
Disc: Googler but nowhere close to AMP.
Re: How fast is AMP really?
#25How fast could google.com be if they trimmed the JS fat?
Re: How fast is AMP really?
#26So basically Google could get 90% of what AMP provides without AMP itself, because the magic is in the caching and forcibly reducing the ad junk the page loads. Does that about sum it up?
Yes, except how do you propose to implement caching and stripping out the ad junk without AMP?
now, seriously, I do that just fine with an ad blocker.
Re: How fast is AMP really?
#27Re: How fast is AMP really?
#28How fast could google.com be if they trimmed the JS fat?
The non-JS version takes 1/3 loading time of the JS version: http://www.webpagetest.org/result/180402_0J_6a3f29516e9a8bcf... vs http://www.webpagetest.org/result/180402_Z3_1bd3e53e1be2668c...
Re: How fast is AMP really?
#29Answer: not as fast as the D lang forums. https://forum.dlang.org/
Wow, that site indeed feels fast! Is there a writeup about how it’s done?
Also, it runs on SQLite. I found that the most surprising of all.
Web development in D is incredibly fun. I love that I can compile HTML templates into machine code (which of courses catches template errors as compiler errors), I love how fast the result is, I love that there is a very lively collection of D packages around web development. In fact, the D package manager, dub, started as a package manager for Vibe.d, the main D web framework.
Re: How fast is AMP really?
#30A suggestion for the author: Please avoid commas (or dots) as thousands separators. My brain parses "4,604ms" as "about four milliseconds", which would be amazing, but is very much not what you mean. ISO recommends half-width spaces as thousands separators to avoid this kind of confusion. Also, I think thousands separators can just be skipped if your numbers are only four or five digits wide.
You might as well say 'please ignore the standards of your country in favour of mine.'
Are you really not aware that this is the standard in Europe?