Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
| Package | Version | Downloads · 30d | Trend · 30d |
|---|---|---|---|
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — |
Live mentions badge
Show how many posts mention your project in the last 30 days.
Live mentions · last 30 days
Mentions
@RuskiZoomer give this to your agent or a similar guide / skill I might not be aware of johnthagen/min-sized-rust
TFA did [0] the most important stuff for minimizing Rust binaries: release mode, LTO, strip, and abort on panic. But there is a lot more you can do if you really care about Rust binary size [1]: remove location details, purge the debug formatters, rebuild the standard library for size, abort with no error message at all, and nuttier stuff. [0]: github.com/zion-sati/NetWasm/blob/main/docs/size-… [1]: johnthagen/min-sized-rust
> ultimately everything is eventually possible against any given hardware. Not everything, no. You can't run C# without the .NET runtime. Some parts of it are irreplaceable. And the Rust optimizations to shrink binary size (see johnthagen/min-sized-rust) are commonly done in production when it matters, not just in WASM but also in embedded.