Viewing profile — fchristant

hi, author here. "This blog post was tough to read! Seems to have capped out at a 6th grade level." I'm not a native speaker, and this is the best I can do. I was expecting less th…

hi, author here, and thanks. I have a straightforward answer. Build incredible PWAs that users will miss out on on iOS, because it has partial support at best. You'd still serve 80…

hi, author checking in. Just doubling down on my statement. I've seen hundreds of discussions and flame wars on browser performance, RAM usage, the ability to keep open 200 tabs. I…

hi, I'm the author. Agree with your point when you read it like that, so I'll clarify what I meant. "Compatible with the web" in the context of this article means compatible with t…

hi, author of the article checking in. Thanks for commenting in the open from Mozilla's perspective, even if its just one voice, it's much appreciated. I agree that Firefox will re…

The main objection I have to AMP is preloading, it is a demonstratable case of an unfair level playing field, that cannot be excused by any technical reason. On slow 3G, where perf…

Agree with all of that, indeed it is a longshot. This leaves us pretty much with the 'awareness' option. I'm not hopeful. Even if you're lucky to have a person in your organization…

We have to differentiate between prefetching from search and prefetching from the actual page being opened. Google CAN preload arbitrary websites. They fully load your website, JS …

hi, I'm the author of the article. I have no idea how to stop it. Bad press doesn't seem to matter, as this has been around for years. One longshot I could think of is reporting it…

You're missing the entire point. It is fine to have a framework like AMP that puts up technical constraints leading to a performance-friendly web page. The problem is the cache and…