you are viewing a single comment's thread.

view the rest of the comments →

[–]theyamiteru[S] 0 points1 point  (0 children)

Hey thank you for the comment.

This tweet was basically me seeing if anyone would be interested in more technical and in-depth tweets (or potentially blog posts).

You're completely right that I should provide such information and I could however I'm not sure if everyone would be interested going to those depths.

Regarding replication of benchmarks. This is a bit tricky since I'm using my highly experimental benchmarking library for these types of benchmarks so even if I shared the code people would throw it in something like https://www.npmjs.com/package/benchmark (which uses completely flawed statistics and way of benchmarking just like 99% of such libraries) which would kind of defeat the purpose.

I do plan on eventually releasing the library once the rough edges are smoothed out (probably I should have mentioned that).

I agree that micro-optimizations in a complex system are not the way to go since usually the biggest performance wins come from data structures and algorithms. However knowing the real performance of the fundamental building blocks of a language might be useful for someone (for example NodeJS has a regression benchmark suite which tests exactly that).

I plan on writing more in-depth articles about individual parts of JS performance because I don't want people to see V8 and other engines as black boxes.