lib-ruby-parser VS artichoke

I realize this might not be for everyone, but I'm writing it in Rust using Lib-ruby-parser and tower-lsp: two existing libraries that handle a bunch of the heavy lifting for me. I'm more productive in Rust than with Ruby at this point, despite doing Ruby full time for 15 years, plus I really really don't want to have to deal with a slow LSP--that was the whome impetus for this project. I started in the spring, made a bunch of headway, then backtracked to redo the internals to make it easier to handle monkeypatching, overriding/redefining of methods, etc. across your project.

For now Artichoke leans on mruby’s parser, but I’m looking forward to using https://github.com/lib-ruby-parser/lib-ruby-parser which is a Rust port of MRI’s parse.y.

The java based ruby, removes the GIL, which provides us real multithreading.

Truffleruby is "A high performance implementation of the Ruby programming language, built on GraalVM." If you prefer there is even a rust based ruby https://github.com/artichoke/artichoke

again, IMO, the microbenchmark, doesn't matter. What matters is the problem domain, whole stack and the whole "speed", including development, deployment and etc, and for some domains, ruby is the best and fast choice.

Not to be pedantic but Ruby has webassembly support, still won't work on the BEAM.

https://github.com/artichoke/artichoke

Artichoke is a Ruby interpreter written in Rust.

The owner of this reserved crate is Ryan Lopopolo who seems to indeed work on artichoke

I believe it was written mainly for/within the context of artichoke, which is an implementation of Ruby written (mostly) in Rust. It's a neat project!