Most professional development I have seen in the past few years already uses a build step, either to pack dependencies, to run linting or to polyfill language f

Most professional development I have seen in the past few years already uses a build step, either to pack dependencies, to run linting or to polyfill language features, so this Binary AST will not really change that. Indeed, I hope that Babel, Webpack & co will eventually ship with an option `--binary-ast` and that the only change for developers will be to add this option to their toolchain. However, if you wish to write JavaScript without build step, you will of course be free to continue doing this. I don't think that anybody has ever thought of making the Binary AST compulsory. It's just a build target that you can use for decreasing file size and parse time. For stats, see the proposal. We'll add more stats once the advanced prototype is complete. > I care a lot for performance, if you want to make me happy, make text rendering in the canvas faster. And if you could also make eval faster I would be very happy. I'm sure both are in progress, but entirely orthogonal to this proposal.