Saying inline functions in render is bad is like correcting somebody who said "who" to say "whom" when "who" was actually correct.
-
-
I've seen some people argue that this is related to the method living on the prototype vs the instance? Would that affect performance?
-
In the case of “actions”/event listeners though, you’d still need to bind() per instance. Presumably this case can be optimized by VMs.
-
…and I suppose VMs could optimize the same function being created in the same spot over and over, too.
-
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. -
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 …
-
@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. -
Macro concerns in apps (processing too much data, rendering way more than you need), sure.
End of conversation
New conversation -
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.