nanoserde
node-foundationdb
Our great sponsors
| nanoserde | node-foundationdb | |
|---|---|---|
| 3 | 1 | |
| 559 | 111 | |
| - | - | |
| 6.8 | 1.5 | |
| 11 days ago | 4 days ago | |
| Rust | TypeScript | |
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nanoserde
-
venial 0.1 - A lightweight alternative to syn
what do you think of the parser in nanoserde? https://github.com/not-fl3/nanoserde/blob/master/derive/src/parse.rs
-
How to speed up the Rust compiler in 2022
Yeah proc macros have a massive hole in their user experience. Nobody actually wants to use them without syn + quote functionality, so the majority of people just pay the compile time cost of syn/quote/procmacro2. But then a subset of people can't afford to pay the compile time cost, so they either: 1. Don't use them. And remove all of their deps that use them ... which is generally a lot. 2. Hand-manage the TokenStream (which is very much not fun). Macroquad doesn't want syn + quote in their tree because they care _deeply about compile times, so they opted to re-implement serde. Serde is the crowned jewel of the rust ecosystem. Someone feeling unable to use it is a massive failure of the system.
- The Serde Rust Framework
node-foundationdb
-
The Serde Rust Framework
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...
What are some alternatives?
miniserde - Data structure serialization library with several opposite design goals from Serde
sapio - A Bitcoin Programming Language
serde_v8 - Moved to https://github.com/denoland/deno
manifold - Manifold is a Java compiler plugin, its features include Metaprogramming, Properties, Extension Methods, Operator Overloading, Templates, a Preprocessor, and more.
serde - Serialization framework for Rust
create-rust-app - Set up a modern rust+react web app by running one command.
watt - Runtime for executing procedural macros as WebAssembly
Rocket - A web framework for Rust.
pfr - std::tuple like methods for user defined types without any macro or boilerplate code