[chrisseaton]

> Keep Ruby as it is - slow and expressive.

Why not try to make Ruby faster without changing how expressive it is? I don't think this project does that by the way - it breaks Ruby semantics - but let's aspire to make Ruby faster.

> If you need to speed up, get faster hardware.

If your code is still too slow for your required per-request latency on a top-of-the-range Xeon and your individual requests have no useful parallelism and are not memory or IO bound... where do you go from there? Where are you getting faster hardware from?

Sometimes there is no faster hardware.

[irjustin]

Ruby is getting a JIT in 3. So it's happening. I'm always supportive of small projects and this is no exception. Still, it is going to get crowded out by the generalized offerings of Ruby 3.

There may be some benefit to ultra specialized for this project to live in still but the audience is going to be quite niche.