node-foundationdb VS create-rust-app

Thats fantastic.

I maintain the nodejs bindings for foundationdb. Foundationdb refuses to publish a wire protocol, so the bindings are implemented as native code wrapped by n_api. The code is a rat's nest of calls to methods like `napi_get_value_string_utf8` to parse javascript objects into C. (Eg [1]). As well as being difficult to read and write, I'm sure there's weird bugs lurking somewhere in all that boilerplate code.

I'd much prefer all that code to just be in rust. That looks way easier to use than all the goopy serialization nonsense I'm doing now. (Though I'd want a serde_napi variant instead of going straight to v8).

[1] https://github.com/josephg/node-foundationdb/blob/master/src...

So, you're looking for create-rust-app?

It's finally come together! If this peaked your interest, check out https://github.com/Wulf/create-rust-app

hey r/reactjs, just wanted to share some work revolving around integrating dsync with create-rust-app.

hey r/rust! I just finished testing and releasing the `dsync` integration with create-rust-app. Let me know what you think!~

tsync by Wulf created as part of the awesome Create Rust App utility for setting up fullstack Rust apps. It's available on crates.io

Wowowowow thanks for your efforts behind this!

I’ve integrated vite with a rust backend[1] and so many people have asked me how I managed to achieve SSR because they equate SSR with render+hydrate but it’s really just classical SSR. I think I can finally make their dreams come true because of this.

[1] https://github.com/Wulf/create-rust-app

I mainly wrote this as a database-first approach for create-rust-app