News for hackers. Stuff that matters.
Re:Don’t let jQuery’s $(document).ready() slow you down by jakevoytko on Thursday August 19, 2010 @08:23AM (#1617141)
Important takeaway: Use Firebug's network monitoring to find out what actually happens when your page loads.
Re:Don’t let jQuery’s $(document).ready() slow you down by dododo on Thursday August 19, 2010 @08:34AM (#1617158)
the rest seems to be summarised as: don't wait for things you don't need to wait for.

$(document).ready() can be a bit of a sledgehammer in terms of latency.

Re:Don’t let jQuery’s $(document).ready() slow you down by pak on Thursday August 19, 2010 @10:18PM (#1619301)
Don't just base your conclusions on one page load, though, as this article seems to do. I wish there was a tool for Web Inspector/Firebug to select various elements over a series of page loads and give me statistics after e.g. 100 refreshes. Page load is highly variable and dependent on things like caching server-side, client-side, within the database, etc. as well as network conditions so repeating the tests is important.
Re:Don’t let jQuery’s $(document).ready() slow you down by Encosia on Friday August 20, 2010 @12:43AM (#1619531)
None of those conclusions are based on the two screenshots shown in the article. I just set those up and included them for illustrative purposes. The article's points themselves are based on my experience routinely using those optimizations in production.

Sorry if that wasn't very clear in the article.