chruby VS faster-cpython

Let’s get started. I prefer to manage my Ruby installations on my development machine with chruby paired with ruby-install. Another outstanding set of tools is rbenv with ruby-build. I highly recommend installing Ruby with one of those two sets of tools. Follow the instructions on their project’s READMEs. For this article, I’ll be running Ruby (MRI) v3.3.0.

To fix this, you’d need to install Ruby correctly using a version manager such as chruby. You’d need to install Homebrew on your Mac first using the command below in your terminal:

Now about the second point on the complexity of the shim strategy (cf. the rbenv implementation) with respect to the PATH update strategy (cf. the chruby implementation), what do you think?

I don’t want any of the bells & whistles that come with rvm and rbenv; I prefer the simplicity of chruby. I’ve used it for 10 years (is that possible?!) and I’ve never cursed at it.

When you type chruby, the function is executed. If it doesn't do what you expect, it's either an issue with the function or your expectations aren't warranted. In any case you'll need to seek help from people who supplied you with this function. If your chrubby function is this one, you can ask from help on https://github.com/postmodern/chruby.

I knew I saw your username somewhere in my investigation: Properly handle gems installed via --user-install.

I use homebrew, chruby, and ruby-install.

It is unclear to me whether Python 3.12 will receive significant improvements. Based on the information from https://github.com/faster-cpython/benchmarking-public, it appears that there may be a 2% performance enhancement. Is this the anticipated result, or are there additional developments awaiting merger?

Initially, the "Shannon Plan" (https://github.com/markshannon/faster-cpython/blob/master/pl...) aimed for a 50% improvement with each release. Has this goal been deemed unattainable, or are there adjustments being made to the plan?

Yes, that's the JIT part of the plan. Sections of code will be compiled, "at runtime". Those sections of compiled code will be tied together with interpreted code. It will be somewhere between rare to impossible to have a fully compiled program, without interpreter glue.

see: https://github.com/markshannon/faster-cpython/blob/master/plan.md

Yes, the Shannon plan, which is actively being worked on by a team headed by Guido, includes JIT work in stages 3 and 4

The goal with faster cpython is for small compounding improvements with each point release[0]. So in the end it should be much more than a tiny improvement.

[0] https://github.com/markshannon/faster-cpython/blob/master/pl...

The Shannon Plan. Announced by Guido at the 2021 Python Language summit, funded by Microsoft.

Well, good news then, it's in the planning!