Re:React Won by Default – and It's Killing Front End Innovation
by alpinisme on Monday September 15, 2025 @07:59PM
(#45256417)
“Most” react apps needing “seconds” definitely needs some citation or evidence. Even in fairly heavy and laggy react apps, it’s still usually network latency, waterfall requests, ad/tracking bloatware, large asset sizes, and the usual old classics that cause perceptible slowness in my experience.
Re:React Won by Default – and It's Killing Front End Innovation
by nazgul17 on Monday September 15, 2025 @08:27PM
(#45256621)
In my humble (backender) opinion, if it's hard to use a tool right, that counts as a cons, and that must be accounted for when choosing which tool to use.
Re:React Won by Default – and It's Killing Front End Innovation
by nosefurhairdo on Monday September 15, 2025 @09:51PM
(#45257135)
It's hard to build non-trivial web UI with any technology—React is just what's familiar. If Angular had won (god forbid) we'd be seeing all the same articles written about how bad Angular is.
Re:React Won by Default – and It's Killing Front End Innovation
by mmis1000 on Monday September 15, 2025 @10:17PM
(#45257293)
You probably never see what reddit like after it just get rewrite. https://www.reddit.com/r/bugs/comments/rj0u77/reddit_redesig...
I won't say most react apps performs like this. But it's what you will get if you ship a big react app without optimization at all.
Other framework mostly have a much saner default (for example, component without argument change does not re-render). So it will work well (not best though) even in large scale. But in react they are all opt-in.
That is very optimistic. Most React projects never get to the optimization stage, and end up with seconds of rendering and transition delays that significantly harm UX. And the amount of time spent battling hooks, re-renders, compatibility issues, etc amounts to hundreds of hours over the course of a medium-sized project, thousands for larger companies.