Are there truly people out there that are terminating HTTP/2 at the application level? That's really quite surprising for anything serving production traffic.

rubocop uses rubocop-ast uses parser, so it will eventually make its way down to rubocop once we finish the compat layer for the parser gem.

Depends on what you mean by Solargraph, because it's kind of a large project. If you mean their typechecking, then definitely not, because it's not using a Ruby parser. If you mean the general feedback, then yeah potentially.

Rubocop yes if it ends up using YARP as a new backend.

Either way, I would suggest you check out ruby-lsp, which is definitely going to benefit from this speed, and soon.

Maybe I'm a masochist, but to be honest it's a dream job. Working on such a complex language and history is really really fun.

The templating is definitely an effort to keep the maintainability in check. It's also because we're planning on keeping a grammar around to generate test cases for us with fuzzing/other algorithms.

The encodings is a bit historical, to my knowledge Ruby is the only major language that was developed by someone whose language did not work with ASCII. So the first encodings written in Ruby were the old Windows pages.

Is that semantic difference documented anywhere? I’ve never heard of this before, would love to learn more.

The official documentation for the implicit conversion protocol (which to_str is part of, as distinct from to_s) is here:

https://ruby-doc.org/core-3.0.2/doc/implicit_conversion_rdoc...

to_s is documented here:

https://ruby-doc.org/core-3.0.2/Object.html#method-i-to_s

Definitely check out prettier for Ruby then! https://github.com/prettier/plugin-ruby. Actively working toward 1.0.