Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I also notice this feeling in web apps that use React managed inputs for example.

I can tell when there's an extra render in a React app, on an input or just when something renders slightly later than expected like an update is being done in a useEffect after the first render, and I agree that it's really annoying. However, the input latency of a React app should be less than 16ms. There's nothing intrinsic to React (or any JS framework) that means there has to be any appreciable lag. Obviously there are badly written ones that do things very poorly, but if you find one like that you should vote with your feet and move to a competitor.



> Obviously there are badly written ones that do things very poorly, but if you find one like that you should vote with your feet and move to a competitor.

What if there are no well written ones? No competitor to move to? I for one haven't seen a single React app that wasn't annoyingly slow, under the standards we're discussing here.

> There's nothing intrinsic to React (or any JS framework) that means there has to be any appreciable lag.

And yet, for common SPA frameworks, it seems it's always there. So if it's not the framework and the language, then something common in the overall process of frontend dev is a likely candidate.


What if there are no well written ones? No competitor to move to? I for one haven't seen a single React app that wasn't annoyingly slow, under the standards we're discussing here.

If that's the case then React is a huge problem.

I've seen lots of apps that nail 60fps that are written in React though, so I don't think it is the case.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: