Epic win. I love this site, I think it's awesome. It looks awesome, it has awesome stuff on it, so it can really only get... awesomer... if it's being upgraded. However, I do have some recommendations regarding what's under the hood -- the client-side code, to be specific. While I love this site, I do often have to deal with excessive RAM usage and slow loading times when I visit here. External streamlining would make the site epically awesome, but external streamlining [i]and[/i] internal streamlining would make the site [i]infinitely awesome[/i]. To that end, I'd like to post my ideas, which, given the volume of comments and traffic on this website, will likely be ignored or unnoticed. - I'd suggest recoding the current JS -- or discarding most of it and starting from scratch. Microsoft's AJAX library should probably be avoided if possible, both because of code bloat and because of the use of frowned-upon practices (such as modifying Object.prototype). Just to demonstrate the former issue: when I set NoScript to allow Bungie.net's JavaScript to load, the load time increases radically, sometimes even tenfold. - Speaking of which, you may want to add code so that the site works without JS. A lot of people browse the web without JS due to security reasons, and I've found that much of Bungie.net is unusable when JS is off. It might be easier if, instead of wrapping the entire page in a non-functional FORM element, smaller FORM elements were used for individual forms (e.x. a FORM for comments, a FORM for ratings). If necessary, JS could be used to replace ugly, difficult-to-style form controls with more customizable equivalents, should a user have JS enabled. - I know for a fact that you have jQuery -- I've seen it in your source code, though a sizable portion of your code doesn't appear to use it at all. In addition to radically streamlining interaction with the DOM, jQuery also has some functionality for AJAX, and could be considered an AJAX framework. You already have it; I'd strongly recommend using it -- if not for DOM and AJAX, then at least for DOM operations. - Removing support for pre-DOM browsers (or better yet, pre-IE7 browsers) will help reduce code bloat and streamline the site's operation. The site's CSS would especially benefit from the obsoletion of IE6, as child selectors will become usable -- child selectors are vastly more efficient than descendant selectors (fewer elements to check when evaluating them), and their usage will allow you to cut down on the number of class names you use. - Considering that the layout is being altered, I would expect some HTML changes to occur. One thing that I really hope to see is the avoidance of tables for layout. While the designers of the current layout did a good job of using divs, there are small spots where tables are used as an alignment mechanism rather than a means of conveying data -- I spotted a layout-table on a Halo 3 File page not too long ago. (Chances are that it's too late in the development cycle to do any of this, assuming that these ideas aren't either absolutely terrible or incredibly obvious. But I just thought I'd throw my two cents in, so to speak.)