3 ms·
I’ve got to be honest I thought this was the right take but I doubt it now. At least with React. Ive been doing performance on a large app now for months and JS
by nwienert 7y ago
I’ve got to be honest I thought this was the right take but I doubt it now. At least with React. Ive been doing performance on a large app now for months and JS is very often the problem. If you’re re-rendering anything that’s more than a few components wide and a few deep, say 20-40 in total, you’re already over your frame (16ms) budget. To me that’s insane. You can’t render more than 20 components at a time? And this is using a really fast computer. I almost can’t believe it. But often just the logic for a single component that’s a few levels deep takes 4ms. I really do feel that should be about 10x faster but for some reason it isn’t.
- around_here 7y agoYou probably need to learn how do either design a better app, or write better react if you’ve got that much of the DOM updating at once.
- nwienert 7y agoA computer shouldn't struggle updating 30 smaller components. It's not DOM I'm talking about it's React, so not sure you even understood me. I've written more React than most people, and am very intimately familiar with the internals, optimization and more. With enough effort you can usually mitigate most of it, but I'm going as far as doing static compilation optimizations just to get it to feel good.