Key points
- The core claim: Redis creator antirez (Salvatore Sanfilippo), in a top-voted Hacker News comment, argues that large frameworks like React are pushed onto the entire industry because big-tech organizational charts demand strict front-end/back-end separation and extreme standardization for hiring flexibility, not because they are objectively better for building websites.
- The 1999 vs. 2026 contrast: Three
.htmlfiles, a sprinkle of CSS, and a few lines of JavaScript once shipped a globally accessible site. Today, the same task involves TypeScript → TSX → JSX → Vite → Webpack → Tree Shaking → Babel → PostCSS → Polyfills. A single<button>can require an entire compilation pipeline. - Organizational structure drives tech stack: API boundaries, client-side data transformation, and client-side routing are mirrors of HR team divisions. Standardized frameworks lower switching costs between jobs, optimizing talent management rather than user experience. As antirez put it, front-end developers end up "knowing the framework but not the language."
- HTMX as a renaissance: HTMX returns HTML rendering to the backend using simple attributes such as
hx-getandhx-target, eliminating front-end routing, state management, and virtual DOM. Antirez, whose Redis is itself a minimalist C masterpiece, aligns with this philosophy. - Criticism of HTMX: A 10-year full-stack developer notes complexity is only relocated, not removed. HTMX's "swap an HTML fragment" model breaks down for real-time collaboration, deep interactivity, and complex state sync (Google Docs, Figma). It fits content sites, admin dashboards, and form-driven apps, but not as a universal replacement.
- Three reflections from antirez: 1. Be wary of corporate "best practices"; Kubernetes suits Google, not every blog. 2. Reconsider the cost of front-end/back-end separation; delivery is the goal, not separation itself. 3. Embrace tool diversity; choose architecture by actual business complexity, not fashion.
- Limits of antirez's view: Redis is a server-side library; his minimalist aesthetic fits server software better than rich user interfaces. He critiques from the outside.
- Open question: No cure yet exists for frontend complexity. HTMX treats symptoms. The real solution may be a new paradigm that expresses complex interaction without an excessive toolchain, something neither a return to 1999 nor continued stacking of 2026 tools can deliver.
- Igor Šarčević, *The Complexity of Modern Frontend: Essential or Accidental?*, binaryigor.com, 2026
- antirez (Salvatore Sanfilippo), Hacker News comment, news.ycombinator.com/item?id=47824051, 2026
- HTMX documentation: htmx.org
- Tony Bai translation and commentary: tonybai.com/2026/05/29/redis-creator-slams-modern-frontend-complexity
Practical takeaway
Match architecture to business complexity. If complexity lives in user interaction and state synchronization, React-class frameworks may be warranted. If complexity lives in data and business logic, an HTMX + backend approach is often lighter. The worst choice is using React to build a site that fundamentally does not need React, simply because "it is the industry standard."