Why JavaScript was made and where it runs
A one-minute timeline from a 10-day prototype to servers, phones and desktops.
JavaScript exists because web pages needed to react. In 1995 pages were static documents, and Netscape wanted a small language for buttons, forms and checks that ran instantly in the browser. Interviewers ask this to see whether you know the language's shape — where it belongs and where it doesn't.
The story in one timeline
May 1995. Brendan Eich builds a prototype at Netscape in about 10 days. Its codename is Mocha.
December 1995. It ships in Netscape Navigator, renamed from LiveScript to JavaScript in a joint announcement with Sun — a marketing nod to Java, a language it never resembled.
1997–2015. The language is standardized as ECMAScript so every browser implements the same core. The big modernization, ES2015, adds classes, modules, arrows and promises.
2009. Ryan Dahl releases Node.js, pairing the V8 engine with an event loop so JavaScript runs servers, not just pages.
Where it runs today
Browsers and web apps. Its home: every button, form and feed you touch.
Servers. Node.js (2009) runs APIs and real-time services in the same language as the page. Seen in: Node.js (nodejs.org, 2009).
Mobile. Frameworks render native controls from JavaScript. Seen in: React Native (reactnative.dev, 2015).
Desktop apps. Editors and chat apps ship as web pages in a native shell. Seen in: Visual Studio Code (Wikipedia, 2015), built on Electron.
Serverless. Platforms run your JavaScript per request with no server to tend — handy for webhooks and scheduled jobs.
Last verified: 2026-10-12.
Key takeaways
- JavaScript was a 10-day browser scripting prototype from 1995 that grew up.
- ECMAScript is the standard; ES2015 is the modern baseline.
- Node.js took the same language to servers in 2009; phones and desktops followed.