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

Add jsPerf disclaimer #20

Open
Kikobeats opened this issue Aug 31, 2016 · 2 comments
Open

Add jsPerf disclaimer #20

Kikobeats opened this issue Aug 31, 2016 · 2 comments

Comments

@Kikobeats
Copy link
Owner

According to the author, JSPerf is used incorrectly, 70% of the time.

http://www.slideshare.net/mathiasbynens/using-jsperf-correctly

@tomByrer
Copy link
Contributor

tomByrer commented Sep 3, 2016

Tricky to have 'real world tests'. For tight loops, if the JS compiler or runner doesn't optimize the code, the CPU might.

@Kikobeats
Copy link
Owner Author

Kikobeats commented Sep 3, 2016

Exactly. Another thing: jsPerf is down 😄

Maybe you can help me with this task!

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

No branches or pull requests

2 participants