HTML5 Dev Conf in San Francisco was a blast.
This post is long overdue. I've had these notes sitting in Ghost since the conference but have been too busy to clean them up, remove proprietary comments, etc.
These are the notes from some of my favorite talks. There were way too many talks to attend -- I'll have to take my team next year to get more coverage!
Kyle's working on a Kickstarted, open-source book called You don't know JS that I plan on reading when it comes out.
Leveling up in AngualarJS
This was by far my favorite talk of the conference. Alicia packed her session full of delicious angular knowledge AND a simple AngularJS recreation of 'Mario'.
Definitely check out the slides. I can't seem to find the video from her talk, but if I do I'll post it.
The Future of Angular
I wanted to sit in on this talk but alas I had to take a customer sales call (they do pay the bills after all). After skimming the slides, most of the material was beyond my near-term vision (3-6 months). I'll put it on the shelf and revisit late 2014, especially as we see what shakes out in ES6 spec.
I've briefly looked at d3.js numerous times but each time I've been overwhelmed by the complexity. Ian is a bit of a d3.js and data superhero and his talk provided me great insight in getting going. I'm certainly much less 'scared' to get my hands dirty.
However, unfortunately the slides he's posted don't do his session justice.
One take away point is to checkout a tool he created, tributary.io. You can code/view your d3.js based visualizations (including importing csv/json data) in realtime. It's a pretty awesome playground.
I also highly checking out his other tutorials.
This talk was right up my alley. I'm a huge fan of continuous deployment - rapid testing improves developer productivity. A lot of the talk was a bit 'rah-rah!' for me, but I could tell most of the audience appreciated it.
My take away points:
- Consider enabling nightly deploys
- Add longer-running tests on staging that trigger automated deploys to production on success
- We should play with Grunt (or now gulp.js)
- Play with Jenkins parameterized builds
This was a cool talk as it walked through the different work flows of an html5 team (Component Developer, Designer, & Application Developer).
This talk was a good walk through of the major modules and APIs in WebRTC. As usual, I left the talk feeling that WebRTC is simply a remake of SIP with all of the nasty complexities of distributed signaling. The multicast audio/video streams will also continue to be a major shortcoming if you want more than 3-4 participants in a conference call.
One question I've been pondering is how to hook WebRTC microphone audio into the WebAudio domain. This link may provide some insight.
I've played with node-webkit a fair amount so there wasn't much that was new for me in this talk. I'm looking to use node-webkit to provide a common user experience (and codebase!) between our browser clients and native clients.
I'm also excited to note from my experimentation that browser security warnings when accessing Microphone/Video are not displayed when you're running local content using node-webkit.
In my opinion, this is probably best way to distribute an html5 voice communication application that is consistent across browser, mobile, and desktop platforms.