The Backlash Against Artificial Complexity: Vanilla JS, Web Components, and Team Scalability
A viral blog post advocating for "Vanilla JavaScript" and native Web Components has sparked a passionate debate on Hacker News regarding "artificial complexity" in modern frontend development. The author argues that modern frameworks (React, Angular, Vue, Svelte) force developers into rigid build pipelines, transpilers, and restrictive state-management abstractions that fight against native browser capabilities rather than leveraging them.
As the author asserts:
"Instead of inventing virtual DOMs, reactive engines, or build pipelines, EHTML activates plain HTML once and then reacts only to real DOM insertions—doing the minimum work needed, exactly when it’s needed." — Why Vanilla JS
The Core Friction: Individual Autonomy vs. Team Governance
The community discussion highlights a fundamental tension between individual developer productivity and the pragmatics of managing engineering teams at scale:
-
The Case for Framework Standardization: Framework defenders argue that the primary value of an opinionated framework is not technical performance, but organizational governance. Frameworks establish "ground rules" that make codebases predictable, maintainable, and hires easily replaceable. When developers build bespoke vanilla solutions, they risk creating unmaintainable "art":
"When you bust out a bespoke solution that carves out that one thing you needed and does it oh so elegantly and perfectly, you're creating art but most of the canvas is left blank for future developers and they're…" — Comment by benoau
-
The Case for Native Simplicity: Conversely, proponents of vanilla development point out that the browser itself has evolved into a highly capable framework. With modern additions like native Web Components, import maps, and JSDoc for build-step-free type checking, the historical justifications for complex bundlers and heavy frameworks are rapidly eroding. Critics of framework bloat argue that the industry has spent a decade "cargo culting" global-scale enterprise architectures onto small-to-medium projects that would be far better served by simple, native code.
The AI Angle: LLMs as Framework Replacements
An intriguing emerging perspective in this debate is the role of AI. Some developers suggest that the rise of powerful LLMs actually decreases the need for rigid frameworks. While frameworks traditionally provided the guardrails to keep humans from writing unstructured spaghetti code, LLMs are highly adept at navigating, documenting, and refactoring clean, native APIs. This allows developers to write lightweight, dependency-free vanilla code while relying on AI to act as the "connective tissue" and maintainer assistant.