-
Notifications
You must be signed in to change notification settings - Fork 66
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
This isn't really mythbusting, just spreading myths? #25
Comments
I collect known tips that are true trying to void noise. Working on progress, but not problem if you think that something is not true. Comments and bibliography are for something. See for example #17. It's easy to say where is the benchmark, but see #20. Also, Most of the time code need time running to be optimal and not easy to demonstrate in a benchmark. Could be nice stablish a guidelines for determinate if something is or not a myth. |
ops, I closed accidentally! |
Did someone say 'ES6 vs ES5' benchmarks'? |
@tomByrer awesome resource! I'm going to study and add it as permanent resource 😄 In fact I think to set a baseline could be |
I like the idea, but two pieces of feedback:
The colour scheme is dark and is okay, in general. However code samples look terrible, particularly comments on them which end up being a dark text on dark background situation.
The main point: None of these appear to be actual mythbusting, at least that I've seen so far. No benchmarks or other repeatable bits of code. Just "Hey this is better!", which amounts to little more than myths in and of itself. Mythbusters was all about taking myths, creating an experiment and figuring out if it was true or not. e.g. http://mythbusters.js.org/workflow/math.html at the very least there should be some simple microbenchmarks there.
The text was updated successfully, but these errors were encountered: