Ruby MRI

It's a funny time, 'cause now, like, all this stuff is like, okay, Ruby's great, and if Ruby is the language we can interact with LMS to build our applications with, then awesome.

But, like, past writing the Ruby code, most of us are not getting into the CRuby internals or anything like that.

We're not diving there, so we don't even realize what actual code gets run.

We're just doing our abstraction layer over the, the actual C version.

But because I'm always gonna have Ruby wherever this specific piece of code is running, I don't think it really benefits me much.

The CRuby bindings, like you can't run CRuby on embedded stuff, right? Like if you're gonna do some embedded hardware IoT thing, right, it's not really meant for that.

And then you've got people that live on JRuby or things like that, right? You know, there's all these different runtimes that have existed for various benefits that people want to be able to put this in and have this connect to this and all those kind of things.

So I wonder how much of if we just start going past that, we don't need that all of a sudden, then maybe if we're just getting down to something where, hey, this is going straight to an executable that doesn't need that runtime, what can it do? What can't it do? And I think this is something that I maybe didn't come across in the keynote, and it's unfortunate because I feel that the nature of how 37signals builds and what they build is dramatically different than a lot of what people in the space are building and working on.

It seems like a freaking neat thing because let me show you here.

Rails on CRuby plus YJIT.

326 requests per second.

Not terrible.

Rails on JRuby, 1,000 requests per second.

So about triple.

Roundhouse emitted on CRuby and YJIT, 3,300 requests per second.

So again, triple.