I didnt look to closely, but it looks like you are creating a closure around the comments var for your event listener function. The problem is that you are doing this within a loop, meaning the comments var changes after each iteraion, probably ending up in something you hadnt intended
This is what I have set up. A Git repository on the server. I push all my code to the repo via ssh.
On the server there are Dev, Staging, and Production environments. Dev and Staging are bare checkouts from the git repo. I have deploy shell scripts that automate deploying to both (checking out from source control and running database migrations). The process should be that code is deployed to Dev, then Staging and finally to Production.
The Production environment is NOT a checkout from source control. It is an exact mirror of the Staging environment. And the deploy script to production does the following:
- tags source control with the new release number
- creates a tar.gz backup of the production directories
- does a database backup dump
- then uses rsync to copy files from the staging web directories to the production directories.
- lastly runs migration scripts on the prod database
Steve Souders is the man who was the head of Yahoo's Exceptional Performance Team, which gave us these rules for speeding up your website: http://developer.yahoo.com/performance/ and also YSlow.
Cuzillion is something he seems to have made to give you a generalized example of what components affect your performance and by how much. So it allows you to test a fabricated example rather than a specific website.
if you are still using the extension I would suggest re-installing once more. I made some fixes and added a few other things, as well as integrating the Firefox update manager. So if you re-install once more, Firefox will automatically find new updates to it for you from here on.
For finding those kinds of mistakes use jslint (http://jslint.com), though it doesnt catch calling a function with the wrong number of arguments (which may be what you intended anyways). If you download the source you can easily write a custom command in vim or emacs to run the current buffer through jslint.
I built a HackerNews firefox extension a few days ago to monitor new comments directed towards you or your submissions which you could port pretty easily to your site if you were interested. Or if you build an api to a users threads/comments (need just be an RSS feed) Id port it for you if you wanted it.
Google and Yahoo can do it because they can take advantage of their scale to monetize ads, as well as their diversity of products (profitable products can help pay for the unprofitable ones).
Which is exactly the author's point. He says that small companies are forced to swing for the fences in terms of user-base because a) that is all advertisers are interested in and b) the competitors (such as Yahoo! and Google) offer free alternatives.
I dont think it reasonable to set Yahoo or Google as the measuring stick of success as those companies are clearly way out ahead of anyone
Traversing the entire DOM on page load and rewriting all links for large pages would also slow down the page though.
Also rewriting links seems too intrusive for my tastes and means I cant "Copy link location" which I frequently do. I like the idea, but I personally would have just used a single "click" event handler on the entire page using the capturing phase and hijack links to redirect through your site first, rather than doing a rewrite for every link in the dom