3 ms·

I think anyone who is going to listen to a react critique has already heard it. For those looking for a more in-depth critique of react, this article looks goo

I think anyone who is going to listen to a react critique has already heard it. For those looking for a more in-depth critique of react, this article looks good: https://www.zachleat.com/web/react-criticism/ https://www.zachleat.com/web/react-criticism/ Although that focuses more on the objective legal and performance issues, if anyone can recommend something focusing more on architectural and developer ergonomics issues I'd love to see it.

SebastianKra 3y ago
The summary does a good job of demonstrating the performance issues. But, just browsing around the web, I noticed that my experiences don't match the criticisms: Amazon is fast, Mastodon is fast, Twitter is (still) fast although a bit flickery, HackerNews loads slower than TheVerge for some reason. JetBrains Space is fast, Jira is a disaster. Static sites like GitHub and GitLab have been testing my patience recently - I wish GitLab was an SPA. The React pages that feel slow are often just poorly designed (momondo.com) or load ten times as much data than React could be responsible for (booking.com, icloud.com). Admittedly, I'm not in a lab. I have content blockers, a fast computer and decent internet. But personally, I don't see a significant correlation between the framework and the perceived speed. Other aspects, such as the design of loading states seem more important.