#whoami ? My name is Nathan. I do UX stuff at projekt202. But most people know me as "the 960 guy" (that's ok). http://sonspring.com | http://960.gs | http://projekt202.com
Download the slides & follow along: http://slidesha.re/nathansmith Or, talk smack about me on Twitter: @nathansmith Note: You don't have to take notes feverishly.
"Storage of ASCII text, and display on [80x24] screens, is in the short term sufficient, and essential. Addition of graphics would be an optional extra with very much less penetration for the moment." – Tim Berners-Lee http://w3.org/History/1989/proposal.html
"JS had to 'look like Java' only less so, be Java's dumb kid brother or boy- hostage sidekick. Plus, I had to be done in ten days or something worse than JS would have happened." Brandon Eich created JS in 10 days. http://en.wikipedia.org/wiki/Brendan_Eich
With classical inheritance, if your mother breaks her leg, you go visit her in the hospital. With prototypical inheritance, your leg would also (instantly) break. Object Inheritance #TLDR #TLDR = "Too Long, Didn't Read" aka: Sum it up for me :)
The word "JavaScript" was chosen to tap into the brand name of the Java programming language. Sun Microsystems (since acquired by Oracle) owned the trademarks for both Java™ and JavaScript™, and stewarded the development of Java (not JavaScript). In 1997, JavaScript (the language) was standardized by the European Computer Manufacturers Association, and it was dubbed "ECMAScript." http://en.wikipedia.org/wiki/JavaScript | http://en.wikipedia.org/wiki/ECMAScript Um - what? Brief history of JS = Clear as mud...
Altogether different beasts: Both potentially delicious (or dangerous), but not actually derived from the same animal. Similar in name: JavaScript is to Java as Hamburger is to Ham.
1996: IE 3.0 ships with "JScript" (for copyright purposes). In 1995, MS begins to ship Internet Explorer with Windows 95. For Netscape, it was the beginning of the end. Microsoft also reverse- engineered JavaScript, as "JScript." http://en.wikipedia.org/wiki/Internet_Explorer
Created at Netscape "ECMA TC39" Committee responsible for evolving the language Who's responsible for JavaScript now? {to name a few... http://en.wikipedia.org/wiki/JavaScript | http://en.wikipedia.org/wiki/ECMAScript TM of Oracle (via Sun) Defines the ECMAScript DOM API
JS browser support is pretty good. JavaScript (ECMAScript 3.0) is supported fairly consistently in all major browsers. ⾨ This is Wikipedia's compatibility table* for: – Trident (IE) – Gecko (Firefox) – WebKit (Chrome & Safari) – Presto (Opera) * I realize those are rendering engines, not specific JS engines (which change names more rapidly). It's how Wikipedia lists 'em. http://en.wikipedia.org/wiki/Comparison_of_layout_engines_(ECMAScript)
JavaScript is that friend in high school you secretly had a crush on, but was always hanging out with that sleazy boyfriend, DOM. Nice > What a punk http://w3.org/DOM
The Document Object Model (DOM) is what allows JS to interact with XML/HTML, ala: window.document.getElementsByTagName('*'); The DOM is stewarded by a different group than governs JS. Browsers also implement it slightly differently. For instance, IE historically didn't treat whitespace as text nodes, even though the official DOM spec says it should. http://w3.org/DOM
Loosely translated: "You'd better lose yourself in the music, the moment. You own it, you better never let it go... You only get one shot, do not miss your chance to [load]." (with apologies to Eminem) window.onload http://en.wikipedia.org/wiki/8_Mile_(film)
Really, it's not the fault of jQuery, nor of any other capable JavaScript libraries: Dojo, MooTools, Prototype, Sencha, YUI... As is almost always the case with code, the problem is actually a human one. We've become complacent and forgotten (or never learned) how JavaScript works. Beware the danger of abstraction & illiteracy. http://ejohn.org/blog/javascript-language-abstractions
1994: Håkon Wium Lie proposed CSS. Initially it was called CHSS, ("Cascading HTML Style Sheets"), but was later shortened to simply CSS. 1996: The first browser to support CSS was Internet Explorer 3.0, followed closely by Netscape Navigator version 4.0. http://people.opera.com/howcome/2006/phd
1998: "Web Standards" advocacy begins. http://w3.org/Style/LieBos2e/history/Overview.html The box model isn't fixed until October 2006, release of IE7.
The "dark side" = developing for 1 browser. Oh, what... Like you never photoshopped you vs. yourself with a lightsaber? C'mon! http://flickr.com/photos/nathansmith/32757176
"Those who cannot remember the past are condemned to repeat it." – George Santayana http://en.wikipedia.org/wiki/George_Santayana "My 'pure CSS' demo only works in WebKit"
Realistically speaking, XHTML 2.0 would've been a very tough sell, from a practical standpoint. It was extremely rigid. A page simply would not render, if it wasn't perfectly formed from an XML structure standpoint. Oh, and it would've done away with . Oh noes!
Technically, "HTML5" is now a misnomer. (But, it's too late. Marketing already got ahold of it.) HTML is to be considered an ever-evolving "living standard". The "WHATWG" — Web Hypertext Application Technology Working Group — will continue to work on HTML, and the W3C will "snapshot" feature sets periodically, and tag them with incremental version numbers: HTML5 (and presumably, HTML6, etc). Thus, no more version numbers in DOCTYPE...
You don't have to type extra junk anymore. <br/>alert('This is some inline JS.');<br/> <br/>/* <![CDATA[ */<br/>alert('Are you kidding me?');<br/>/* ]]> */<br/>
type="text/css" media="all" /> Note: Media queries best defined via @media in a single stylesheet anyway, to avoid unnecessary HTTP requests. (No? Me neither, so why "type" it?)
You can't do that! What about the validator? Relax. It's valid. HTML5 is no longer a sub- set of SGML like all versions of HTML before it. Nor is it a spin on XML, like XHTML 1.x was. HTML is just HTML now. This is how browsers always treated (X)HTML anyway. I know what you XHTML purists are thinking: (phew!) http://en.wikipedia.org/wiki/HTML
2011: IE9 supports SVG (proposed in 1999). Examples of Dojo.js charts To be fair, IE9 renders SVG very fast, via hardware acceleration. Konqueror (WebKit predecessor), was the first browser to have built-in SVG support, in 2004. http://user.sitepen.com/~dwalsh/dojo-charting.html
SVG is like construction paper. Layers retain distinct shapes. SVG files can live without JS. http://flickr.com/photos/124330160/2127121118 And, each layer can respond to mouse events!
I won't cover or in detail during this talk, but two helpful JavaScript libraries are worth noting... Raphaël (SVG) – Dmitry Baranovskiy Processing JS (Canvas) – John Resig http://raphaeljs.com http://processingjs.org
Metaprogramming Haml => HTML Sass/Compass => CSS CoffeeScript => JS Note: Yes, I'm sure there are many, many more examples in the wild. But my time is finite, and this is what I'm familiar with. http://haml-lang.com | http://sass-lang.com | http://compass-style.org | http://coffeescript.org
Personal note: After giving 'em a try, I am becoming more a fan of meta languages that treat whitespace as significant. Usual disclaimers apply: "It depends." Your mileage may vary. No purchase necessary. Machine-wash only. Enter at own risk. Batteries not included. Void where prohibited, etc.
I could go on. But I won't. (Sorry Jina) Note: Don't steal another presenter's topic. Note: Jina Bolton is presenting on Sass later today. Don't miss it!
Okay, so abstraction for HTML and CSS is fine. It saves keystrokes, and those languages are pretty #yawn anyway, right? I mean, they're declarative, so of course we should automate writing them. But this is a JS conference, right? Do not touch my JavaScript. I repeat...
Nuthin' wrong with being overly clear. var joe = 1; var sue = 2; var bob = 3; Minifiers like Uglify JS can handle removing repeated var keywords. Put that burden on automation, not yourself. https://github.com/mishoo/UglifyJS | http://marijnhaverbeke.nl/uglifyjs
I just tell JSLint: "Hey JSLint... Shut up." Actually, JSLint.com is a great tool for checking for JavaScript errors. But validation is a means to an end, not the goal itself. If you want to ensure JSLint compliance, there's CoffeeScript... http://jslint.com
One last example... (Sorry Brandon) # CoffeeScript: happy = true unless raining // JavaScript: var happy; if (!raining) { happy = true; } That's hawt. Note: Brandon Satrom is presenting on CoffeeScript later today. Don't miss it!
(Free) fonts used in this presentation. Anonymous Pro http://j.mp/font_anonymous-pro Hand of Sean http://j.mp/font_hand-of-sean Titillium Text http://j.mp/font_titillium-text Lady Ice REDDIRT.js logo http://j.mp/font_lady-ice SteelFish http://j.mp/font_steelfish (Listed in order of appearance)
nathansmith
aicocco
uxevents
uxaustralia
ajstarks
mewmo
hjmkth
lovchikov
visional_engineering_and_design
chriscoyier
zenorocha
reverentgeek
malarkey
ufuk
morganepeng
jonrohan
eitanlees
jakevdp
3n
mthomps
brad_frost