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.
Since then, the CPU trends did every we feared and web use on mobile cratered -- in part because the web has depended too much on JS to be usably fast.
-
-
Mozilla was on track to help developers close the capability gap (via proprietary FFOS APIs, but direction was right); need both fast and powerful enough (and installable + discovery) to compete
-
"was". :-|
- 2 more replies
New conversation -
-
-
Mobile-UX CSS special forms are high level remedy for the "too much JS" diagnosis. The iPhone 1 required fast -webkit-* innovation for the Web to be the app platform (before games forced native ~8 months later). Seems to me we should've focused more on CSS than JS stuff like O.o.
-
Some of that happened during FFOS (will-change in CSS, maybe scroll snapping but I'm not sure of the timeline). Huge issue is that there is still no great mobile-first framework, and I'm not sure anyone knows what it would look like. In a way we need *less* choice for devs.
End of conversation
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.