2B Pages On Web Now Use Google's AMP, Pages Now Load Twice As Fast (venturebeat.com)
At its developer conference I/O 2017 this week, Google also shared an update on its fast-loading Accelerated Mobile Pages (AMP). The company says that over 900,000 domains on the web have enabled AMP, and over two billion pages now load faster because of it. Taking things forward, Google says AMP access from Google Search is now twice as fast. From a report: Google first unveiled the open source AMP Project in October 2015. Since then, the company has been working hard to add new features and push AMP across not just its own products, but the larger web. Google Search only launched AMP support out of developer preview in September 2016. Eight months later, Google has already cut the time it takes to render content in half. The company explains that this is possible due to several key optimizations made to the Google AMP Cache. These include server-side rendering of AMP components and reducing bandwidth usage from images by 50 percent without affecting the perceived quality. Also helpful was the Brotli compression algorithm, which made it possible to reduce document size by an additional 10 percent in supported browsers (even Edge uses it). Google open-sourced Brotli in September 2015 and considers it a successor to the Zopfli algorithm.
AMP? No thanks. I already have APK and his hosts files in my life speedifing all my intertubes. Zoom zoom zoom!
I think you mean "half as slow".
Twice the spam and half as much time to notice that there is zero content but the top 10 will BLOW YOUR MIND!
I'd gladly wait again to actually get what I am looking for instead of having to click through 20 pages of rubbish only to find out in the end that I got tricked into going to a page that offers anything but what I wanted.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Say bye-bye to brand/domain authority
The Register posts this today, and now Slashdot has the rebuttal.
https://www.theregister.co.uk/2017/05/19/open_source_insider_google_amp_bad_bad_bad/
Seems like an ad blocker should be able to bring similar improvements these days ...
In fact, if we could get ad blockers to also eliminate links that include strings like this, we'd be even FASTER.
You'll never believe what happens next
number 7 will melt your heart
you'll plotz when you see #3
https://www.theregister.co.uk/...
between AMP, Ad Sense, and Chrome native ad blocking, how is google going to avoid MS style anti trust?
You are a cancer on the www.
I use Opera on my Android phone. Apart from having its own (optional) 'acceleration' using Opera's own servers, it's one of the few mainstream browsers on Android that does text reflow (word wrapping) when I zoom in to enlarge the text (most other browsers use WebKit, which no longer supports this). But following a link from a Google search, I get the AMP version of the page, which totally breaks text reflow. I need a couple more taps to get the original version of the page from Google's link bar, which takes much longer than if I'd been served the real page in the first place.
My big problem with the recent browser is that does boot and load too
slow due to hundreds of megabytes in disk and memory.
I don't know what is the shitpile of programmed code of this browser.
5 years ago, it was tens of MBs instead hundreds of MBs of today.
Facebook wants to show the news without the users ever leaving Facebook. Archive.org ignores robots.txt and just hosts everything. Google moves search engine results to their own servers with AMP. Take your grubby fingers off my content, you slimy aggregators! Come up with something yourself if you need more stuff to glue eyeballs to your sites!
It took me forever to try to figure out what the headline was saying. Is that 2B some mistake for "28"? No, that doesn't seem like a very big number. Is there a website that I don't know about called "2B pages on the web"? A google search only comes up with this article. What the hell could 2B mean?
TWO BILLION!!!! Why is that so hard to type?
Headlines are limited in length. Abbreviating "2 Billion" to "2B" saves seven characters that can be used elsewhere. Otherwise, the headline gets chopped off:
It's the same reason Slashdot users use "M$" in comment subjects: to save seven characters off "Microsoft" while recalling Microsoft's history as a publisher of BASIC interpreters.
I honestly read the title as "28 Pages on Web Now Use Google AMP."
I've only ever had problems with Google webpages.
Remember when Gmail used to be SUPER FAST ULTRA HYPER LOADING deluxe?
On a similar machine today, it is sluggish as fuck. (even with the SAME browser, I tested that too)
But why is it slower?
Enclosures. DEEP enclosures more importantly.
Enclosing your code behind layers of wrapper functions is considered the hot new meme of web development today.
Problem is, EVERY SINGLE JS engine sucks hard at working with this sort of JS.
Deep enclosure layers add considerable overhead to JS. Every layer you go deeper, the overhead increases.
This is why libraries like jQuery and such were all slow, because their code was hidden behind generic accessors, which were all wrapped up in deep enclosures and inheritance to boot, talk about slow on top of slow.
Put simply, JavaScript is incapable of delivering this sort of use-case properly.
Worse yet, for some reason people think this actually makes it easier to work with. I... fuck knows what sort of broken brains they have, any time I look at such heavily wrapped JS, it looks terrible. JS is trivial to understand, shit wrapped behind 20 different wrapper languages looks like text vomit. It's as bad as those retards that do all kinds of code-olympics to avoid using GOTO or [insert the new hot hate-meme of the decade]. (I think people hated IF last decade, not sure what this decade of retard-children hate)
This is why Google Wave died. It was created right at the beginning of this shit meme of everyone enclosing code behind so many wrappers.
It was hilariously slow because of this.
And on top of that, it also had a fuckton of event handler abuse everywhere. (another common abuse these days, especially ad trackers that monitor site interaction on TIMERS instead of events)
Being so slow, people quickly left it. All that was left were shitposters and technophiles that love new things for the sake of things. They DID manage to optimize some of the site by refactoring the shitcode it was, but it was already too late.
Web development truly is a cancerous place to be today.
I'm glad I got out.
How much does this really help, though, when the typical site is bloated with:
The interface really stinks, makes it hard to share posts. Speed increase not worth it.
Most sites have a web optimized version that's plenty fast.
The horrible UX provided by AMP is the number one reason I started looking at other browsers on mobile. I believe they made changes to make it less horrible but I never once landed on an AMP page and thought, "What a great layout! I'm glad the removed all the visual cues from the site I was trying to visit!" I moved over to Brave. It has some rough edges but it renders things correctly and I don't feel like someone's trying to force their bad personal design decisions on me.
100% free & combined w/ script stalling you FLY via APK Hosts File Engine 9.0++ SR-7 32/64-bit https://www.google.com/search?hl=en&source=hp&biw=&bih=&q=%22APK+Hosts+File+Engine%22+and+%22start64%22&btnG=Google+Search&gbv=1/
Ads/script & malware rob speed/security/privacy
Hosts add speed (via hardcodes/adblocks), security (vs. bad sites/malware/poisoned dns), reliability (vs. dns down), & anonymity (vs. dns requestlogs/trackers).
Less power/cpu/ram + IO use vs. DNS/routers/addons/antivirus + less security bugs/complexity & faster vs. addons/routers/remote dns!
Avoids DNSChangers in routers/IP settings & dns redirects (99.999% of ISP DNS != patched vs. it) + lightens DNS load & resolves faster from local system RAM!
* Via what u NATIVELY have in the IP stack in FASTER kernelmode!
APK
P.S. - Safe https://www.virustotal.com/en/file/e01211ca36aa02e923f20adee0a3c4f5d5187dc65bdf1c997b3da3c2b0745425/analysis/1433430542/
My first impression of AMP was "the thing that suddenly replaced usable links with garbage so broken I couldn't even scroll down to the body of the text I wanted to read."
Thankfully that has been fixed, but talk about a lousy first impression.
Procrastination Man strikes again!
If your page is on Amp, I will not visit it.
Admittedly my android phone is about 2 years old now, and not a top-end model, but AMP has given me nothing but trouble. From images loading unevenly and causing my screen to jump, unresponsive pages, images/videos cut off and unable to resize (and all the full screen buttons being exclusively on the right side doesnt help) There will be occasional problems like this elsewhere of course, but its so constant a problem that I've been actively avoiding AMP links and more than once have gone to a different search engine or attempted to go to the root site and search from there. Tl;dr: still needs a lot of work.
Maybe Slashdot could use a bit of this. It's the most amazingly painful site when I load it on my phone. The page appears, and then I have to wait for ten seconds while it keeps jumping around before I can start reading. Every time it finishes loading another ad the whole page reformats. That's the sort of garbage AMP is meant to fix.
"I'm too busy to research this and form an educated opinion, but I do have time to tell everyone my uninformed opinion."
Implement it as a simple subset of HTML, a meta-tag and http-header (choose one for your site) to indicate its a amp site. Skip the part with javascript crap, especially skip the part of javascript-crap forced from the google-cdn.
Now everyone can implement in their browsers, newsreaders, whatever a amp-parser, which can parse AMP-HTML really really fast. Further, simple html WITHOUT javascript, with basic inline css and a limit how big images may be (else the amp-browser stops loading) will have really fast transfer times as well.
But no, let's make it google crap and fuck the rest of the world.
See subject: On PC's they're faster vs. adblock http://superuser.com/questions/686041/which-leads-to-faster-browsing-an-ad-blocker-or-an-edited-hosts-file/
APK
P.S.=> Anecdotal bs from UNIDENTIFIABLE anonymous trolls != facts shown above... apk
I'm going to continue using the Host File Engine. Your software is well written, functional. The Host File Engine performs exactly as promised by mmell
his hosts program is actually pretty good by xenotransplant
his hosts tool is actually useful for those cases in which one does indeed want to locally block stuff outright while consuming minimum system resources by alexgieg
(APK's) work, I've flat out said it's good by BronsCon
I've tried his hosts file generating software. It works by bmo
I like your host file system by Karmashock
I find your hosts file admirable by vel-ex-tech
* It's recommended & hosted by Malwarebytes' hpHosts!
APK
P.S.=> See subject: ... Perfectly every time bugfree & bulletproof ACCURATE TO A FAULT output via multithreaded virusproof self-checking SINGLE .exe (no 3rd party libs beyond NTAPI) uncrashable program protecting hosts beyond Windows' WFP/SFP (that speeds you up & secures you simultaneously (only one that does))... apk
Don't make THAT mistake - BobTheSuperWEASEL did & I blew him away on it here https://politics.slashdot.org/comments.pl?sid=10458715&cid=54192877/ & my 8 replies beneath him made him EAT HIS WORDS as always vs. me.
* What do you mean by "plants"?
IF you mean they're my "sockpuppet" FAKE accounts, boy, are YOU wrong!
(I don't do that crap - I don't have to resort to such lameness, I have actual GOOD results & reviews for my work & it'd make me as bad as other "FAKE NAME for FAKE LIVES"'ers as I call them around here - I won't become what I can't stand personally).
APK
P.S.=> They're real registered /.'ers (some of whom don't even get along w/ me well but @ least they're honest)... apk