Superhero.js: articles and videos on building large JavaScript apps

I'd consider adding some articles from <a href="http://rmurphey.com/" rel="nofollow">http://rmurphey.com/</a> ( that's where I started reading about large javascript apps), <a href="http://peter.michaux.ca/" rel="nofollow">http://peter.michaux.ca/</a> (very interesting), and even some of the demo apps from <a href="http://rightjs.org/" rel="nofollow">http://rightjs.org/</a>, like <a href="https://github.com/MadRabbit/typing-ninja" rel="nofollow">https://github.com/MadRabbit/typing-ninja</a>, are pretty good for learning javascript. IMHO.

Great looking site, good font, and an invaluable collection of resources. But the name is confusing - the .js in it suggests it's a javascript library to me?<p>Also your github link 404s.

Honoured to be one of the superheroes! :)

I've been trying to come up with a javascript module pattern for my rails apps. Right now, I use the Foundations javascript libraries, however those are very generic. I'd like to do something like Foundation does: have separate js files for accordians, sliders, tooltips, etc...I've been looking at the module patterns, however, as a new-comer to js (I'm ruby backend dev), there seems to be so many ways (<a href="http://www.adequatelygood.com/2010/3/JavaScript-Module-Pattern-In-Depth" rel="nofollow">http://www.adequatelygood.com/2010/3/JavaScript-Module-Patte...</a>), to do the same thing, and I'm at a loss trying to figure out which one to start out with.<p>Anyone facing this issue? How have you gone about starting out? Thanks.

Really cool!<p>I'm biased, but the WebAPI proposals that come with Firefox OS deserves an entry in the "On the horizon" section.<p>If you want to hear more about them you should join in on todays IxDA!<p>wiki.mozilla.org/WebAPI

Content is very good and I've signed up for the newsletter. Really like the site design. What the proper term for this type of graphic? Is there any repositories of free graphics of this type for non-commercial use?

Thanks for the work! At the very least this allows me to consolidate a multitude of bookmarks I struggle to keep organized.<p>As someone who will probably be visiting this resource a lot, I think it would be helpful if a User could navigate to each section from the initial scene. I feel like scenes one and two can be merged in to a more valuable experience from the start.

I have to admit I chuckled when I saw that one of the authors is @vandelay :)<p>Seinfeld reference or just the name of the author?<p>This is an invaluable resource for people interested in client-side apps, thank you very much for packaging all this knowledge in a convenient and easy-to-browse gift bag guys.

I don't see anything that's specifically for 'Creating, testing and maintaining a large JavaScript code base'. These just look like regular (but very good), oft-cited javascript resources.

Am I missing something or is writing documentation deemed unnecessary for large apps?<p>Personally, I use YUIDoc which has some serious flaws, but I haven't found anything better yet.

I like this. It seems that the order the items could be changed. Reading through the beginning Javascript, the third link would fit better as the first.<p>But overall, it's good.

fyi: I can't view this page within my corp network. This Websense category is filtered: Potentially Damaging Content. Sites in this category may pose a security threat to network resources or private information, and are blocked by your organization.

Awesome stuff. Thanks for putting this together.

no mention of the closure compiler. pretty insane in my opinion, tis like static analysis and tree shaking is a bad thing.

why was "Secrets of the JavaScript Ninja" book excluded from the listing?. What criteria made the final list?

Nice! Keep up the good work!

nothing special.

While javascript has very specific issues and problems, I'd like to see more "generic" programming resources on how to develop fat clients, wether they are desktop or web , how to structure an app , etc ...<p>You dont learn much if you are only applying solutions that are relevant to javascript.<p>Since most of devs know javascript , it can be used to express "generic" algorithms , but OOP design patterns not so much. Yet a large application you need those patterns. And these are the same patterns one would use to code Java , C++ , C# , obj-c mobile/desktop clients. But i guess javascript flexibility, and the "DHTML battery included" , DOM &#38; CSS gives one the impression one doesnt need them .