Needs more context about js-mythbusters

[Kikobeats]

Thanks for your comment!

I think you are right, because I started this project from my javascript background and I assumed things that should not be assumed from the vision of the user reading the site.

I feel the project between a fine line of performance but also not write too low level or clever code. This is why the documentation content tips about readibility.

About benchmark, I do not feel confident with them because

1. most of the benchmarks you can find are bad preconditions, so result is not deterministic.
2. as you mentioned, the result is could be different between node versions or browser.

Of course this is not an excuse for don't refutate documentation affirmations.

My point was provide a bibliography section from people with more experience than me, but the most important thing I did the site more accesible to make possible anyone can edit a wrong or incomplete piece of documentation.

[fed135]

Don't get me wrong, this is a good initiative, I think it can help in the majority of cases. Most of the topics covered are on point and I don't know of anything like it right now.

So I didn't mean to discourage you, quite the opposite. Performance in JS is a very complex topic and I think projects like yours are a step in the right direction.

I'm just trying to think of a way to verify or test assumptions in various contexts and environments. This could be under the shape of a runnable samples on the site using benchmark - which is somewhat consistant (not sure for reliability) and running those on vms with the desired os/node versions.

Someday perhaps. I'll close the issue now. Thanks for hearing me out!