so… the problem is 0.25 M of the entire site
-
-
Replying to @Pinboard
The root of the problem is lack of testing on actual devices over actual networks. Results in slowness
2 replies 0 retweets 1 like -
Replying to @yoavweiss
with respect, the root of the problem is bloat. You don’t have to test vanilla HTML+CSS over a variety of networks
1 reply 0 retweets 6 likes -
Replying to @Pinboard
I think you're agreeing. You can have an 8mb html doc that renders once the first 20k lands. The type of bloat matters
@yoavweiss3 replies 0 retweets 2 likes -
Replying to @jaffathecake @yoavweiss
I actually strongly disagree. “Bloat is okay as long as it renders quickly” is how we got into this tarpit
1 reply 4 retweets 11 likes -
Replying to @Pinboard @yoavweiss
of course bloat is bad by definition. But I'll take 100k rendering progressively over blocking.
2 replies 0 retweets 0 likes -
Replying to @jaffathecake @yoavweiss
I have become a bloat jihadist because I think people screw up progressive loading too routinely
2 replies 0 retweets 5 likes -
Replying to @Pinboard @yoavweiss
they screw up "don't bloat" routinely too.
1 reply 0 retweets 2 likes -
Replying to @jaffathecake @yoavweiss
absolutely. But my hard line 1) removes ‘but it renders fast’ as an excuse and 2) is really easy to measure
2 replies 0 retweets 2 likes -
I'd argue that "speed of render" is objectively measurable, while "bloat factor" is purely subjective.
1 reply 0 retweets 4 likes
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.