YUI Theater: BayJax Tech Talks from Nicholas Zakas, Isaac Schlueter, and Matt Hackett

September 17, 2009 at 12:49 pm by Eric Miraglia | In Development, YUI Theater | 7 Comments

Nicholas C. Zakas speaking at Yahoo on September, 8, 2009.

We had a terrific September meeting of the BayJax group here at Yahoo! a few weeks ago, and videos are now ready from those sessions. If you’re viewing this post in an RSS reader, you may need to click through to watch the videos (the downloadable versions are much lower-resolution and formatted for iPod/iPhone playback). For best results, toggle into full-screen mode.

Nicholas Zakas: “Scalable JavaScript Application Architecture”

Isaac Schlueter and Matt Hackett: “Server-Side JavaScript”

Other Recent YUI Theater Videos:

Subscribing to YUI Theater:

Find conversations: bloglines | technorati

Share and extend: Bookmark with Yahoo! My Web | Bookmark with del.icio.us | digg it! | reddit!

7 Comments »

RSS feed for comments on this post. TrackBack URI

  1. “Scalable JavaScript Application Architecture” slides available anywhere? can’t read the demo code…

    Comment by Henry Ho — September 17, 2009 #

  2. found it:
    http://www.slideshare.net/nzakas/scalable-javascript-application-architecture

    Comment by Henry Ho — September 17, 2009 #

  3. A better title would be:
    “Composable JavaScript Application Architecture”
    or:
    “Modular JavaScript Application Architecture”

    The term “scalable” is more usual for topics tied to performance.

    Comment by Preston L. Bannister — September 23, 2009 #

  4. [...] for Web Developers. The full slides to the talk can be found at SlideShare, which can accompany the video of the talk available at the YUI [...]

    Pingback by Bayjax: Scalable JavaScript | Engineering Blog - Genius.com Marketing SaaS — September 23, 2009 #

  5. I started to develop a “scalable application architecture” a few months ago. Your speech has pointed out that i’m on the right way. Moreover it has given me some further inspiration for the javascript part. Thank you!
    Where my approach differs the most from yours, is that my html/css is based on OOCSS. Because all modules have a .mod and a .mod{moduleName} class, i’m able to automatically register all modules on the page by using this classes to instantiate the appropriate module (ie. new Nx.Module.{moduleName}()).
    What do you think about this approach?

    Comment by Remo Brunschwiler — November 17, 2009 #

  6. @Preston – The definition of scalable is “capable of being easily expanded or upgraded on demand”, which I believe fits this approach very well.

    @Remo – That’s a fine way of determining which modules to register. You might also want to consider using the element’s ID as a way to do the same.

    Comment by Nicholas C. Zakas — November 17, 2009 #

  7. ID’s have the disadvantage of uniqueness. Because I wanted to be able to use the same module more than once on one page, I decided to go with classes (despite of the minimal performance loss). I will soon be ready for a first release of the framework. Would be great if you found the time to have a look.

    Comment by Remo Brunschwiler — November 21, 2009 #

Leave a comment

Note: Comments are moderated for first-timers. Spam deleted.

XHTML: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Hosted by Yahoo!

Copyright © 2006-2010 Yahoo! Inc. All rights reserved. Privacy Policy - Terms of Service

Powered by WordPress on Yahoo! Web Hosting.