It's very interesting to see how their benchmarks [1] progress over time. I would love to see a comparison with the alternatives. Perhaps that could show some of the benefits of writing this in Rust.<p>For another JavaScript parser, but written in TypeScript, check out Seafox [2]. It's also self-hosted [3], which I always enjoy seeing.<p>[1] <a href="https://boa-dev.github.io/boa/dev/bench/" rel="nofollow">https://boa-dev.github.io/boa/dev/bench/</a><p>[2] <a href="https://github.com/KFlash/seafox" rel="nofollow">https://github.com/KFlash/seafox</a><p>[3] <a href="https://en.wikipedia.org/wiki/Self-hosting_(compilers)" rel="nofollow">https://en.wikipedia.org/wiki/Self-hosting_(compilers)</a>
> Boa is an experimental Javascript lexer, parser and compiler written in Rust. It has support for some of the language, can be embedded in Rust projects fairly easily and also used from the command line.
Does anyone know what they mean by "compiler"? The README file on their repository didn't expound on this. (I have a very fast parser and lexer for JavaScript written in C++ that is very compliant in Cycript--the main issues I sometimes see are in my hacky "try to do everything in a single pass"semantic optimizer pass I am doing to generate code, but that is of course optional--though I haven't pushed updates to its repository in a few years despite my doing a lot of work on it... I kind of decided at some point I hated users. But I don't have a "compiler" unless the meaning is "compile from JavaScript to JavaScript", in which case it would be fun to benchmark it against boa and I might start doing that. It is just that it sounds a bit like boa is also executing the JavaScript?)