On Fri, Jun 1, 2012 at 8:02 PM, Isaac Schlueter <[email protected]> wrote: > It's not just "deciding to not take the advice". Show me a real world > use case where you need the current nextTick semantics. Like, a > production application that will be broken by this change. I'm aware > of several production applications that are suffering without the > proposed change, and there are many ways that we can make things fine > for the problems presented in this thread. >
Given direct access to the NPM database, would it not be a useful exercise to go through, from the more popular packages, to see where nextTick is used, and just give it a visual eyeing that it's being used in a way compatible with this change? Even if someone did the top 20 packages that might be something useful to do. I gave a quick look through Haraka and it looks like the proposed change would be fine (I think - there was one case where I had to add it into sqlite callbacks that I'm not 100% sure of), but obviously there's a lot more code out there than my stuff. It does make me wish we had a better testing culture in Node, like Perl has with CPAN and cpantesters (see http://wiki.cpantesters.org/wiki/WhatIsCPANTesters) - basically a group of people contributing smoke testing machines for different versions of Perl (or Node in our case) that download libraries off CPAN and run the test suites, and upload the results back to base. These sorts of setups can really help weed out problems introduced with development versions. Matt.
