Is it an easy fix though? It seems necessary, but not sufficient, to build an open source, cross platform JavaScript engine that integrates with node.js, just

Is it an easy fix though? It seems necessary, but not sufficient, to build an open source, cross platform JavaScript engine that integrates with node.js, just to be able to advocate for the benchmark change to be made. That seems like a non-trivial task. Though luckily (for the JS community) they've been working on it. Happily, they've thought about this stuff already: "Continuing to invest in understanding and improving real world performance is a priority for the team. Going forward, we also want to work with the benchmarking workgroup[0] and the community to identify real world performance scenarios for Node.js." [1] [0] - https://github.com/nodejs/benchmarking https://github.com/nodejs/benchmarking [1] - https://blogs.windows.com/msedgedev/2016/01/19/nodejs-chakracore-mainline/ https://blogs.windows.com/msedgedev/2016/01/19/nodejs-chakra...