4 ms·
I've spent plenty of time optimizing performance. It almost always comes down to a backend issue, unless the frontend is doing something profoundly stupid, like
by johnfn 2y ago
I've spent plenty of time optimizing performance. It almost always comes down to a backend issue, unless the frontend is doing something profoundly stupid, like making multiple API requests in serial when they could be batched or parallelized.
- LtWorf 2y agoYes because loading 500 different css and js files is not a problem for performance.
- smrq 2y agoThey literally just said "unless the frontend is doing something profoundly stupid".
- yawaramin 2y agoThat's the norm in the React world nowadays. You should take a look at https://infrequently.org/2024/08/object-lesson/ https://infrequently.org/2024/08/object-lesson/
- johnfn 2y agoThis article is better, but has very little to do with React. The major issues I see are 1) loading a 2.5 MB AWS library (not React), 2) not doing SSR (not React) and 3) not tree shaking (not React). I agree these are all problems. But shouting to the skies about React is not going to solve them.
- yawaramin 2y ago'React' is really just a stand-in for the excesses of client-rendered apps. Do you really think Alex Russell, after writing all these blog posts about the general problem, thinks that React specifically is to blame? Of course not. He is picking it as an example that often causes higher complexity.
- LtWorf 2y agoI think his definition of profoundly stupid probably differs from other people's.