← Back to context

Comment by lucideer

2 years ago

> if this becomes a frequent issue

This becomes a frequent issue in any app at scale.

If your app is at a small enough scale that it doesn't run into this issue, I would not recommend using a framework: just use vanillajs &/or some modular utility components.

If you're working on a small app & want to do it in a framework because you anticipate scale, use one with key support.

13 comments

lucideer

Reply
tipiirai  2 years ago

Hardly a frequent issue. I use zero apps in real life with more than 30 items on a single view, let alone 100 or 1000 — that all needs to be completely changed in one operation without re-rendering.

It's a common theme in benchmarking apps though, which will ultimately be the main reason for adding the key support.

  • latchkey  2 years ago

    > I use zero apps in real life with more than 30 items on a single view, let alone 100 or 1000

    I do.

    You've now disqualified this entire framework over a single issue, number of items in a list.

    • tipiirai  2 years ago

      I was talking about the applications I personally use frequently, like Slack for example. Unlike the parent said that "this becomes a frequent issue in any app at scale", I just don't see this happening on the UI's I personally use.

      Having said that: they key-optimization thing will be implemented. The more frequent issues get a higher priority. Maybe it's this one.

      5 replies →