this is exactly why SPA's get a bad rep: developers think an 80ms delay on a minor render operation is acceptable

The same could be said for php, c, or even basic.

They get a bad rep, but it's perfectly possible to create something secure, stable, maintainable and performant

You might be surprised just how fast 80ms really is. Again I'm not saying this shouldn't be addressed if it's causing noticeable issues but labeling it as a bug just seems strange to me (but that label wouldn't change the priority for me by itself)

> You might be surprised just how fast 80ms really is.

it's, like, five frames on a slow monitor. missing a single frame is already bothersome and worthy of bug reports.

It's noticeable if something is moving because that won't look smooth. But a 80ms delay will be very hard to notice. An average reaction time is around 300ms.

With all the downvotes I'm getting I might be missing something though :P

You're not wrong about 80ms being a "small" amount of time, but you're saying that in absolute terms. Native UI tool kits for decades now have targeted <100ms latency[1]. That includes processing user input and rendering. 80ms for part of a render operation spends almost your whole budget.

The sum total of ignoring this kind of performance footgun is why apps like Slack feel so crappy. You can't get into the flow because it's a pile of high-latency, asynchronous interactions. I haven't used Photoshop in a long time, but back in the early 2000s even on my Compaq with 32MB of RAM it was snappy. I can't imagine using something as complex as Photoshop built as an Electron SPA and keeping my sanity.

[1] https://stackoverflow.com/questions/536300/what-is-the-short...

> An average reaction time is around 300ms.

just because human's reactions are slow, does not mean that humans do not notice. In music it's routine to have people complain when latency goes above 15 ms and it was recently shown that humans could notice in some physiological way down to half a millisecond of latency.

Do you have a source for the half a millisecond part?

Just curious

It's very minor, but when it happen many times, it'll be noticable. It's proven because author start the investigation.

It won't be a problem if the tooltip has delayed appearance by 80ms, but it holds the process. So the site will have a 80ms stutter everytime a tooltip appear.

Which generally won't be noticed but it depends on the site. I'm not saying it isn't an issue just that I wouldn't call it a bug. Certainly not something so bad that it would turn you away from web dev. I mean we even have the tooling to track it down fairly easily

It's a bug. I don't care for your semantic separation of issue/bug and neither should you. Pointless distinction for the sake of ego protection. It is unwanted behaviour, therefore a bug.

Alright I guess we will just have to agree to disagree. For me, if an action takes slightly longer than it could take but isn't significantly impacting UX then I don't personally think of that as a bug. Maybe I just don't understand the impact this particular issue had

"Minor" performance issues add up quickly when there are more of them. And with this attitude there will be more of them

I never said it shouldn't be addressed if it is impacting the user experience