Skip to content

Instantly share code, notes, and snippets.

@zaunere

zaunere/The Ups and Downs of Javascript.md

Last active November 30, 2024 13:13
Show Gist options
  • Save zaunere/f211ce1312134d5290b68ccc2004b456 to your computer and use it in GitHub Desktop.
Save zaunere/f211ce1312134d5290b68ccc2004b456 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
The Ups and Downs of Javascript.md

JavaScript History Timeline: Highlights, Setbacks, and Shifts

A chronological breakdown of JavaScript's most significant events, including moments when it was discouraged and later became essential, formatted by the companies and communities that drove these changes.

Netscape

  • 1995: Creation of JavaScript (Mocha/LiveScript)
    • Brendan Eich developed JavaScript in 10 days for Netscape Navigator, initially called Mocha, then LiveScript, and finally JavaScript.
    • The first JavaScript engine, SpiderMonkey, was embedded in Netscape browsers.

Microsoft

  • 1996: JScript
    • Microsoft released JScript with Internet Explorer 3, aiming to compete with JavaScript and ensure compatibility with Netscape’s scripting.

Late 1990s–Early 2000s: JavaScript Disablement Encouraged

  • JavaScript faced security issues (e.g., XSS vulnerabilities) and browser stability problems.
  • Security experts often recommended disabling JavaScript to avoid harmful scripts or browser crashes.

ECMA International

  • 1997: ECMAScript Standardization
    • JavaScript was standardized by ECMA International as ECMAScript, making it more consistent across different browsers.
  • 1999: ECMAScript 3 (ES3)
    • ES3 brought important updates that improved reliability, such as regular expressions and better exception handling. JavaScript was still considered insecure at this point.

Mozilla

  • 1998: Rhino JavaScript Engine
    • Mozilla developed Rhino, a Java-based JavaScript engine for server-side use.

Early 2000s: Encouragement to Disable JavaScript

  • Despite community contributions, JavaScript still struggled with security, performance, and compatibility issues.

Apple

  • 2002: JavaScriptCore (Nitro)
    • Apple released JavaScriptCore (Nitro), the JavaScript engine for Safari.

Mid-2000s: Performance Concerns

  • JavaScript engines were still slow, and performance was an issue. Users were often encouraged to disable JavaScript for better browsing speed, especially on low-powered devices.

The Shift to Encouraging JavaScript Use

  • 2005: AJAX Revolution and Web 2.0
    • AJAX (Asynchronous JavaScript and XML) became popular, allowing dynamic content updates without page reloads.
    • Companies like Google began encouraging JavaScript to create richer user experiences, reversing the trend of disabling it.

Google

  • 2008: V8 JavaScript Engine
    • Google released V8, a high-performance JavaScript engine with JIT compilation, powering Google Chrome.
  • 2009: Node.js (Powered by V8)
    • Node.js was developed by Ryan Dahl, bringing JavaScript to the server-side.

Microsoft (Continued)

  • 2010: Chakra Engine in Internet Explorer 9
    • Microsoft released Chakra, a high-performance engine for IE9.
  • 2016: ChakraCore Open Sourcing
    • ChakraCore (the core of Chakra) was made open-source, inviting broader community contributions.

Mozilla (Continued)

  • 2008: TraceMonkey
    • Mozilla introduced TraceMonkey, the first JIT compiler for SpiderMonkey, improving performance in Firefox.
  • 2011: JaegerMonkey
    • JaegerMonkey improved SpiderMonkey’s performance further.
  • 2019: Warp JIT for SpiderMonkey
    • Warp, a new optimizing JIT, was introduced to SpiderMonkey.

Apple (Continued)

  • 2006: SquirrelFish/Nitro
    • Apple enhanced JavaScriptCore with SquirrelFish, later known as Nitro, to make JavaScript execution faster.

Late 2000s–2010s: Rise of JavaScript Use

  • Safari started using JavaScript extensively for better web experiences, aligning with the broader industry shift toward JavaScript-heavy websites.

Opera

  • 2009: Carakan Engine
    • Opera introduced the Carakan engine with JIT compilation, improving JavaScript speed in the Opera browser.

Community and Industry-Wide Standards

  • 2014: ECMAScript 6 (ES6/ECMAScript 2015)
    • ES6 brought major improvements like let/const, arrow functions, classes, modules, and Promises, making JavaScript more developer-friendly.

Google (Further Contributions)

  • 2018: Ignition and TurboFan for V8
    • Google introduced Ignition and TurboFan for V8, further improving performance and reducing memory usage.
  • React and SPAs
    • React (2013) and AngularJS (from Google) popularized Single-Page Applications (SPAs), relying heavily on JavaScript to deliver an app-like experience.

Summary of Encouragement and Decline

  • Early Resistance (Late 1990s–Mid-2000s):
    • JavaScript was discouraged due to security issues, performance problems, and frequent browser crashes.
  • Shift Towards Encouragement (2005–Ongoing):
    • Companies like Google and Mozilla significantly improved JavaScript engines, marking a shift in perception.
    • The AJAX revolution, V8, and Node.js demonstrated the power of JavaScript, making it a core technology for creating interactive web experiences.

Conclusion

  • Early 2000s: JavaScript was seen as a liability due to security and performance concerns.
  • Mid-2000s: The advent of AJAX and performance improvements in JavaScript engines led to a significant shift in favor of JavaScript.
  • 2010s and Beyond: JavaScript became indispensable for modern web development, powering everything from dynamic front-end experiences to server-side applications.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment