Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usage of native map, filter, forEach, etc. if available (impressed by jQuery 1.8+ way) #76

Closed
wolfflow opened this issue Feb 4, 2013 · 3 comments

Comments

@wolfflow
Copy link
Member

wolfflow commented Feb 4, 2013

Is it suitable to use the native map, filter, forEach, indexOf functions
in _.map, _.filter, _.each, _.contains
if browsers support these features?

@eskimoblood
Copy link
Contributor

Native methodes are not always the fastes, take a look at this talk by John-David Dalton about lodash: http://www.youtube.com/watch?v=dpPy4f_SeEk

@raimohanska
Copy link
Contributor

On my opinion, all performance related improvements should be verified using performance tests. Right now, there's a simple performance tests for running a somewhat complicated bacon.js setup in node.js (see #56 ). I guess we should be running perf tests in different browsers to see what the effect of this kind of changes would be to actual users.

@raimohanska
Copy link
Contributor

Will close for now. If there's proof (perf test) for performance improvement gained by using natives, I'll merge your P.R.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants