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

By YUI TeamSeptember 17th, 2009

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”

src="http://d.yimg.com/m/up/ypp/default/player.swf" type="application/x-shockwave-flash"

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

src="http://d.yimg.com/m/up/ypp/default/player.swf" type="application/x-shockwave-flash"

Other Recent YUI Theater Videos:

Subscribing to YUI Theater:


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

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

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

  3. [...] 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 [...]

  4. 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?

  5. @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.

  6. 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.