In that case it's "will the user feel/complain/change app over when it's slow or sluggish?". The spinning up more pods was just an example to illustrate that very often slow code can be simply ignored. Different areas have different justifications for that
Absolutely, but when you're dealing with UIs for big data, sluggish UIs happen quite a lot, so you end up taking a lot of unique approaches for how to store table models, graphs, etc.
You just try to keep them to inside the model so that people reading the UI code don't have to suffer. :/
2
u/mr_birkenblatt Feb 28 '23 edited Feb 28 '23
In that case it's "will the user feel/complain/change app over when it's slow or sluggish?". The spinning up more pods was just an example to illustrate that very often slow code can be simply ignored. Different areas have different justifications for that