Explained how it works here https://blog.amp.dev/2018/07/23/privacy-and-user-choice-in-amps-software-architecture/ … We're working on making it work for non-AMP content, toohttps://blog.amp.dev/2019/05/22/privacy-preserving-instant-loading-for-all-web-content/ …
-
-
Replying to @fchristant @BrendanEich and
If you argue one should not innovate and be doing the best thing for users because it requires making technology trade-offs, and the solution cannot be immediate be equally distributed through the entire web, then yeah, we'll need to agree to disagree.
1 reply 0 retweets 2 likes -
This Tweet is unavailable.
-
Replying to @drybones_5 @fchristant and
It made things massively faster. https://developers.googleblog.com/2019/08/the-speed-benefit-of-amp-prerendering.html … At the time there was a massive threat that user activity would move entirely into native apps, and AMP providing competitive UX had a small part in making that not happen.
3 replies 0 retweets 1 like -
Replying to @cramforce @drybones_5 and
I still hear of a huge threat from native apps, even with AMP and its search “tying”. This threat seems not obviously true as stated, or solvable by counting APIs added to the web platform. It seems more about OS upgrades & better CSS special forms. I don’t mean to belittle it. +
1 reply 0 retweets 6 likes -
Replying to @BrendanEich @cramforce and
In my experience, there is always a threat. But this doesn’t justify tying or other power moves that won’t get into standards and which finally have antitrust cops on the move. From 2010 on, Parkour, Polymer, etc., to Fugu, the threat and response seen to shift but not deliver. +
2 replies 0 retweets 5 likes -
Replying to @BrendanEich @cramforce and
Good progress has been made but more via incremental work that does make it cross-browser sooner than later. This enables adapting to lessons learned and emergent knowledge, as well as to hardware & network shifts foreseen poorly or missed. Can we de-escalate from emergency talk?
1 reply 1 retweet 6 likes -
Replying to @BrendanEich @cramforce and
It's an emergency. We've been steadily losing on mobile and too many are acculturated to the pace of loss.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @BrendanEich and
Who is the ‘we’ you’re referring to? If you mean Google, I’d probably agree. If you mean users - that’s a big nope from me. Content is still king - how you get it is up to the content provider. Mechanism shouldn’t matter. Web and native can co-exist. This isn’t a one or the other
1 reply 0 retweets 1 like
"we" here is "the web"
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.