There's nothing wrong with a Google employee participating in a Google-related discussion (edit: I mean in an HN thread of course), same as with any company. It's nice if they say so, which jefftk did.
Nothing wrong with that, sure, but making comments related to ongoing antitrust litigation against company employing you, while not being any official spokesperson and not having your comments vetted by legal and PR, can be really, really detrimental to one's career if Google decides that it doesn't like your comments. Google is very explicit in its internal trainings to never make any public comments like that unless you're officially empowered to do so. You can say or write anything you want on HN... on the last day at your job.
Yes, in the EU employees are more protected and it is much more limited what an employer are legally allowed to do. In fact they have to prove that your intention was malicious.
No, why would they? He's not whistleblowing. The commenter even admits that he has no context on the link in question and just suspects it's what's being implicated.
It seems possible that in the history of internet forums, some of them might occasionally receive subpoenas because forum members posted something essential to one side's case in some litigation. It also seems possible that some of those forums receiving subpoenas would rather not deal with the burden of responding.
Do I understand correctly that the 1-second delay existed in both AMP and non-AMP case? And later, someone found a way to remove the 1-second delay for AMP since it could be done without a negative UI impact (unlike for the non-AMP case)?
The first article I found about this was https://timkadlec.com/remembers/2018-03-19-how-fast-is-amp-r..., which claims that AMP is actually faster in practice, probably mostly because it encourages good habits. Where are you seeing that it's not faster? This article is from '18 so perhaps there has been a change in how well AMP performs versus the baseline.
Also worth noting that we should probably judge AMP as a whole product. What if it didn't make things faster at all, but did make them predictable and amenable to prerendering? The product is AMP+Cache+Prerendering. Prerendering unquestionably gives huge speed advantages in many scenarios. If you don't have AMP, you don't have prerendering, which means AMP-as-a-product gives significant speed advantages, since it's on the critical path to prerendering. (All of this is of course predicated on the idea that you can't practically prerender normal HTML pages, which perhaps you can, I don't know. I'm just saying if that justification for AMP is correct, it shouldn't necessarily matter that HTML+AMP markup is not faster than HTML markup.)
> mostly because it encourages good habits. Where are you seeing that it's not faster?
You just answered it yourself. If someone follows good habits already, then AMP isn’t faster for them (aside from Google not allowing non-AMP loads to start sooner).
So tl;dr: Traditional HTML+JS ads have always needed an extra second delay to load because of cross-domain UX degredation, but because AMP is pre-caching pages, they're able to pre-cache the ads too?
I believe that the idea is that if the ad is amp, you can be sure it will load fast and not impede the ux of the page, whereas if it's html/js, you can't. It isn't about whether it is cached or not.
But this sounds like a technical limitation that makes sense? This entire comment chain is mostly people interpreting the lawsuit as claiming this was a deliberate artificial delay for business reasons and getting outraged about that, not a technical issue.
It's a little murky. If the status quo comes with a cost, because of practical uncertainty, and you provide an alternative that eliminates the uncertainty (and the cost), and then you use the elimination of the cost to prefer your own method... at minimum, that feels "not fair."
If the top-line goal is to make the page as responsive as possible, I'm a little stumped as to what the alternative would be beyond delaying the loading of arbitrary html and JS. Can you think of a way to load arbitrary HTML immediately and not cause any page responsiveness issues on, say, a three year old Android device?
(Disclosure: I work on ads at Google, and I'm friends with some of the people at the link. Speaking only for myself.)