A tale of webpage speed, or throwing away React
&gt; we’ve discovered that React also leads to some questionable practices. Like hovers in JS (rather than in CSS), drop-down menus in JS, not rendering hidden (under a hover) text (Google won’t be happy), weird complex logic (since it’s possible!), etc. You can have a React app without those problems, but apparently, you have to have better self-control than we had (nobody’s perfect!).<p>idk if this is fair. OP was using some pretty niche tools (clojure) whereas best practice React metaframeworks like Nextjs may have addressed some of those pagespeed issues.<p>additionally, I highly doubt that the author has replicated this functionality by using his new turbolinky framework.<p>So the post is better titled &quot;I improved webpage speed by throwing away React AND a bunch of UI requirements&quot;. which is fair dinkum, but less exciting.