Historiae JavaScript

Breve storia di JavaScript e della sua scalata al web.

Presentato il 27/10/2016 al meetup mensile del FEVR

Transcript

1. Historiae JavaScript Marco Solazzi - @dwightjack FEVR 10/2016
2. About me - Senior Front-end @ AQuest - Co-founder Frontenders Verona
3. Nolan Lawson - Oct 2016 http://www.digital-web.com/articles/fluid_thinking/
5. Don’t flame Think
6. Don’t flame Think
7. Understand by History
8. JS Timeline -10 (1995) Netscape 0 (2005) AJAX 0 (2005) Prototype.js 1 (2006) jQuery 8 (2013) React 4 (2009) Node.js 5 (2010) Backbone.js 7 (2012) Grunt
9. Before JavaScript -10 before JS
10. -10 before JS (Mid 90s) - The Hyper-text Era
11. - wild new world - limited design and styles - no SEO - a couple of crappy browsers - just plain noisy PCs Hyper-text Era
12. <font> <center> <strike> <menu> <u> <dir> Weird gods
13. -5 before JS (2000) - XHTML - XML all the thing - improved semantics - stricter error handling - let CSS do the style
14. “ … Graceful degradation means that your Web site continues to operate even when viewed with less-than-optimal software in which advanced effects don't work... ” Graceful Degradation Peter-Paul Koch - Oct 2002 http://www.digital-web.com/articles/fluid_thinking/
15. And Then There Was AJAX The blank screen rebellion (year 0)
16. “ … Instead of loading a webpage, at the start of the session, the browser loads an Ajax engine — written in JavaScript [...]. This engine is responsible for both rendering the interface the user sees and communicating with the server on the user’s behalf. ” Async JavaScript and XML Jesse James Garrett - Feb 2005 http://adaptivepath.org/ideas/ajax-new-approach-web-applications/
17. “ … Instead of loading a webpage, at the start of the session, the browser loads an Ajax engine — written in JavaScript [...]. This engine is responsible for both rendering the interface the user sees and communicating with the server on the user’s behalf. ” Async JavaScript and XML Jesse James Garrett - Feb 2005 http://adaptivepath.org/ideas/ajax-new-approach-web-applications/
18. Web 2.0 - Breaking Changes
19. Progressive Enhancement Aaron Gustafson - Oct 2008 http://alistapart.com/article/understandingprogressiveenhancement
20. “ … Progressive enhancement focuses on the content. [...] Content is the reason we create websites to begin with. Some sites disseminate it, some collect it, some request it, some manipulate it, and some even do all of the above, but they all require it. Content-first theory
21. “ … Progressive enhancement focuses on the content. [...] Content is the reason we create websites to begin with. Some sites disseminate it, some collect it, some request it, some manipulate it, and some even do all of the above, but they all require it. Content-first theory
22. Is it true?
23. Is it true?
24. The backbonian Dynasty 5 after JS - the sengoku era of frameworks
25. “ … Backbone.js gives structure to web applications by providing models with key-value binding and custom events... ” Backbone.js
26. “ … Backbone.js gives structure to web applications by providing models with key-value binding and custom events... ” Backbone.js
27. Web.site !== Web.application
28. The web has changed, indeed...
29. “ We are trying to build applications that run right in a dozen browsers, look good on thousands of different devices, load fast enough for impatient commuters in the subway, and are still accessible enough that blind people can use them. ” Frontend Fadigue Quincy Larson - Oct 2016 https://medium.freecodecamp.com/javascript-fatigue-fatigue-66ffb619f6ce
30. Old concepts for a new era? Motorwagen
31. JavaScript, Your New Overlord 7 after JS - Grunt & the discovery of frontend-ops world
32. “ Being primarily a JavaScript developer, I decided to use Node.js and npm because the dependencies I most care about (JSHint and UglifyJS) were already npm modules. ” Grunt Ben Alman - Mar 2012 https://bocoup.com/weblog/introducing-grunt
33. “ Being primarily a JavaScript developer, I decided to use Node.js and npm because the dependencies I most care about (JSHint and UglifyJS) were already npm modules. ” Grunt Ben Alman - Mar 2012 https://bocoup.com/weblog/introducing-grunt
34. - modular buildings - frontenders can rule the CLI - JavaScript can manipulate itself - JavaScript can generate other languages Discovers
35. One true web language 8 after JS - The React advent & JavaScript Inquisition
36. “ Oh my god no, no one uses jQuery anymore. You should try learning React, it’s 2016.” Jose Aguinaga - Oct 2016 https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f
37. - CSS sucks → CSS in JS - HTML boo! → JSX it please - You might not need jQuery - … but at least 200MB of npm modules new rules
38. Coffeescript anyone?
39. “ Yes, it is easy to poke fun at CSS and it’s Frankenstein-esque syntax. It is also easy to show that you can do all the things it does with other technologies.” Christian Heilmann - Oct 2016 https://www.christianheilmann.com/2016/10/05/can-we-stop-bad-mouthing-css-in-devel oper-talks-please/
40. “ Yes, it is easy to poke fun at JavaScript and it’s Frankenstein-esque syntax. It is also easy to show that you can do all the things it does with other technologies.”
41. “ JavaScript is too great an opportunity to build accessible, easy-to-use and flexible solutions for the web to not use it. [...] We shouldn’t blindly rely on it – we should own the responsibility to work around its flaky nature and reliability issues.” Christian Heilmann - Oct 2016 https://www.christianheilmann.com/2016/10/14/we-need-javascript-to-fix-the-web/
42. Server-side rendering 10 after JS - a new hope
43. Client-side code that renders on the server generating a static HTML to be served to the user...
44. Back to square one
45. Thanks