it’s actually really easy to migrate bits of logic from python/js/etc. to Rust and get immediate performance improvements

even just calling as a subprocess, the easiest method with the most overhead, can be a huge improvement

gud article

it’s actually really easy to migrate bits of logic from python/js/etc. to Rust and get immediate performance improvements

even just calling as a subprocess, the easiest method with the most overhead, can be a huge improvement

gud article

https://t.co/KtYFTzFdAs

lispy dev, building /basedremyboys

basedremyboys.club

I’ve used Rust native modules from Node, as well as from Python with bindings generated by PyO3, and it’s been super easy and smooth each time

gonna give wasm more of a shot soon

> at runtime I don’t expect anything beyond “an error happened when calling this foreign function” and if i’m really lucky a line number

Stuff like that makes me want to write a small lisp pre-processor over zig, still can use its ecosystem & libraries, etc but with lisp macros, and a proper repl.

I treat them as external libraries, so they get their own tests etc. in their own repo

at runtime I don’t expect anything beyond “an error happened when calling this foreign function” and if i’m really lucky a line number