uclicious VS serde

I made this handy function to pass callbacks to C: https://github.com/andoriyu/uclicious/blob/master/src/traits...

I'm using a library that I wrote because I was unhappy with what was there: https://github.com/andoriyu/uclicious

You misunderstood. Game developers should use a _good_ third–party library, not a _bad_ one. At a minimum they should be able to read the source code so that they know it is good. Thus open source libraries should be at the top of the list.

If you don't know what “good” looks like, take a look at [Serde](https://serde.rs/). It’s for Rust, but its features and overall design are something you should attempt to approach no matter what language you’re writing in.

We have written our own http server framework focused on openapi support: https://docs.rs/dropshot/latest/dropshot/

https://serde.rs/ is the serialization/deserialization framework in Rust, and is well supported in the ecosystem.

We also wrote https://github.com/oxidecomputer/oxide.ts to generate TypeScript clients from the OpenAPI.

We mostly use react-router (or remix for older things that haven't been upgraded yet).

So the way that it works is, you define your api in dropshot. You ask it to generate an openapi document. You run this on that document to get a typescript client. And then you use that client in your react-router application.

I'm personally using it in the "framework" mode, so I have a "backend for frontend" going on, but the main appliccation is using it purely on the client, served from the same server as that API. Both have pros and cons.

If the request parameter cannot be parsed, the appropriate response code is sent instead of calling the function, so we have the usual comfort of type safety. Request bodies are handled very similarly, and of course, parsing integrates seamlessly with serde.

lack of finished solutions for serde (default values, partial initialization)

Serde Crate

We’ll use Axum with Tokio to build a web backend, Tracing for logging, and Serde for serialization and deserialization.

On the flip side of this, when libraries in rust do reach 1.0, they often are just done. The serialization/deserialization library serde which has become the de-facto standard has been on 1.0.xxx for the past seven years. https://crates.io/crates/serde/versions

I think this speaks to rust's strengths in that if you know your spec, you can write a rock-solid version of it - and its weakness, where if you don't know your spec you'll be making breaking changes a lot.

Serde Documentation: Comprehensive guide and reference for using Serde, Rust's framework for serializing and deserializing data.

Not just for hardware support: https://github.com/serde-rs/serde/issues/2538