@thdxr: it's worth deeply studying why no framework dethroned react it's completely misunderstood and it's why every prediction…
Summary
A tweet discussing why no framework has dethroned React and how this insight applies to broader predictions.
View Cached Full Text
Cached at: 06/25/26, 09:15 AM
it’s worth deeply studying why no framework dethroned react
it’s completely misunderstood and it’s why every prediction you see by programmers tends to be wrong
and once you get it, you can apply this understanding to nearly everything you do
Similar Articles
@kentcdodds: React haters showing up in the comments on this one You might hate it, but I'm not wrong. And I predicted it back in 20…
A tweet from kentcdodds about React haters commenting on his correct prediction from 2020, with links to receipts.
Just Fucking Use React
This opinionated article aggressively advocates for using modern JavaScript frameworks like React over pure HTML for complex web applications, arguing that complexity requires proper tooling.
Does Anybody Actually Like React?
A compilation of critical blog posts about React, covering performance issues, a critical security vulnerability (CVE-2025-55182, CVSS 10.0), and broader ecosystem concerns.
Announcing Topcoat: a framework for building full-stack reactive web apps with Rust
Tokio announces Topcoat, a modular, batteries-included Rust framework for building full-stack reactive web apps, entirely server-rendered with reactive instructions similar to HTMX.
@evanyou: To answer a common question - why not make React Compiler a plugin? It all comes down to practical trade-offs. Making i…
Evan You explains why integrating React Compiler directly into OXC (Rust) offers significant performance gains over a plugin approach, while addressing binary size concerns and future plans for AST transfer.