Breaks shouldComponentUpdate, PureComponent's strict equality checks, but lots of devs never use those in the first place.
-
-
Replying to @cvitullo @ryanflorence
Ok. I think it's probably more of a readability and maintainability hazard in some cases, but "no inline funcs" is like saying "no use of +"
1 reply 0 retweets 0 likes -
I think the problem is that it defeats the JIT and leads to more allocation/GC.
2 replies 0 retweets 0 likes -
Stuff you do in your own components is almost never the hot path. I don't want to say never but it's basically never.
1 reply 1 retweet 4 likes -
I've seen some people argue that this is related to the method living on the prototype vs the instance? Would that affect performance?
1 reply 0 retweets 0 likes -
Replying to @15lettermax @wycats and
In the case of “actions”/event listeners though, you’d still need to bind() per instance. Presumably this case can be optimized by VMs.
1 reply 0 retweets 1 like -
Replying to @tomdale @15lettermax and
…and I suppose VMs could optimize the same function being created in the same spot over and over, too.
1 reply 0 retweets 1 like -
Replying to @tomdale @15lettermax and
My philosophy is to write clear code, only worry if it appears in profiles, and otherwise bet on
@bmeurer & team’s ability to work miracles.1 reply 0 retweets 10 likes -
Replying to @tomdale @15lettermax and
Have you ever tried loading your site on one of these? https://www.amazon.co.uk/dp/B01H6MMT08/ref=cm_sw_r_cp_apa_P-rXzbG03X731 …
1 reply 0 retweets 0 likes -
@tomdale's comment does *not* apply to framework code. I've never personally seen this kind of micro concern in app code be the bottleneck.2 replies 0 retweets 0 likes
Macro concerns in apps (processing too much data, rendering way more than you need), sure.
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.