it's worth pointing out, I get painted as a naive reimplementor, but this is good reason to keep polyfills tiny.
-
-
Replying to @_developit @treshugart
I don't think you're naive, but I'm not sure your obsession with smallness is healthy :-)
1 reply 0 retweets 2 likes -
Replying to @AdamRackis @treshugart
probably quite unhealthy, but honestly I don't see anyone else pushing for it and it disappoints me.
4 replies 0 retweets 16 likes -
Replying to @_developit @treshugart
I don't think it matters much, honestly. That 40k of React will prolly be cached and served from a SW.
3 replies 0 retweets 0 likes -
Replying to @AdamRackis @_developit
: not on first load it won't, and you eval *every* time. Size matters.
3 replies 0 retweets 8 likes -
But parse time is usually <<< download time, right? Esp on mobile?
3 replies 0 retweets 0 likes -
Replying to @AdamRackis @_developit
: and both are exacerbated by size. CPU is biggest parse factor
2 replies 0 retweets 2 likes -
There a standard scaling you're aware of? ie, for each unit of size, parsing _ fraction of download?
2 replies 0 retweets 0 likes -
Replying to @AdamRackis @_developit
:
@addyosmani did parse time work recently. Haven't seen a ratio. Might be interesting!3 replies 0 retweets 4 likes -
Replying to @slightlylate @AdamRackis and
parsing time is not a function of size, a complex small file can hurt equally
2 replies 0 retweets 0 likes
: that's a detail I omitted for the sake of brevity
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.