HTMX 4.0 and the Enduring Backlash Against Frontend Complexity
HTMX 4.0 shipped (thread 49478178) and the release sparked the usual debate about whether server-rendered HTML is the right mental model for web apps. The thread also collided with a broader UI philosophy debate (49479837) about whether GUIs should be keyboard-driven, whether TUIs are worth building, and whether the web should just be the default UI layer for everything.
The through-line is a genuine and recurring frustration with frontend complexity that hasn't gone away. HTMX represents a specific thesis: that most web apps don't need a client-side JavaScript framework, and that the complexity introduced by React and its ecosystem is a bad trade. The 'CEO of HTMX' joke in the comments landed because the project has become something of a cultural symbol for that frustration, not just a library.
The Twelve-Factor App (2025) thread (49472216) runs adjacent to this, with people mourning Heroku and noting that modern cloud complexity has made simple deployment harder, not easier. The nostalgia for simpler abstractions is real and consistent.
So what?
HTMX continues to gain adoption because it solves a real problem: teams that don't need a SPA but built one anyway are drowning in complexity. If you're starting a new internal tool or a B2B product where the user base is small and predictable, seriously evaluate whether a server-rendered approach with HTMX costs you less in maintenance than a React app would. The 'simpler is better' crowd is growing and they have a point.