Download to read offline
Uploaded byCristian Vat
Ten years later
This document discusses the history and evolution of JavaScript over the past 23 years, from its origins in 1995 to the present. It focuses on key events like the standardization of ECMAScript, the introduction of AJAX, jQuery, and how Google Chrome and technologies like V8, Node.js, and WebAssembly have driven JavaScript's widespread adoption and improved performance. JavaScript has gone from an experimental scripting language to being ubiquitous across the web and in applications through technologies like Electron.
More Related Content
![[Start] Playing](https://cdn.slidesharecdn.com/ss_thumbnails/start-playing-121117211541-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Ten years later
- 1.
- 2.
- 3. 23 years ago •1995, Netscape Navigator • Brendan Eich wrote a prototype in 10 days • Mocha • LiveScript • JavaScript • Internet explorer 3 (or was it 2?) in 1996,VBScript and Jscript and JavaScript • ECMAScript standardization
- 4.
- 5. AJAX • XMLHttpRequest • IE5, March 1999 • Thank you Microsoft • OutlookWeb Access 2000 • IE was great • AJAX term coined 2005?
- 6. jQuery • January 2006 •Cross-Browser • DOM abstraction • Chaining
- 7. Ten years ago.GeekMeet #4 • 8 Feb 2009 • JavaScript still sucked • Changes right around the corner • http://geekmeet.ro/timisoara/2009/02/03/program/
- 8. Now • JavaScript isEverywhere • For better or worse
- 9.
- 10.
- 11. Google Chrome • September2, 2008 • Changed everything
- 12. SPEED Make the infrastructurefaster, new uses for it will appear
- 13. Stability / ProcessIsolation • Each tab has its own process • Crashes only crash tab (SadTab) • 3 years after Intel Core2 Architecture came out • 1 year after Nehalem
- 14. V8 • JavaScript importantenough to get custom-built engine • V8 team in Denmark • Lars Bak and Kasper Lund • Both previous worked on Java HotSpot at Sun Microsystems • Platform independent • Modularized • Hidden ClassTransitions ... well types • Dynamic Code Generation
- 15. Security/Sandboxing • Tab =Process = Jail • Further restrictions on what processes have access to • Google Safe Browsing list
- 16. Embeddable? • Modular components •Cross-platform • New use-cases
- 17. Incognito? • For reasons... •For developers
- 18. PDFs • Chrome 8,2010-12-02, built-in PDF viewer inside Sandbox • Pdf.js: 2 July 2011 • JavaScript + Canvas • Included in Firefox since 2012/2013
- 19.
- 20. 2013: Blink • Coincidence?Aliens? • Enough market share to want better control
- 21. CEF • June 12009 • You may not know what it is • You probably have it on your system, at least once • Steam • Adobe Acrobat, Adobe Suite • Battle.net
- 22. Node.js • 27 May2009 • V8 • libuv for async IO
- 23.
- 24. Npm • 12 January2010 • Good, bad, mixed? • Necessary evil
- 25. 15 JULY 2013:ATOM SHELL NOW ELECTRON
- 26.
- 27.
- 28. We love ourElectron apps: • Skype • Slack • Discord • Teams • WhatsApp
- 29. Skype • Old Skype:30 MB RAM • New Skype: 300 MB RAM • I’ve seen 3 GB ... • But Skype developers are happier? • Skype is more consistent across platforms/devices
- 30. JAVASCRIPT IS DEAD Whostill programs directly in JS?
- 31. New level above: •CoffeeScript • TypeScript • Elm • Kotlin
- 32. asm.js • Sub-set ofJS • You will NOT write this yourself • JS but FASTER
- 33. Emulation is here •Games! • More Games! • History/Digital Preservation
- 34. SIMD.js • Fun whileit lasted, will be re-done in….
- 35. WebAssembly • New bytecodefor the web • Stack-based virtual machine • Goal: Near-Native Performance • StillTODO: • GarbageCollection / DOMAccess
- 36. WebAssembly – Use-cases •Cryptominers • Games/Emulation • Hiding your source • Breaks theView Source advantage • But that’s already broken with complex frameworks
- 37. It’s not justv8 • V8 • JavaScriptCore • Rhino ... Nashorn (Rhino but in German) • SpiderMonkey • Chakra • GraalVM
- 38. WebAssembly source code: •C,C++ • Rust • Once GC happens maybe more interesting ones
- 39.
Editor's Notes
- #2 https://www.destroyallsoftware.com/talks/wat
- #4 ECMAScript 3 was released in December 1999 and is the modern-day baseline for JavaScript
- #5 Also, with the release of Microsoft Internet Explorer 5.0, Microsoft released the first version of XMLHttpRequest, giving birth to Ajax
- #6 XML due to MSXML Also included XSLT for transforming data Both XML and XSLT mostly abandoned for JSON+JS
- #7 DOJO slightly earlier MooTools slightly later
- #8 https://www.slideshare.net/deathy/language-barriers slide 31 http://geekmeet.ro/timisoara/2009/02/03/program/
- #12 http://blogoscoped.com/google-chrome/ Chrome actually for speed, retrofitted for minimal browser chrome/UI
- #18 https://en.wikipedia.org/wiki/Private_browsing First one was Safari (yay Apple and privacy...)
- #20 In December 2009, Google released beta versions of Chrome for OS X and Linux. Google Chrome 5.0, announced on May 25, 2010, was the first stable release to support all three platforms. https://gs.statcounter.com/browser-market-share#monthly-200901-201908
- #21 Wow....see next graph... Blink once they had enough market share to want to control everything?
- #22 https://en.wikipedia.org/wiki/Chromium_Embedded_Framework https://en.wikipedia.org/wiki/Chromium_Embedded_Framework#Applications_using_CEF
- #23 Ryan Dahl,
- #24 https://nodejs.org/en/docs/guides/getting-started-guide/
- #25 Notable breakages https://en.wikipedia.org/wiki/Npm_(software)#Notable_breakages In March 2016, npm attracted press attention after a package called left-pad, which was a dependency of many popular JavaScript packages, was unpublished as the result of a naming dispute. Although the package was republished 3 hours later, it caused widespread disruption, leading npm to change its policies regarding unpublishing to prevent a similar event in the future. In February 2018, an issue was discovered in version 5.7.0 in which running sudo npm on Linux systems would change the ownership of system files, permanently breaking the operating system. In July 2018, the npm credentials of a maintainer of the popular eslint-scope package were compromised resulting in a malicious release of eslint-scope, version 3.7.2. The malicious code copies the npm credentials of the machine running eslint-scope and uploads them to the attacker. In November 2018, it was discovered that a malicious package had been added as a dependency to version 3.3.6 of the popular package event-stream. The malicious package, called flatmap-stream, contained an encrypted payload that steals bitcoins from certain applications. npm administrators responded by removing the offending package.
- #32 December 2009 Rails... TypeScript: 1 Oct 2012
- #33 TODO: Screenshot? Just show web sample
- #34 Internet Arcade, MS DOS games
- #38 JS Core: Safari Chakra: IE, but dead?