Full Frontal Javascript Conference
-
date post
12-Sep-2014 -
Category
Technology
-
view
831 -
download
1
description
Transcript of Full Frontal Javascript Conference
http://2009.full-frontal.org/
Christian Heilmann
Frontloaded and zipped up - do loose types sink ships?
1. JavaScript gets the blame for server-side security issues
2. Improve security with Caja – subset of JavaScript
3. YQL – JavaScript ‘SQL’ to access data via Web Services
http://www.wait-till-i.com/2009/11/21/frontloaded-and-zipped-up-the-full-frontal-2009-keynote/
select farm,id,secret,owner.realname,server,title,urls.url.content from flickr.photos.info where photo_id in( select id from flickr.photos.search where woe_id in( select woeid from geo.places where text="london" ) )
Robert Nyman
Javascript from birth to closure
1. JavaScript has nothing to do with Java (no, really?)
2. Lots of slides of stuff we know…
3. Odditiestypeof(NaN) == number
4. Usefulshash[‘val’] == hash.val
Peter-Paul Koch
W3C Widgets
1. Many, many mobile browsers – many on Web Toolkit, but not Blackberry or iPhone!
2. They all have quirks
3. W3C Widgets are local applications written in HTML, CSS, and JavaScript
4. They cannot access phone data – geo data, address book, etc.
http://www.quirksmode.org/http://www.quirksmode.org/presentations/mobilebrowsers/fullfrontal09.pdf
Stuart Langridge
New things that HTML5 provides for JavaScript Hackers
1. No slides – forgotten most of what he said…
2. Main thrust – selectors being implemented in many new browsers, but different support and syntax in each browser!
3. Libraries will take advantage of these new features, so keep using your favourite library (e.g. jQuery 1.3.2 uses new Sizzle selector engine)
Todd Kloots
More accessible user interfaces with Aria
1. Most browsers now support screen readers for the visually impaired
2. ARIA provdes roles (menu), properties (hasPopUpMenu) and states(enabled)
3. Keyboard accessibility (e.g. home media center)
4. Discoverability
Jake Archibald
Optimising where it hurts
http://www.jakearchibald.co.uk/jsperformance/
1. Optimisations can make no difference (e.g. bitwise v slice)
2. eval() is usually bad for performance
3. Scope all vars
4. Creating DOM elements; create html as string, then insert
5. Use selectors correctly:$(‘div#id’) v $(‘#id’)
$(‘.class’) v $(‘#div .class’)
$(‘:header’)
Simon Wilson
Web API mischief with Javascript
Simon Wilson
Server-side JavaScript: Event-driven web serving
http://simonwillison.net/2009/Nov/23/node/
1. Something genuinely new and exciting
2. JavaScript is ideally suited to event-driven programming:
1. Event handlers
2. Callbacks
Standard Web Servers
Event Driven Web Servers
Clean, Easy Comet
AJAX call with long poll (10s)
Reply?
ProcessReturn Data
Server
Wait
Yes
No
Node.js
1. Small, simple
2. Lightning fast, highly efficient
3. But:1. Untested scalability
2. Very new not available at hosting companies
Worth a punt?
http://nodejs.org/http://wiki.github.com/ry/node
Conclusions
1. A JavaScript conference in in the UK! Over 100 delegates Completely sold out
2. Exciting new developments as browsers implement new features
3. Libraries the best way to future-proof at the moment
4. Mobile is a minefield
5. IE6 now down to about 35% of users
6. Book early for next year
http://2009.full-frontal.org/