4 ms·
I think the 5% was a metaphor for how the org is barely able to utilize its resources. Also wouldn't React JS/TS be an instance where you are fully utilizing r
by ericmcer 4y ago
I think the 5% was a metaphor for how the org is barely able to utilize its resources.
Also wouldn't React JS/TS be an instance where you are fully utilizing resources? Not from a raw machine performance standpoint, but from a developer efficiency standpoint. Using nested for loops instead of a series of JS array functions is way more efficient but it is not even close to worth it. Machines are so powerful these days also that sacrificing readability/maintainability for performance doesn't really make sense to me.
- leeoniya 4y ago> Using nested for loops instead of a series of JS array functions is way more efficient but it is not even close to worth it. i work with canvas rendering and 2M-datapoint arrays, so for me it's almost always worth it. but yes, for < 1K elements it isn't. i wrote a 4x faster version of _.groupBy() recently to process our datasets. is a hand-rolled function worth it for 100 elements? not really, but that's not our use case. so, as with everything in life, it depends!
- dorolow 4y agoSure if you work on something where performance doesn't matter
- fsdjkflsjfsoij 4y ago> but it is not even close to worth it It's often extremely worth it. Most people don't profile though and don't care that their web apps are horrendously inefficient at almost every level.