"We actually started using this technique in jQuery core, recently, to detect functions and arrays (search for isArray: in the [latest nightly](http://code.jquery.com/nightli...))." - John Resig
"Boston is a great city, it has a good mix of history and tech. I dislike the valley since it feels like it just popped up in the last couple years (which is roughly true). Living in the Cambridge/Somerville area is great - I live inbetween Harvard and MIT and there's a great mix of intelligent people and culture." - John Resig
"Running a test 100,000 times may sound good, in theory, but what about browsers that are moving towards tracing optimizations? Firefox 3.1 is landing tracing support and both Chrome and WebKit can't be too far behind. A couple months ago I would've agreed with you on this, but not so much anymore. I think it's far more important, at this point, to run tests for a set about of time (allowing you to then calculate a # of runs/second rate). Granted the tracing engines will still be significantly faster - but running for a fixed large number of runs isn't a complete solution." - John Resig
"Well, except for the fact that both Chrome and Firefox 3 are perfectly capable of producing accurate time results - so there obviously is a better solution out there. In the ticket in which the Firefox team [1] fixed the bug they detail the solutions that they used to fix it. Just because all the other browser vendors phoned it in by using nothing more than the standard tick count doesn't mean that there's nothing better. I would disagree that this is a knowledge issue here, as well. It certainly wasn't obvious to the WebKit, Firefox, and Chrome teams who were all happily testing on Windows XP using bum tests - and those are some pretty smart people (IMO). [1] https://bugzilla.mozilla.org/s..." - John Resig
"I don't think I said that Lightbox was innovative - just that it was a relatively new UI convention that was popularized on the web. I don't think anyone is denying that it has become insanely popular (regardless of the fact that some people seem to genuinely dislike it)." - John Resig
"For the vast majority of people the answer is Yes. I assume that it would be "unjustifiable" if the download size was too large and/or if you knew enough to already develop a framework of your own *and* enjoyed dealing with cross-browser issues. For me 190kb of uncompressed JavaScript is unacceptable - but 15kb compressed for another library (say, jQuery) is very enticing. Prototype and Scriptaculous can be compressed to within the 20-30kb range - which is also acceptable. It seems like you 1) Have been doing JavaScript development for a long time and 2) Enjoy tackling the harder problems that libraries tend to make simple. So, for you, no a library may not be justifiable. Or you may want to look into [JavaScript minification and GZip compression](http://www.julienlecomte.net/b...) - which may help to make it palatable." - John Resig
"We should probably move this discussion off-Reddit but do you still have the page demonstrating the bug? (It seems to 404 now.) Also, yes, I would be interested in seeing code in which jQuery is not optimal - always looking for ways to improve!" - John Resig
"I assume you're talking about the built-in .hide()/.show() animations. We've been considering that for a while now - but it has far greater potential to break layout than what we currently have. That being said we hope to possibly land something here soon. In the meantime you can do: $("#test").animate({ // What we have now width: "hide", height: "hide", opacity: "hide", // What we could add paddingTop: "hide", paddingBottom: "hide", paddingLeft: "hide", paddingRight: "hide", marginTop: "hide", marginBottom: "hide", marginLeft: "hide", marginRight: "hide", borderTopWidth: "hide", borderBottomWidth: "hide", borderLeftWidth: "hide", borderRightWidth: "hide" }, "slow");" - John Resig
"It's quite hard to quantify irregularities in animations - have you been able to do so with any of the jQuery animations? It would certainly help us to be able to improve them." - John Resig
"Once you're in edit mode just hit the 'Run' button to re-run it (right now the only way to "go back" to the formatted code mode is to reload the page - of course then you lose all your changes). Eventually I'd like to have each slide persist a little revision history (so you can revert back to the original slide - and be able to reload the page without losing your changes)." - John Resig
"Awesome, glad you found it to be useful. I suspect that this talk (in its current state) is most useful for people who've used JavaScript before. When I gave this talk at the Web 2.0 Expo it was pretty obvious that there were some in the audience who had never used it before, so I had to spend some time explaining why the syntax for object literals was different from other syntax used in the language - stuff like that." - John Resig
"Unfortunately there wasn't any video recorded of the talk (which was about 3 hours long). I could record something but I'm not sure how useful it would be (since it pretty much requires interaction with the people watching - having no feedback would make the presentation kind of dull, imo). Maybe I could give the talk as a ustream livecast and have people join in." - John Resig
"I think you may have mis-read me - obviously I can't really point someone to the candidate's web sites (since those are huge sources of bias) but rather unbiased third parties (such as domain experts) who are able to provide critiqued analysis of the positions that the candidates take. For example, the NPR interview with Jonathan Oberlander was excellent (based upon his article for the New England Journal of Medicine on the candidate health plans). I learned a lot about the positions and felt much more informed." - John Resig
"Some links that I plan on passing along, so far: * [The Washington Post on the consumer tax plans](http://chartjunk.karmanaut.com...) * [Political scientist Jonathan Oberlander analyzing Health Care policies on NPR](http://www.npr.org/templates/r...) I want to have reasonable conversations with my family (who are still undecided) and so I'm looking for more information (beyond what you can find on the candidate's web sites). Unbiased third-parties would be preferred!" - John Resig
Also, have them watch/listen to the candidates' speeches from the conventions. My previously undecided mother-in-law did and she made up her mind. - Claude Betancourt
"Animations. By having animations actually be able to run faster the probability for smoother animations increases. Combine this with the "process per site" architecture (aka. less chance for a garbage collection cycle to occur) and I'm willing to lay down money that Chrome will have the smoothest JavaScript animations of any browser on the market." - John Resig
"Internet Explorer 8 is still in very, very, rough shape. This suite is actually quite good at testing the memory capabilities of browsers. I've been able to crash WebKit, Gecko, and Internet Explorer - some are just more responsive at fixing the crashes than others." - John Resig
"I'm confused - the Dromaeo v2 tests do include library independent DOM benchmakrs: DOM attributes, DOM modification, and DOM querying - none of which rely upon JavaScript libraries (they're just pure tests of the individual DOM methods/properties). I guess I could look at GQuery, but I'm not in a huge rush (wanted to get the major libraries tackled first)." - John Resig
"I didn't leave out the JavaScript tests, at all. I'm referring to the second version of the Dromaeo suite, which includes JavaScript, DOM, and JavaScript library performance tests: http://v2.dromaeo.com/ As it stands, v1 of Dromaeo is pretty much just a subset of the tests that are in SunSpider. It's better to just tests SunSpider and v2 Dromaeo, at this point." - John Resig
"The V8 engine is really fast at function calls - it's not clear if they designed the test to emphasize that, or if they built the tests then built the engine to do good at it. Regardless of this fact - it's still a really fast engine - it's just not OMG crazy-go-nuts." - John Resig
"As I mentioned in the comments of the blog post: Correct, a process per-tab is the same as IE. But that is not the point that I was making: IE doesn't provide a Tab Process Manager - allowing you to monitor how much memory, CPU, and bandwidth your tabs are utilizing. *That* is the killer feature - not the "process per-tab"." - John Resig
"That was intentional - the game doesn't work in IE (IE doesn't have Canvas support) - no need to enable to code for people who won't be able to enjoy it!" - John Resig
"The only thing stopping me is the one gotcha: If jQuery is loaded dynamically (say via a dynamic script tag) then the last script on the page will be executed twice - which is hardly desirable. I don't have a good solution for this yet, but if I find one, I'll definitely lean strongly towards this." - John Resig
"Firebug uses the internal JSD service in Firefox - and it has... to put it gently... not aged well. It's been a long time since it's seen a serious update. We're [proposing a bunch of changes](https://bugzilla.mozilla.org/s...) that will help to modernize the service and give us better feedback (so that we, in turn, can actually help web developers)." - John Resig
