chruby VS cinder

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.

Meta is actually contributing directly to upstream cpython. If you really wanted to, the internal fork is also open source: https://github.com/facebookincubator/cinder

Just one example: last year Meta open-sourced Cinder, which powers Instagram and provides sizeable speedups compared to CPython.

I used to work on the Cinder JIT and can help document any passes you find interesting or confusing.

You might enjoy Cinder then. It's based on CPython so it is nearly 100% compatible.

https://github.com/facebookincubator/cinder/

Disclaimer: I used to work on it.

I think Cinder's Static Python, which also performs runtime type checking, is more ambitious. Though it's not production ready yet.

Here's a fork that implements that https://github.com/facebookincubator/cinder - it might be nice to one day get that up streamed but obviously it'll be controversial and it certainly needs more time to bake. Hopefully at some point we can make it a pip installable extension though.

The other thing that was interesting to me, was the potential of type annotations to help make for a faster, safer experience on the compiler end of things. One example is seen in Meta’s Cinder project, on the docs it explains how typing can be used to reduce the number of steps for the compiler ([cinder/static_python.rst at cinder/3.8 · facebookincubator/cinder · GitHub](https://github.com/facebookincubator/cinder/blob/cinder/3.8/CinderDoc/static_python.rst)), making it more effective.