diplomat VS typeshare

The tooling for the first kind -- calling Rust from another language -- is a bit less developed, and tends to rely on code generation that doesn't necessarily produce a natural C API. cbindgen, uniffi, cxx, and Diplomat all take this course.

I don't think that accurately describes what ICU4X does. It generates code directly in the language needed using Diplomat. Which currently supports JS/TS/Wasm, C, C++, and .NET, but we plan to support more (Dart is actively being worked on, there is a lot of interest in Java). Diplomat is designed to be relatively easy to write backends for: you have to write code that converts its internal IR to bindings code, so you mostly need to understand that internal IR and figure out how to idiomatically map it to other languages.

The ICU4X team is developing diplomat - https://github.com/rust-diplomat/diplomat/

I'm not that interested in a separate tool for this but it would be really cool to have a dart plugin as a part of Diplomat. Diplomat's not fully polished yet but it's totally okay to add new language backends to it. (Eventually I plan to restructure it so that it has a cleaner plugin interface, but for now "checked into tree" is fine for backends)

It doesn’t generate a complete client but 1Password’s Typeshare can generate TypeScript from Rust data structures https://github.com/1password/typeshare

Aren't there things like typeshare to aid with that case?

Sure. I would love some help. I am visiting my family all March (I am typing this from the airport), so I don't know how much time I'll have to work on trane for the next month. But maybe that gives you some time to use it, and read the code and docs.

I am not going to put my personal email here, and I don't see an option to send private messages on hn, although it's probably out there somewhere. Probably in the commits, lol. Worst case, feel free to open an issue on the trane repo.

As a first ask, what do you think of this: https://github.com/1Password/typeshare?

I figured writing the UI in rust is probably not a good idea. The ecosystem for UI is very immature and the language itself is probably overkill. But doing it in typescript/html/css requires you to understand the internal data structures (all the JSON files you see in the courses are just serialized rust objects).

I found that repo and it seems like a promising approach to autogenerate the types and make the interaction easier.

How does this compare to typeshare?

Recently, 1Password open-sourced Typeshare, to help Rust developers create FFI (foreign function interfaces). Curious to learn more? Join the team behind the tool this week on Zoom at 11a Eastern to discuss Typeshare and answer any questions.

Newly open-sourced project that might be handy for some of you all https://github.com/1Password/typeshare

Typeshare by 1Password, the original inspiration for this blog post. It's available on crates.io.

For sure! We actually open sourced an early version of it a while back (https://github.com/1Password/typeshare), but it became a slowdown to work on it both for our own internal needs and for the outside world, so that was abandoned and it's since fallen out of sync with the project internally today.