3 ms·
Updating a hundred on-screen elements requires special performance optimizations - are we back in 1985? Articles like this tend to confirm my prejudice that mos
by pavlov 12y ago
Updating a hundred on-screen elements requires special performance optimizations - are we back in 1985? Articles like this tend to confirm my prejudice that most new JavaScript frameworks are useless for real-world software.
I know that's not the full picture, but what I don't understand is why you would build something on these technologies when the practical performance ceiling of the framework magic is so achingly low, and once you hit it, you'll be spending much of your time fighting the framework that was supposed to be boosting your work.
- dignati 12y agoThe implementation feels like a complete overkill to me. The most obvious one being the Column component. I don't think you can judge the whole library on one instance where it's used (seemingly) without much experience and with an over the top approach.
- hcarvalhoalves 12y agoThat's not a performance optimization, you're supposed to implement "shouldComponentUpdate" on React components. Not sure what you mean by "spending time fighting the framework" either, it's one line of logic. In case you missed the point of the article: it's not that you have to implement that method, but that you've to be careful implementing it because JS has mutable objects by default. Also, when he's talking about "render" it's not a simple rasterization, it's actually manipulating the document tree and triggering a layout engine. Apples and oranges. If he wanted speed he could render his graphics on a canvas, then your 1985 comparison would make sense. Let's educate ourselves about the subject before venting?