Google's latest Unitard - Arsenic Manipulation Pathologically
-
AMP - a web component framework to easily create user-first web experiences
Whether you are a publisher, e-commerce company, storyteller, advertiser or email sender, AMP makes it easy to create great experiences on the web. Use AMP to build websites, stories, ads and emails.
For many, reading on the mobile web is a slow, clunky and frustrating experience - but it doesn’t have to be that way. The Accelerated Mobile Pages (AMP) Project is an open source initiative that embodies the vision that publishers can create mobile optimized content once and have it load instantly everywhere.
In a pre-emptive repsonse to the obvious fact that ads (which account for 96% of Google's revenue) are the number one reason pages load slowly, they've included this in their FAQ::
How will advertising work on Accelerated Mobile Pages?
A goal of the Accelerated Mobile Pages Project is to ensure effective ad monetization on the mobile web while embracing a user-centric approach. With that context, the objective is to provide support for a comprehensive range of ad formats, ad networks and technologies in Accelerated Mobile Pages. As part of that, those involved with the project are also engaged in crafting Sustainable Ad Practices to insure that ads in AMP files are fast, safe, compelling and effective for users.
-
TL;DR, they're going to just have ads be horribly ugly text or something so they load faster.
-
-
It gets better if you read the Technical FAQ:
We’ve taken first steps to make ads in AMP HTML better, but we aren’t done yet. AMP HTML doesn’t allow JavaScript so ads cannot be directly embedded – instead they live in sandboxed iframes with no access to the primary document. Relying on iframes solves some of the worst performance pitfalls with ads, in particular with respect to
document.write. We also prioritize ads lower during loading than other content and optimize load timing to avoid jank. Ads in AMP files can still be heavyweight, so there is still a lot of work to do for us.(emphasis added)
So ads are forced to be additional document loads with arbitrary "phat" pages and erase whatever performance benefits they hoped to gain. Fantastic.
Oh, and by the way, no JS, so AMPed Discourse is going to be ... fun.
-
It's a new way to monetize ad spaces: sell ad insurance. For a mere $25 a day, if your ad doesn't get a single view all day, you get $24.95.
-
So ads are forced to be additional document loads with arbitrary "phat" pages and erase whatever performance benefits they hoped to gain. Fantastic.
If--IF--they are in iframes, that should actually help, because then the browser won't have to hold up rendering while waiting for them.
The first browser maker that moved away from the idea, after dynamic rendering became a thing, that the page should come first, and then be reflowed as images and whatnot downloaded, should've been beaten.
-
It gets better if you read the Technical FAQ:
AMP HTML doesn’t allow JavaScript
Moar Lulz:If you go to the Technical FAQ page, it says "The page you are currently reading is an AMP HTML document". But, one of the files that pages loads is https://cdn.ampproject.org/v0.js and if you block the loading of that Javascript file, the Technical FAQ page will not display..
Filed under: AMP HTML doesn't allow Javascript, except when it does
-
https://www.ampproject.org/how-it-works/
The page you are currently reading is an AMP HTML document.
so let me get this straight, you break image loading on your page if javascript is disabled...to make it faster?
-
AMP components may have JavaScript under the hood
The page itself cannot, the components themselves can.
-
As part of that, those involved with the syndicate are also engaged in crafting Sustainable Chocolate Coated Cotton Practices to insure that the chocolate coated cotton in the new cafeteria is delicious, nutritious, irresistible and mandatory.
Filed under: the syndicate makes the profit, and everybody has a share
-
. AMP HTML doesn’t allow JavaScript
I fully endorse this product. Lets do our best to make this work if only to put another nail in Discourse's coffin.
-
-
No JavaScript at all?
So people were abusing scripts to make slow clunky pages, and instead of figuring out how to limit them to important stuff, they just banned them?
-
Let's start using VBScript then.
Filed under: Some people cannot understand "Javascript" and "Client-side Script", and think they're always interchangable.
-
Let's start using VBScript then.
Maybe we should use this new fangled technology called java? That's basically javascript isn't it?
-
@Spanky587 said:
to insure
Shirley they meant to ensure, unless they're entering the insurance space
Are you (as)sure?
-
+1 for Catch-22 reference that isn't the obvious one.
-
Maybe we should use this new fangled technology called java? That's basically javascript isn't it?
It's actually a subset of it, that's why it's got only part of the name
-
This is my favorite part:
<html ⚡>Emoji are now part of your codebase. You're welcome.
-
No JavaScript at all?
So people were abusing scripts to make slow clunky pages, and instead of figuring out how to limit them to important stuff, they just banned them?
People who make slow, clunky pages don't give a shit about users. Which is why AMP HTML will end being just another Google project that quickly disappears.
-
AMP components may have JavaScript under the hood
The page itself cannot, the components themselves can.I find it humorous that it says:
"For a headline, some text and an image, you do not need JS"And yet, the AMP HTML How it Works page, which perfectly fits that description, requires JS or else it won't display. At all.
-
Woah woah woah woah woah. Is that... They're literally using emoji as part of HTML code?
Jesus Christ, why
The Evil Ideas Thread is
-
What are you talking about? It works just fine without JS.
-
Required, in fact. That's how you signal that it's amp-html, not plain html.
-
This is a dangerous precedent.
-
At least say that's the only emoji it uses. Please. Lie to me if you must. Just say that's it.
-
(psst.. you can use
<html amp>instead for one less byte)
-
Of course you can, but if emoji are functionally equivalent and shorter, people will start using them more, and eventually all code will look like
/me rocks back and forth in the corner
it'll be okay...
-
*snipped broken on my machine exposition*
I am going to say "what the fuck is the point of the
opacity:0style in the first place that has to be overriden by JS loaded from a CDN or by a style in a noscript tag?"
-
ignores it
with JS disabled,
Note that they're considering replacing that with blocking JS that sets
opacity: 0.It looks like their ultimatum to the client is "Run our javascript, or run no javascript".
-
Great, so there's something wrong with IE and Chrome on this computer.
Tried it on a second computer at the office and it worked.
Still, my question stands, why even do
opacity:0by default?
-
Why don't we want more code with emoji? Because they're hard to type.
Why won't we start seeing more code with emoji? Because they're hard to type.
It's a problem that solves itself!
A job for Bender (Futurama) – 00:08
— Jan Mart Liewes
-
They're really easy for younger generations.
-
What are you talking about? It works just fine without JS.
If I block https://cdn.ampproject.org/v0.js the page won't load. I get a 404.
-
No repro:
-
lmao it's because chrome doesn't let extensions turn
<noscript>blocks on or off
-
Why won't we start seeing more code with emoji? Because they're hard to type.
It's a problem that solves itself!
Real Life Emoji Keyboard! – 02:13
— Tom Scott
-
Pretty much where we're heading.
-
-
What the actual fuck.
-
Have you young'uns honestly never encountered APL before?
-
Nope. Not me, anyway. Never seen it before, and it looks horrifying.
-
It's one of the few actually-used-for-something languages that make Perl look readable by comparison.
-
Looking at that wiki page, the only readable code in it is a string.
-
-
Tildes, tildes with umlauts, greek letters, arrows...
-
To be fair, with proper rendering support you may see APL source code, so it's arguable whether you'd be any better off.
-
Still, my question stands, why even do opacity:0 by default?
It's hard-wired in Chrome to prevent paint and composite, iirc. By using it directly on the body element they are essentially taking direct control over when the browser does its first render pass.
-
Did you know, you can actually get Chrome to render the
<head>tag and its content with some simple CSS? Those tags are not part of the body ;)
-
Bummer. Don't worry though, I'm sure firefox will catch up soon enough.
APL (programming language) - Wikipedia
