I agree that React (or anything like it) is not the right choice for static content [0]. Islands are great too.<p>I disagree that React is fundamentally bad. React (et al) probably should not be used in 80% of the cases it is being used for, but it is plenty fast for 80% of cases it is reasonable to use. And yes, I read the author's links on the topic.<p>What I found to slow SPA type things (mostly built in React due to its popularity) to a crawl are ~bad~ terrible choices for UI libs, several (!) tracking libraries, badly loaded 3rd party assets, unoptimised images, ads, not using URLs properly, and a cascade of API calls. All of which independent of React, but much of it affordances of client-side fuckery.<p>0 - The idea to set up an entire stack and everything that comes with it to render a hand full of paragraphs borders on lunacy. It is equally insane to wire up a dozen services and as many databases to manage a hand full of entities for a dozen users. I have come to terms with the fact that all software is fundamentally broken and everybody involved (including myself) has been infested with brain worms. The Butlerian Jihad can't come soon enough.