spliceOne performance

[browserify]

spliceOne performance

[goto-bus-stop]

The reason we use it is because node.js does, and events tries to stay as close as possible to the node.js source code so applying changes from future node.js updates is easier.

node.js uses it because they've benchmarked it and found it faster, although of course that can change over time with V8 updates!

Right now, spliceOne is faster for me in both cases on Firefox:

And on Chrome the difference is negligible:

I think typically with event emitters, the most common case is removing a listener from the tail, and removing listeners from somewhere in the middle. Unfortunately I can't manage to log in to jsperf to add that last case :(