codemod VS cinder

This is new to me, sounds interesting!

I once used Codemod [0] to migrate an old JS codebase. Would this be a use case for Ohm as well?

[0] https://github.com/facebookarchive/codemod

That differs but is a reasonable understanding. I’m instead referring to automations that perform large scale refactoring as handled by Facebook, who would be contributing to this effort.

https://github.com/facebookarchive/codemod

It sounds like what you are describing is what’s known as poly fills which convert code into a variant that maximizes function across implementations which isn’t really applicable here.

That's why I've been working on a tool that automatically upgrades major versions of libraries with breaking changes, the idea is to simplify the process and save developers time and effort by having a bank of transformers (using codemod & jscodeshift) and open source them:

What they did appears similar to https://github.com/facebook/codemod.

I think codemod is probably one such tool: https://github.com/facebook/codemod

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.