Replacing JavaScript with Just HTML

A recent article published on HTMHell explores the concept of building modern web interfaces using only HTML, without relying on JavaScript. The piece, part of an advent calendar series, delves into the challenges and potential of creating interactive web experiences with standard HTML features. It discusses how many modern web functionalities can be replicated using HTML attributes and form elements, though often with significant limitations or awkwardness. The article highlights the tension between the simplicity of HTML and the complexity introduced by JavaScript frameworks. It serves as a thought experiment on web standards and developer practices, prompting readers to reconsider their reliance on JavaScript for tasks that might be achievable with pure HTML. The discussion has garnered attention on Hacker News, with users debating the practicality and philosophy behind such an approach.

The article presents a provocative challenge to modern web development practices by asking if it is possible to replace JavaScript entirely with HTML. This concept is not about using frameworks that compile to HTML, but rather utilizing the native capabilities of the HTML language itself. The author explores the idea of returning to the roots of the web, where interactivity was achieved through browser-native features rather than custom scripts. This approach emphasizes progressive enhancement and accessibility, suggesting that a baseline experience should always be functional without JavaScript.

However, the article quickly acknowledges the vast gap between what HTML can do natively and what users expect from modern web applications. The author examines various HTML attributes and elements that provide interactivity, such as form validation, the <details> element for accordions, and CSS pseudo-classes triggered by user actions. While these features exist, their limitations are often what drive developers to reach for JavaScript solutions in the first place. The piece argues that understanding these limitations is crucial for writing better, more resilient web code.

The article details several specific examples of what can be achieved with pure HTML. For instance, the <details> and <summary> elements can create a toggle or accordion without a single line of JavaScript. Similarly, the target="_blank" attribute on a link can open a new window, and the download attribute can force a file download. Form elements offer built-in validation through attributes like required, pattern, and min/max. The article also points to the :target CSS pseudo-class, which can be used to create stateful interfaces like tabs or modals by manipulating the URL hash.

Despite these capabilities, the author highlights significant drawbacks. The user experience of these HTML-only solutions is often clunky. For example, the <details> element cannot be animated open and closed, and form validation messages are difficult to customize. The :target method for state management pollutes the browser history, making the back button behave unexpectedly. These limitations demonstrate why developers have historically turned to JavaScript for finer control over the user experience, even for seemingly simple interactions.

Beyond the technical exploration, the article serves as a commentary on the philosophy of web development. It questions the prevailing trend of treating the browser as a runtime for complex applications, often managed by heavy frameworks like React, Vue, or Angular. By stripping away JavaScript, the author forces a re-evaluation of what is truly necessary for a functional website. This aligns with the principles of the Indie Web and progressive enhancement, where content and functionality are prioritized over complex, client-side rendering.

The discussion also touches on the learning curve for new developers. The modern JavaScript ecosystem is notoriously complex, with build tools, transpilers, and countless libraries to learn. In contrast, HTML is relatively simple and stable. The article suggests that starting with HTML and only adding JavaScript when absolutely necessary could lead to a more robust and accessible web. It encourages developers to master the platform's native features before reaching for external tools.

The article was shared on Hacker News, where it sparked a lively debate among developers. The discussion reflected a divide between purists who champion the simplicity and resilience of HTML-only solutions, and pragmatists who argue that modern user expectations make such an approach unfeasible for most commercial projects. Many commenters pointed out that while the HTML-only approach is an excellent educational exercise and suitable for simple content sites, it falls short for complex applications like dashboards, editors, or social networks. The consensus seemed to be that the article is a valuable thought experiment that highlights the power of the web platform, even if a full replacement of JavaScript is not a realistic goal for the majority of the web today.