First, as Sam discussed (https://www.youtube.com/watch?v=5auGeCM0knQ …) and HTTP Archive confirms (http://httparchive.org/trends.php ), we're sending more script every year
-
-
Replying to @slightlylate
This wouldn't be a problem if the devices we were sending it to and the networks we send it over could handle it & remain responsive.
1 reply 0 retweets 3 likes -
Replying to @slightlylate
There's huge value in script! It's our collective escape hatch and it's awesome...but it comes with great responsibility.
2 replies 1 retweet 9 likes -
Replying to @slightlylate
Mobile is hard. Harder than it looks. When we ported Chrome to Android, it took a *long* time to get a handle on mobile's limits & adapt
1 reply 1 retweet 5 likes -
Replying to @slightlylate
E.g., a multi-process architecture is easily affordable on desktop (RAM, IPC overhead, etc.). Mobile? Not so much.
1 reply 0 retweets 2 likes -
Replying to @slightlylate
So for all of us coming from desktop to mobile, a change in outlook is crucial. Mobile is much less forgiving.
1 reply 1 retweet 3 likes -
Replying to @slightlylate
But just like desktop, our collective goal is to deliver great experiences to users. That's *always* Job #1. And that job just got harder.
2 replies 0 retweets 3 likes -
Replying to @slightlylate
If we don't adapt we won't succeed. The transition is hard! It has been hard for us too; see, e.g.: http://v8project.blogspot.com/2016/10/fall-cleaning-optimizing-v8-memory.html?m=1 …
1 reply 0 retweets 2 likes -
Replying to @slightlylate
So all of us working on the web are learning mobile, browser engineers included, and it isn't easy.
1 reply 0 retweets 3 likes -
Replying to @slightlylate
My colleague
@drufball reminder me of our own long road, and he's dead on: we're all in this together.1 reply 0 retweets 2 likes
And if we're sounding the alarm, it's because we're only slightly ahead.
-
-
Replying to @slightlylate
The reality is that if our responsibility is to end users then we need to change our approach when the constraints change.
1 reply 1 retweet 5 likes -
Replying to @slightlylate
Now, what I didn't do yesterday is to pull up traces from sites or frameworks that haven't made the change.
1 reply 0 retweets 2 likes - 12 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.