I see a pattern where developers ignore performance if it is not seen as an eminent problem.
Examples of this could be ignoring components re-rendering excessively because it's not a real performance problem yet for the targets user, accepting that derived state is calculated unnecessary, having cookies/headers on requests that have no need for them etc.
From a business perspective this makes good sense.
There are usually better business gains elsewhere.
I also do this myself at work.
But 10+ browser tabs with these kinda of shenanigans going in them + other applications add up.
Especially when we start to consider mobile devices.
That leaves me wondering..
- Isn't this kinda of lying to our selves by only looking at best case scenarios?
- When does this become too puristic?
- How could we mitigate this in a way that makes sense business wise?
Edit, extra question.
- How would we measure if this is a problem for users in a none-intrusive way?