From a discussion with @deoxxa and @yoshuawuyts: is there any hard data on JS size impacting page load time (via CPU) across devices?
-
-
I believe you can see the parse time in the inspector. It is extremely negligible compared to network.
2 replies 0 retweets 0 likes -
Apart from parse time & network, are there other downsides to big (let's say 1mb gzipped+uglified) JS?
3 replies 0 retweets 0 likes -
Replying to @mipearson
I think the human factor plays into this here: bigger code bases means you'll be relying on others to fix bugs
@KoryNunn@deoxxa1 reply 0 retweets 0 likes -
absolutely. I'd consider that more of a concern personally.
1 reply 0 retweets 0 likes -
Becomes a surface area problem - but what if you judge a 200kb third party lib "safer" than your 20kb own?
2 replies 0 retweets 0 likes
I feel like we're heading towards the agreement that: "it depends" - it feels very much situational @KoryNunn @deoxxa
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.