I guess the joke was too complicated? The joke was that it's the JavaScript frameworks that make the site slow, not the back end, even though people always claim back end issues are what makes the web slow. Also, no, experienced web devs all seem to use frameworks!
-
-
Replying to @cmuratori @jordanorelli and
I mean at least if you just look at http://youtube.com , http://facebook.com , https://twitter.com , etc., etc., there is tons of OSS JavaScript getting pulled in there. This is not some "my first web site" thing.
1 reply 0 retweets 3 likes -
I haven't worked on those feeds, so I can only guess as to why, but I spent like six months working on Etsy's feed a few years ago. # of requests is a poor metric; the metrics that are noticeable to users are things like time to first byte and time to first paint.
1 reply 0 retweets 0 likes -
Replying to @jordanorelli @cmuratori and
the page for this thread, for example, shows 4 js requests; my fb feed is 431 and counting. fb feed's time to first paint is 1.64s, the time for this page was, err, 1.71s. so even though fb had 100x the number of requests, time to first paint was similar.
1 reply 0 retweets 0 likes -
Replying to @jordanorelli @cmuratori and
often times lots of little files is used because a cache invalidation is then going to invalidate a small percentage of your total requests, instead of a larger percentage. plus a browser fetches six resources at a time in parallel.
1 reply 0 retweets 0 likes -
Replying to @jordanorelli @cmuratori and
so like the way we had it was every item was a separate resource in a cache, and your feed would request dozens or hundreds of items, and over 95% of them would come from an in-memory cache, and only a small percentage would cause database queries.
1 reply 0 retweets 0 likes -
Replying to @jordanorelli @cmuratori and
when you get an Amazon package, it often has a lot of empty space in it. yes, it's inefficient for the one package, but they do it that way to fill trucks to avoid things sliding around. looking at one request or one page load usually misses the forest through the trees.
1 reply 0 retweets 0 likes -
Replying to @jordanorelli @cmuratori and
the point is games engineering and web scalability are different disciplines and they're wholely unrelated to Amazon crashing on Prime Day, web scalability, AWS, or JS trend fuckery. for all we know, Amazon crashed when people went crazy about the Trump Putin meeting ¯\_(ツ)_/¯
1 reply 0 retweets 2 likes -
Replying to @jordanorelli @cmuratori and
yes i realize i said web scalability is unrelated to web scalability and you know what i'll just live with that because as i said before cache invalidation is hard
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
No no, the problem is that people are saying it's bad. If we all just said it was good, then it would be good!
-
-
Replying to @cmuratori @Jonathan_Blow and
That Trump/Putin meeting seemed to go pretty well though.
0 replies 0 retweets 0 likesThanks. 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.