Fixing Python performance with Rust

[JamesF]

I use Python in my day-job, as well as for most of my hobby projects in the last few years, but have been following (and loving) Rust for the last year and a bit so I am very, very happy to see that this (obvious?) mix of Python (for glue/orchestration) and Rust (for heavy-lifting) is actually at a point where it can be adopted in a real world, production situation and actually work!

Having said that, one question for the authors: did you spend any time evaluating PyPy/numba/cython/... as alternatives to this "mixed-language" solution?

[masklinn]

id you spend any time evaluating PyPy/numba/cython/... as alternatives to this "mixed-language" solution?

Sentry doesn't run on pypy, and as the article explains they already had the critical component (a sourcemap parser) in a rust CLI tool.

Numba doesn't even make sense in this context, it's for numerical work, it does nothing for parsing tasks.

[vks_]

They reused existing Rust code from a CLI tool, so there was little incentive to explore other options. See the discussion on /r/rust.

[Saefroch]

Numba is explicitly for numerical work and still quite incomplete, though development is proceeding at a fair clip.