8 ms·
Faster AMP on the Origin: AMP and SSR
- fartcannon 7y agoNo thanks! Is there a term for creating something with two purposes? Where one seemingly benevolent purpose hides a malevolent one?
- predakanga 7y agoA Trojan horse?
- ben_jones 7y agoIs it a Trojan Horse when the strategy is so blatantly obviously? Google exists to turn this path: User -> Internet -> Website Into User -> Google -> Internet -> Google -> Website So that they can sell more ads.
- cpeterso 7y agoAccording to a recent study of Google US web searches in 2019 Q1: Received 150+ Billion searches Solved 48.96% of those searches without a click Sent 6.01% of all searches (~12% of search clicks) to websites owned by Alphabet, Google’s parent company Directed a click to non-Alphabet-owned websites (aka, the rest of the web) after 45.03% queries https://sparktoro.com/blog/how-much-of-googles-search-traffic-is-left-for-anyone-but-themselves/ https://sparktoro.com/blog/how-much-of-googles-search-traffi...
- predakanga 7y agoPerhaps a poisoned chalice, then?
- Chirael 7y agoI’m not sure about a term, but the Underhanded C Contest [1] is (another) great example. [1] http://www.underhanded-c.org/ http://www.underhanded-c.org/
- cco 7y agoWouldn't that be a Trojan horse?
- craftinator 7y ago"Evil"? Is that the word you're searching for? Here, let's use it in a sentence for context: "Google is Evil." Yeah, that seems like it fits the billet!
- thelittleone 7y agoPerhaps a 'ruse' or 'slight of hand'?
- correct_horse 7y agoStrangely, it is correctly spelled ”sleight of hand”
- tannhaeuser 7y agoPull a Google? I mean many of their actions, on the surface, could be euphemistically called "helping humanity" when in reality they're only helping Google. Penalizing non-https sites: "we're making the web more secure" - and lock out advertisement surface to the benefit of our ads quasi-monopoly (admittedly, a weak case though) Android Stagefreight bug: "we're disabling MMS to protect Android users" - and by the way close a channel for easy publishing with carrier billing that is part of the highly regulated 3G/4G stack HTML5: "we're advancing the web and make it fully portable" - and also capture HTML standardization and make it so overcomplicated and never-ending that even MS (and long-time pioneer Opera) are forced-out of producing web browsers alltogether
- buboard 7y agoAmpification
- greyskull 7y agoI don't fully understand the implications here, and I know I'm oversimplifying given the SSR half, but I find it amusing that part of this feature is "remove the code we told you to add".
- londons_explore 7y agoSo AMP is designed to be so so fast, and yet has such a big JavaScript library attached that we need to process the content twice (once in a server-side render, and then again when the client side JavaScript loads)? Anyone fancy going through the AMP library and inspecting it for cruft?
- dkh 7y agoI mean, there are valid concerns over the ethics or intentions behind AMP, but let’s not kid ourselves—it’s definitely damn fast to load. Say what you will about the implications or whatever, but they nailed it in a technical performance sense.
- dmitriid 7y agoThey didn’t. It only loads fast because tgey aggressively preload AMP scripts when you search. A cold load is hardly performant.
- boromisp 7y agoBut that's the point. AMP makes preloading feasible by making it safe.
- manigandham 7y agoAny HTML page can be preloaded. It's even built into modern browsers.
- londons_explore 7y agoGoogle's entire reason for not using the browser preload function is is violates the users privacy - the site gets to know the users cookies and IP even if they never end up visiting. It's a legit excuse, but not enough if a privacy leak in my opinion to slow down everyone's browsing substantially.
- 7y ago
- londons_explore 7y agoTake a look at Google's AMP script: https://www.google.com/xjs/_/js/k=xjs.av.en.1ic8JaUStX4.O/m=jsa,r,d,hsm,ampsa,amp,tnqaT/am=AACAAORCDwDgqwFWAg/d=1/br=1/rs=ACT90oFDGnudWjXLeDH-NewC5hLtO_NGLw https://www.google.com/xjs/_/js/k=xjs.av.en.1ic8JaUStX4.O/m=... Ask yourself... Is that really the minimum amount of script needed to render a basic fast text and images only webpage? Notice the handcoded crypto functions? Notice the copious numbers of debugging functions and log messages and error messages? Notice the large numbers of copyright notices and complete license texts. This stuff, if Google's dream comes to fruition, will be downloaded billions of times per day. For every byte of cruft in this file, an ethernet cable needs to be installed/upgraded somewhere. We shouldn't let Google get away with such massive inefficiency in the name of efficiency.
- IanCal 7y agoSurely it should be downloaded rarely and cached heavily?
- technion 7y agoCheck the advertised site, https://amp.dev/ https://amp.dev/, and look at the headers for v0.js. I'm seeing an "expires" tag of "now", a cache-control header of 'private' and 'max-age' of 50 minutes. You'll also see the 105KB Javascript used to support animated gifs, 46KB amp-bind which allows documents to "add interactivity", and several others.
- snek 7y agoThe sad truth is that Google's goal isn't efficiency, it is keeping people on Google's property. The best way to do this is to make people package their websites into little bundles that are safe for Google to preload. They're even working on a way to capture sites that don't want to invest in AMP (signed exchanges).
- skybrian 7y agoAn aside: one interesting thing about this is that Google's lawyers believe that copyright notices are required in minified JavaScript, and other people don't. Who's right? Is everyone else breaking copyright agreements?
- dmitriid 7y agoIt’s called HTML. Google reinvents HTML and calls it an amazing innovation.
- craftinator 7y agoFavorite excerpt: " AMP SSR is for everyone If you publish AMP pages, you should publish server-side-rendered AMP pages. Similar to minifying your HTML or CSS, running AMP Optimizer or the Go transformers should be a normal part of your build / rendering chain. The improved rendering performance makes a big difference in FCP times, but more importantly, in the user experience. " Other than being the most heavy handed, imperative/authoritarian style call to arms I've seen, the part of this that really bakes my cake is "makes a big difference... in the user experience." Ya know what makes the experience of visiting my website great for a user? When they actually visit MY website. It's like, the single most fundamental part of a website visiting experience. When their browser and my server host kanoodle around in cyber space together, instead of having some creepy cuckold experience involving Google's server. So I'm thinking that AMP, and all derivative technologies, should really make like 'Google Health' and retire to the trash bin.
- codegladiator 7y agoMake your site fast so that Google can avoid the traffic to your fast site.
- dvt 7y ago> It doesn’t make sense to hand-write SSR’d AMP. Instead, use a tool to automatically transform your AMP files into a SSR’d version, like a compiler would. "Compiling HTML" would've been Star Trekian techo-babble a few years ago. And yet, here we are, where a straight-faced Google developer advocate is telling us to do just that. Should we laugh or should we cry?
- NetOpWibby 7y agoI look forward to never using this nonsense.
- RobLach 7y agoEvery developer second put into AMP is a waste of cosmic resources.
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- asadkn 7y agoIt's just sad that enormous amount of developer resources are being wasted into a tech which should have been used for the standard web instead. It's not just the developer hours put into the AMP project itself. Thanks to all the SEO blogs, every site out there has to wasted resources into an AMP implementation. The days of maintaining two versions of a website - a "mobile version" (in AMP) and the normal - are back again. Takes me back to the WAP days (not saying it's that bad). Then there are those that are going AMP-only - getting locked into AMP and all the excessive-yet-limited JS baggage (try building a full-fledged site and you will have a lot of AMP JS). JS compilation and execution isn't cheap on phones either. I sure as hell can make faster-rendering sites without that AMP bloat that can compete despite their prefetch. This proprietary tech isn't helpful and is a massive dev resource sink. And let's not kid ourselves, there were many better ways for Google to prioritize and encourage speedy websites.
- sverige 7y ago>And let's not kid ourselves, there were many better ways for Google to prioritize and encourage speedy websites. That's not the goal, though. Better tracking of your social graph is the goal of AMP. It's like alt.test to see how fast your link propagates, and where it goes. Useful information for influencing you and others.
- lern_too_spel 7y agoWith signed exchanges, they won't have any information about when people share AMP cache links, so that conspiracy theory doesn't work.
- madeofpalk 7y ago> wasted into a tech which should have been used for the standard web instead. But its all just javascript, html, and css. It is the open web. They're also taking bits, like Signed Exchanges, to the standards bodies to make then "standard web" as well.
- amluto 7y ago> With this attribute being set, the validator treats SSR’d AMP as valid AMP. SSR’d AMP optimizations break the rules of the AMP spec, hence making the document invalid, which is why it’s necessary to indicate this case with this new flag. With the flag and the optimizations both being in place, the document is considered valid and you’re good to go. Wait, does this mean that websites could serve plain HTML but set this flag and this avoid being penalized by Google? Win!