Autogenerating Rust-JS Bindings with UniFFI

I&#x27;m not a rust dev, but this language is moving so fast into new territories that I&#x27;m more and more interested in picking it up.<p>Could UniFFI be used to generate native modules to use rust with react native?<p>The web story with wasm already looks like it could eat away a big chunk of JS&#x27;s share if WebIDL becomes a thing.

I built a proof of concept with UniFFI recently at work. The futures&#x2F;async support is quite immature and for me meant declaring part of my functions in the UDL file and partly in proc macros, but it&#x27;s not clear what is supported where. It&#x27;s still a little early, but is generally a really cool project.

I&#x27;m using <a href="https:&#x2F;&#x2F;koffi.dev" rel="nofollow noreferrer">https:&#x2F;&#x2F;koffi.dev</a> for running rust-compiled code in Node.js, so if this -in any way- means there&#x27;s going to be something that <i>just works(tm)</i> as part of the standard JS stack, rather than having to rely on third parties to &quot;mostly&quot; implement FFI, that&#x27;d be amazing.

Similar to the PythonMonkey project which provides high level bindings to SpiderMonkey from Python. Although its implemented in C++, I wonder if it or other projects like it could benefit from UniFFi<p>PythonMonkey lets you arbitrarily execute JS code like:<p>``` import pythonmonkey pythonmonkey.eval(&quot;(() =&gt; { console.log(&#x27;hi from js&#x27;); })()&quot;) ``` for reference.

Did switching from &quot;everything is synchronous&quot; to &quot;everything is asynchronous&quot; break a lot of other UniFFI users? I keep hearing people recommend UniFFI as the solution for <i>Easy-FFI</i>™, but that sounds like a drastic change that might break folks downstream.

This what I actually want LLMs to do. Generate spec adhering code from one language to another

why is this big news weve had this stuff for decades now ?