11–20 of 52 posts
WordPress is schizophrenic Oh hey let's load up your webpages with all this cr*p by default, tons of javascript, css, external files, fonts, headers, footers useless markup. Oh hey, let's use this plugin to strip all that out. How about not putting it in there in the first place.
Are AMP and HTTP/2 best practices contradictory to one another?
Are AMP and HTTP/2 best practices contradictory to one another?
As I've noted elsewhere: to use AMP, you must load JavaScript from the AMP CDN, which is operated by Google. So you are handing over the security of your site and your user's privacy to them. From https://github.com/ampproject/amphtml/blob/master/spec/amp-h... : > The AMP runtime is loaded via the mandatory " rel="nofollow">https://cdn.ampproject.org/v0.js"> tag in the AMP document .
AMP is just a subset existing web technologies. It's entirely possible to build a page that loads just as fast or faster, without loading the AMP scripts, if you so choose. But AMP greatly simplifies the process, which is what developers need, and the script enforces the limitations necessary to make the page load and render quickly, which users love. Right now AMP is under heavy development and lots of changes are b…
Want to embed content from another site? Great! You can choose from , , , , or .
Building an advertising startup? Hooray! I hope you're one of the dozen whitelisted ad networks that allows.
In Russia or China? Maybe Google will deign to implement and if we're sufficiently humble.
This is not the Web I want.
I've got Ublock Origin and funnily enough, the LongReads example AMP page loads only marginally faster than the "full" one. I don't understand why people can't just remove all of the crap from their main pages rather than relying on this Google-sponsored equivalent?
Earlier quoted context omitted.
AMP is just a subset existing web technologies. It's entirely possible to build a page that loads just as fast or faster, without loading the AMP scripts, if you so choose. But AMP greatly simplifies the process, which is what developers need, and the script enforces the limitations necessary to make the page load and render quickly, which users love. Right now AMP is under heavy development and lots of changes are b…
AMP erects walls around the Open Web and enshrines Google as the gatekeeper. Want to embed content from another site? Great! You can choose from , , , , or . Building an advertising startup? Hooray! I hope you're one of the dozen whitelisted ad networks that allows. In Russia or China? Maybe Google will deign to implement and if we're sufficiently humble. This is not the Web I want.
Earlier quoted context omitted.
AMP is just a subset existing web technologies. It's entirely possible to build a page that loads just as fast or faster, without loading the AMP scripts, if you so choose. But AMP greatly simplifies the process, which is what developers need, and the script enforces the limitations necessary to make the page load and render quickly, which users love. Right now AMP is under heavy development and lots of changes are b…
AMP erects walls around the Open Web and enshrines Google as the gatekeeper. Want to embed content from another site? Great! You can choose from , , , , or . Building an advertising startup? Hooray! I hope you're one of the dozen whitelisted ad networks that allows. In Russia or China? Maybe Google will deign to implement and if we're sufficiently humble. This is not the Web I want.
And please, please tell me what's wrong with using e.g. ? It's just a web component! All it does is what you want it to do, and if it doesn't do what you want then either you shouldn't do that, or you can just submit a PR.
The whole point of AMP is 1) make sure the developer doesn't do anything that'll make the page load unnecessarily slowly or repaint/relayout unnecessarily and 2) make it way easier for the developer to accomplish #1 because all you have to do is type .
AMP is no different from, say, jQuery, or React, or Angular. It's a different way of doing things, but it's not a "gatekeeper" on the web. It's just another option, one more tool in your belt, if you so choose.
As I've noted elsewhere: to use AMP, you must load JavaScript from the AMP CDN, which is operated by Google. So you are handing over the security of your site and your user's privacy to them. From https://github.com/ampproject/amphtml/blob/master/spec/amp-h... : > The AMP runtime is loaded via the mandatory " rel="nofollow">https://cdn.ampproject.org/v0.js"> tag in the AMP document .
When one company such as Facebook decides to launch a very privacy-intrusive service, people are like "Oh, no! We must support Google's very privacy intrusive-service so Facebook doesn't win!" - just like people saying "we must not let the pro-corporate Republicans win, so we must support the pro-corporate Democrats".
It's such a race to the bottom. How about we reject both? (in both cases).
Earlier quoted context omitted.
AMP erects walls around the Open Web and enshrines Google as the gatekeeper. Want to embed content from another site? Great! You can choose from , , , , or . Building an advertising startup? Hooray! I hope you're one of the dozen whitelisted ad networks that allows. In Russia or China? Maybe Google will deign to implement and if we're sufficiently humble. This is not the Web I want.
The project is open source and open to contributions from anyone. Every single time this comes up the project contributors have said that they will gladly modify to support any network they can. They're also constantly developing new components to fill in the gaps for other embeddable services. You want ? Submit a PR! Open an issue! It's open source! And please, please tell me what's wrong with using e.g. ? It's just…
Who gets to decide which pull requests get accepted? What if I wanted to create an amp component for my network with a userbase of two people?
http://searchengineland.com/get-started-accelerated-mobile-p...
"More than likely, simply installing the WordPress plugin will not be enough, and you will have to go through and validate all of the pages you’d like to benefit from Accelerated Mobile Pages.
Depending on how your articles are formatted, you may need to make some changes in order to get the AMP pages to validate. The most common problems I personally experienced were with specifying height and width attributes for images and correcting old YouTube embed codes that weren’t using https."