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

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

The one thing that in hindsight I should've expected but didn't at the time was calling wasm functions from a frontend and not declaring them as references on the rust side for exported rust types. As you may expect, the wasm memory zeroes it after taking ownership and running the wasm, but the object in the js space is still a valid object/type/whatever, just that it's complete garbage and points to 00000 etc in memory.