Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
JavaScriptWHO, WHAT, WHEN, WHERE, WHY
About Me Authored tamufeed.js     GoMobile Tech Team                           Responsive Web Design
what
whatJavaScript is a lightweight, interpreted, object-oriented language with first-class functions.
the server side 1994 Netscape Enterprise Server 1996 Microsoft IIS 3.0 Today: Node.js
the client sideAdobe Flash, Google Chrome, Nexus 7, Firefox, Opera,Safari, iPad, Kindle PaperWhite, Windows 8, InternetExp...
The Language & Its Libraries Like Java and .NET, JavaScript has its go-to libraries Libraries! extend the present, polyf...
Links MDN https://developer.mozilla.org/en-    US/docs/JavaScript   MDN, Learn https://developer.mozilla.org/en-    US/l...
what it’s not vbscript python CoffeeScript Google Dart Microsoft TypeScript
when
when 1995 Netscape 2.0 1996 IE 3.0 1997 Ecma-262 1999 Ecma-262 Ed.3 2009 Ecma-262 Ed.5 2011 Ecma-262 Ed.5.1
when When do you JavaScript?
where
where HTML5 Texas http://html5tx.com @jsconf http://jsconf.com http://texasJavaScript.com http://austinJavaScript.comF...
Who’s Who? Douglas Crockford Y! http://www.crockford.com Brendan Eich N. @BrendanEich    http://BrendanEich.com   John ...
why
why Pervasive: It’s everywhere Performance: Browser Wars for the win Mutable: JS lets you do stuff Community: Welcome ...
howBEST PRACTICES
some best practices
best practices Use meaningful variable names Write narrative code
best practices Use object literals And JSON notation whenever possible
best practices Don’t pollute the global namespace.
best practicesUnobtrusive JavaScript Code is decoupled from markup; only binding of behavior to DOM is the CSS selector....
best practices Use strict mode. Stick to The Good Parts
best practices the module pattern
best practices Isolate & minimize DOM access
best practices Patterns
best practices Enhance progressively and degrade gracefully.
best practicesPrefer JS libs over HTML5 API over ES5.1
best practices Compress (e.g. YUI Compressor) Concatenate to avoid network latency & HTTP  overhead Synchronous JavaScr...
best practices Know your JS engines when testing.
JavaScript: the who, what, when, where, why, & how
Upcoming SlideShare
Loading in …5
×

JavaScript: the who, what, when, where, why, & how

699 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

JavaScript: the who, what, when, where, why, & how

  1. 1. JavaScriptWHO, WHAT, WHEN, WHERE, WHY
  2. 2. About Me Authored tamufeed.js  GoMobile Tech Team  Responsive Web Design
  3. 3. what
  4. 4. whatJavaScript is a lightweight, interpreted, object-oriented language with first-class functions.
  5. 5. the server side 1994 Netscape Enterprise Server 1996 Microsoft IIS 3.0 Today: Node.js
  6. 6. the client sideAdobe Flash, Google Chrome, Nexus 7, Firefox, Opera,Safari, iPad, Kindle PaperWhite, Windows 8, InternetExplorer 9, Windows Phone
  7. 7. The Language & Its Libraries Like Java and .NET, JavaScript has its go-to libraries Libraries! extend the present, polyfill the past, and pioneer the future
  8. 8. Links MDN https://developer.mozilla.org/en- US/docs/JavaScript MDN, Learn https://developer.mozilla.org/en- US/learn/ W3 http://www.w3.org/community/webed/wiki/Main_ Page#JavaScript_core_skills Future http://www.webPlatform.org http://pineapple.io/resources/tagged/javascript?typ e=tutorials&sort=all_time
  9. 9. what it’s not vbscript python CoffeeScript Google Dart Microsoft TypeScript
  10. 10. when
  11. 11. when 1995 Netscape 2.0 1996 IE 3.0 1997 Ecma-262 1999 Ecma-262 Ed.3 2009 Ecma-262 Ed.5 2011 Ecma-262 Ed.5.1
  12. 12. when When do you JavaScript?
  13. 13. where
  14. 14. where HTML5 Texas http://html5tx.com @jsconf http://jsconf.com http://texasJavaScript.com http://austinJavaScript.comFollow the individuals
  15. 15. Who’s Who? Douglas Crockford Y! http://www.crockford.com Brendan Eich N. @BrendanEich http://BrendanEich.com John Resig jQ @jeresig http://ejohn.org Nicholas Zakas Y! @slicknet http://www.nczonline.net Stoyan Stefanov Y! @stoyanstefanov http://www.phpied.com Rebecca Murphy B! @rmurphey http://rMurphey.com Addy Osmani G. @addyosmani http://addyosmani.com
  16. 16. why
  17. 17. why Pervasive: It’s everywhere Performance: Browser Wars for the win Mutable: JS lets you do stuff Community: Welcome to brogrammer culture Mashups Cross Platform: Apps for Windows 8, to iPhone, to Android Circumvent Your CMS Responsive Web Design
  18. 18. howBEST PRACTICES
  19. 19. some best practices
  20. 20. best practices Use meaningful variable names Write narrative code
  21. 21. best practices Use object literals And JSON notation whenever possible
  22. 22. best practices Don’t pollute the global namespace.
  23. 23. best practicesUnobtrusive JavaScript Code is decoupled from markup; only binding of behavior to DOM is the CSS selector. Styles are decoupled from code (antipatterns: Twitter Badge JS, Titanium 2)
  24. 24. best practices Use strict mode. Stick to The Good Parts
  25. 25. best practices the module pattern
  26. 26. best practices Isolate & minimize DOM access
  27. 27. best practices Patterns
  28. 28. best practices Enhance progressively and degrade gracefully.
  29. 29. best practicesPrefer JS libs over HTML5 API over ES5.1
  30. 30. best practices Compress (e.g. YUI Compressor) Concatenate to avoid network latency & HTTP overhead Synchronous JavaScripts blocks the browser, so load last on the page
  31. 31. best practices Know your JS engines when testing.

×