evcxr VS rutie

Emacs didn't invent REPL, and it's common everywhere. For Rust: https://github.com/evcxr/evcxr/blob/main/evcxr_repl/README.m.... But heck, the compiler is reasonably fast enough that any IDE can REPL by compiling the code.

The value here is more in being able to read a script before you run it, then have it run fast, maybe tweaking something here and there. And a compiled script will run 10,000 times faster than LISP, which can be important.

https://github.com/evcxr/evcxr can run Rust in a Jupyter notebook. It's not Golang but close enough.

The engine uses rust_decimal::Decimal to represent high precision decimal numbers, like the weight property. Serialization of RocksDB keys is done by the storekey crate. To know how Yumi's machine stores diffs, we can now ask- How does storekey serialize rust_decimal? Well, using evcxr to run Rust in Jupyter, the answer is as a null-terminated string:

In theory you should be able to create Rust notebooks (Jupyter notebook) using evcxr so maybe some AI, data analysis, prototyping make sense if you aim for good performance in final application (protype in evcxr and use notebook as reference to implement final application in Rust for speed and safety).

You should check out evcxr

There is also implementations of rust REPLs, like the beautifully named evcxr.

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!