Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-opus-4-20250514· AnthropicHugging Face LMArena Human Preference 140K

HIstory of vanilla js. Was it really a framework?

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Googlegemma-3-27b-it’s answer.
  1. User

    HIstory of vanilla js. Was it really a framework?

  2. Claude Assistant

    Vanilla JS isn't actually a framework - it's a tongue-in-cheek term that refers to plain JavaScript without any libraries or frameworks. The name emerged as a humorous response to the proliferation of JavaScript frameworks and libraries in the early 2010s.

    The term gained popularity around 2012 when a satirical website called "vanilla-js.com" was created. The site playfully presented vanilla JavaScript as if it were a framework, complete with download buttons and performance comparisons showing it was "faster" than jQuery, React, Angular, and other actual frameworks (because, of course, using no framework at all has zero overhead).

    The joke resonated with developers who felt overwhelmed by the constant stream of new JavaScript frameworks and the pressure to always use the latest tools. It became a way to advocate for using plain JavaScript when it's sufficient for the task at hand, rather than automatically reaching for a framework.

    The history of JavaScript itself dates back to 1995 when Brendan Eich created it in just 10 days at Netscape. Over the years, JavaScript evolved significantly through various ECMAScript standards (ES3 in 1999, ES5 in 2009, ES6/ES2015 in 2015, and annual updates since then). These improvements made "vanilla" JavaScript increasingly powerful and capable of handling tasks that previously required libraries.

    Today, "vanilla JS" remains a useful term to distinguish between using plain JavaScript versus using frameworks like React, Vue, or Angular. Modern vanilla JavaScript includes features like Promises, async/await, modules, arrow functions, and sophisticated DOM APIs that make it quite capable on its own for many projects.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.