3 ms·
I would like to see Babel ES6-to-ES5 converted performance here too, because that's how most real-world ES6 code is going to be run --- there are too many non-E
by david-given 11y ago
I would like to see Babel ES6-to-ES5 converted performance here too, because that's how most real-world ES6 code is going to be run --- there are too many non-ES6-compatible browsers out there.
- masklinn 11y agoThat's exactly the information the "babel" rows provide? Each row is a given "ES6 implementation" and how it performs compared to the baseline "ES5 native" implementation of a feature. So the first row of each section is the babel-compiled (to ES5) ES6, the second is traceur-compiled, third is typescript-compiled and last is native ES6 runtime. If you look at the test files, most of them only have an es5 and an es6 versions.
- david-given 11y agoOh, FFS. I managed to spend some time looking at the table without actually seeing what the entire point of it was. Tea, you have failed me! Sorry about that.
- jsprogrammer 11y agoIsn't that what the 'babel' rows show?