3 ms·
Adding 1,200 image components to a web app and never cleaning up the ones that aren't visible is a poor approach to building a mobile web application. It doesn
by Offler 11y ago
Adding 1,200 image components to a web app and never cleaning up the ones that aren't visible is a poor approach to building a mobile web application.
It doesn't matter what technology you use, it's a bad idea.
So he's basically tested the performance of a badly architected application.
- JDDunn9 11y agoKind of like how React benchmarks like to create tables with hundreds of rows and dozens of columns to test against other frameworks?
- Offler 11y agoYou mean a grid? A component one is often asked to add to web applications for businesses. I've added 4 in the last week alone to apps I've worked on. It's bread and butter stuff.
- JDDunn9 11y agoYou shouldn't be making large grids for the web. Terrible practice. You should paginate.
- Offler 11y agoI'm not sure why it's terrible practice, the only reason I can think of is a performance one. As I said earlier in the thread though that's only a problem if you create infinite lists and never clean up after yourself. The correct way to design such components would be to only create DOM for elements in view. Which is why this test is flawed.