I feel like there's some Suze Orman happening in my timeline. People coming to grips w/ cost of their abstractions for the first time.
-
-
Replying to @slightlylate
Do your framework and tools cause your app to load in more than 5s on a 3G connection on real hardware? If "yes", YOU CANNOT AFFORD THEM.
5 replies 19 retweets 30 likes -
Replying to @slightlylate
Do you think frameworks are the main limitation here? In my experience, it's just caring that's the limitation.
2 replies 1 retweet 3 likes -
Replying to @asolove @slightlylate
Most slow sites that use React/Ember just don't have good CDN, cache, or code splitting setups. Frameworks don't prevent that.
1 reply 0 retweets 1 like -
Replying to @asolove @slightlylate
I appreciate concerns about raw network/execution time. But most sites aren't close to that being their biggest problem.
1 reply 0 retweets 1 like -
Replying to @asolove @slightlylate
For most sites, a good http2 CDN with server-push would make them far faster than a from-scratch rewrite in hand-optimized js.
2 replies 0 retweets 0 likes -
Replying to @asolove
: what I'm seeing in traces is that these things are CPU bound. It's about how much script gets loaded and when.
3 replies 0 retweets 4 likes -
Replying to @slightlylate
: H/2 only helps when you're sending lots of smaller modules. I'm seeing huge roll-ups as the default. Totally screws perf.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @asolove
It's why chrome is writing a new javascript interpreter, because people are shoving SO MUCH CODE in, on the average
1 reply 0 retweets 0 likes
: sort of? Interpreter helps w/ memory use. Most devices are constrained that way.
-
-
Replying to @slightlylate @asolove
I know the target is memory use reductions, but simplifying the js->bytecode pipeline will help with code throughput
1 reply 0 retweets 0 likes -
Replying to @Aranjedeath
: sort of. It's complicated. Interpreter will run w/ --no-lazy. Means we'll process more code, but only once (on avg).
1 reply 0 retweets 1 like - 4 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.