webrtc-unreliable VS ozz-animation

The Cargo.toml on GitHub has the optional dependency specified correctly.

I use WebRTC for multiplayer, and Rust has a great library (webrtc-unreliable) To be fair, C++ has libdatachannel which I like using too.

You can, in theory, get UDP-like characteristics out of a different web API - with a WebRTC datachannel configured to be unreliable and unordered. I haven't seen anybody use that API just because it's a pretty big pain to use. The developer of Agar IO called it too hard to use in a HackerNews comment, but nowadays there's simpler libraries than the ones he had in 2016 like webrtc-unreliable and libdatachannel. You still need to run a STUN/TURN server and the integration is easier than it was back then, but still much harder than raw UDP sockets though.

webrtc-unreliable: Provides an async API to a UDP-like transport over WebRTC

You can do this today with https://github.com/kyren/webrtc-unreliable

Take a look at webrtc-unreliable. I haven't tried it, but it claims to implement just a simple subset of webrtc to get udp-like functionality.

I really like the C++ ozz-animation library, and Rust doesn't have a good answer for it (yet! work is being done) It has a really great compressed animation data format that again is good for the web It also has a great runtime library for distributing animation calculations across separate cores

I'm not sure that even Sokol has animation support built in. The animation sample appears to use OZZ Animation, which could probably be used with the other rendering libraries too.

http://guillaumeblanc.github.io/ozz-animation/ for animations

On the otherhand, if I was going to pull in some code/an existing animation system, I have been interested in messing with https://github.com/guillaumeblanc/ozz-animation. It is pretty cool. There is a separate runtime/engine code from whatever editor/asset management you use. I've been toying with the idea of maybe pulling it into Jedi Academy.