rutie VS rust-cpython

For example, they list PyO3 for Python (see also maturin for packaging), NAPI-RS for Node.js, and Rutie for Ruby.

If this sounds useful you should also take a look at rutie, another library that does the same thing and has been around longer.

I'm not the first person to have this idea, there's also the great rutie. I make no claims that Magnus is any better, it's just my attempt at it.

I did some tinkering before with excelent rutie gem, which enables writing ruby libraries with rust as native extension, so was wondering if I could use that one + ripgrep for faster searches.

hlua or rlua are what you want for Lua, rust-cpython or PyO3 for Python, rutie for Ruby, and possibly deno_core for JavaScript.

I was at first using mrusty, then I switched to rutie, because I thought mrusty didn't support blocks (it does, it's just he documentation for it is easily missed, it's in the docs for the for the mrfn! macro, right near the bottom of the page), so I'm switching back (haven't yet started on this redo) because it has what I want & it's easier to use.

If writing the whole API in Rust is too big of a sell for your employer, I highly recommend checking out rutie or helix (running native rust modules from ruby).

Helix (https://github.com/tildeio/helix) is deprecated though. The only candidate alive enough seems to be Rutie (https://github.com/danielpclark/rutie). At least you don't risk putting people in the wrong direction! I think I will buy the book, from skimming it seems cool!

I've never used pyo3, just cpython, but the latter at least let me do things like:

And don't forget https://github.com/dgrunwald/rust-cpython to complete the circle

For interoperating with Python, check out PyO3 or rust-cpython. (More generally, see Rust Interop and Are We Extending Yet?)

You probably should learn Rust. Aside from the process of learning new and different languages making you a better programmer, rust-cpython, PyO3, or Interoptopus make it easy to expose Python APIs from your Rust code. (eg. So it's easy to compile the same codebase as both a Python module and a WebAssembly module.)

Have you looked into abi_stable, flapigen, interoptopus, cbindgen, PyO3, or rust-cpython?

Personally, I'm not willing to compromise on my GUI look and feel, so I use PyQt or PySide to write my GUIs against the QWidget API (I'm a KDE user and Python is the only language with mature memory-safe bindings to Qt) and, if the project can be structured with a frontend-backend separation, I use rust-cpython or PyO3 to write a backend in Rust that the Python frontend can import. Sort of using Python/Rust as a QWidget analogue to the QML/C++ architecture promoted for Qt Quick. (Which I don't use because it's still too incomplete on Kubuntu 20.04 LTS.)

also, check out rust-cpython, PyO3, and maturin, among other things. They're really nice options for using Rust for its strengths and Python for its strengths within the same project.

This section uses flapigen to expand the foreign_class macro into many cpython functions as an extension module, and cargo compiles it as a cdylib. If you want to see what that looks like, install cargo-expand and run cargo expand. You'll get a lot of generated rust code.

For Python specifically, In addition to using rust-cpython or PyO3, maturin makes it really comfortable to build, package, and publish Rust code into Python packages and, if your niche doesn't quite fit, there's setuptools-python which might do it.

hlua or rlua are what you want for Lua, rust-cpython or PyO3 for Python, rutie for Ruby, and possibly deno_core for JavaScript.