The data I shared in this talk keeps me up at night. The web is going gangbusters on desktop -- but it's dying, *actually dying*, on mobile, where users now live. Why? Sites built for desktop shoehorn'd into phones & policies that undermine browser choice + web competitiveness.https://twitter.com/FronteersConf/status/1181295096752492550 …
-
-
"teams turn on NSM to provide guardrails, ensuring ... devs do not stay from the golden path". Guardrails and badges are nice, but to make NSM a real goal for dev teams, there must be significant incentives, e.g. NSM sites appear first in search results. Would Google go there?
-
The point of the opt in is to help unlock clear incentives, ala the TLS transition.
- 3 more replies
New conversation -
-
-
We really need a replacement to SPA architecture. That's at the very root of the problem but no one wants to talk about it, admit it.
-
@sil's brilliant talk from@JSCampRo goes into this and how Potals will deliver us from script. A real must-see: https://kryogenix.org/code/dont-need-that-js/ … - 4 more replies
New conversation -
-
-
I love the proposal!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
An idea: common libs and frameworks "built in" into browsers, updated async in background, and accessible as Built-in Modules (like KV Storage). This could significantly reduce per-site download & parsing overhead, especially given the realities of double-keyed caches.
-
We've been talking about some kind of built-in cache for a long while. Haven't yet figure out a way to make it so it would not significantly increase the default download size and introduce friction against innovation.
- 8 more replies
New conversation -
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.