4 ms·

We Built a Cross-Platform Library with Rust

• deleted 5y ago
  [deleted]
• apendleton 5y ago
  I wonder how practical it would be, and what the performance hit would be like, to just use WASM everywhere, since they've already built a WASM backend for their JS client? It seems like that would let them sidestep having to build everything per OS/arch, and it seems like most languages have WASM runtimes nowadays.
  • saolsen 5y ago
    Hey, author here. I've wondered that myself. It's not quite as "built in" to other languages as it is in JavaScript but if there was a good implementation it could probably work well. Something to look into.
• kodah 5y ago
  I have this problem. My team supports four different SDK's that are fairly parallel to the selection Oso has. Maintaining all of the core logic for each of these SDK's is really tiresome and not scalable as an organization grows. I've been looking for ways to write the core client logic in one language, and have frontends in each of the languages we support. I've previously thought about WASM for this, but I haven't found any ways to embed a binary (like WASM) in a Go package. This post is a good update, showing it's possible even if complicated. If anyone has write ups on how, I'd love to read them.
  • xet7 5y ago
    Maybe https://haxe.org https://haxe.org and https://go2hx.github.io https://go2hx.github.io could be a little related?
• fuddle 5y ago
  Sounds similar to https://github.com/mozilla/uniffi-rs https://github.com/mozilla/uniffi-rs. Hopefully Oso open source their library.
  • kodablah 5y ago
    > Hopefully Oso open source their library. https://github.com/osohq/oso https://github.com/osohq/oso seems to have the core, C FFI, and language bindings.